The Open vSwitch plugin with VLANs

This post looks at the Grizzly Open vSwitch plugin when it is configured to use VLANs to isolate the VM traffic of different Quantum networks on the physical network.

Metadata via the DHCP namespace

This is a follow-on from the previous post that described how metadata requests go from instances to the Nova metadata service via a namespace proxy in a Quantum router namespace. This post shows how requests can go via a namespace proxy in a DHCP namespace instead.

Metadata via the Quantum router

Grizzy adds support for the Nova metadata service to work with overlapping IP address spaces from Quantum. Now Quantum proxies metadata requests to Nova adding HTTP headers which Nova uses to identify the source instance. Quantum actually uses two proxies to do this: a namespace proxy and a metadata agent. This post shows how a metadata request gets from an instance to the Nova metadata service via a namespace proxy running in a Quantum router. It is also possible to run the namespace proxy in a DHCP namespace, but that is not covered here.

The Quantum L3 router and floating IPs

This post shows how the Quantum L3 Agent uses the Linux IP stack to implement the Quantum L3 Routing and NAT API extensions. It explains in detail how external access with floating IP works and how it can be debugged.

Debugging Quantum DHCP and Open vSwitch

This post describes how Quantum DHCP in Grizzly works when using the Open vSwitch plugin. A basic understanding of the mechanism is needed to troubleshoot issues.

OpenStack Grizzly with Quantum multi-node auto-install script

This Ansible script installs OpenStack Grizzly onto three Vagrant/VirtualBox nodes using the OpenStack packages from the Ubuntu cloud archive. The install steps are in the readme.