[openstack-dev] [neutron] 'routed' network type, DHCP agent + devstack support - review requested
Neil.Jerram at metaswitch.com
Sun Jul 19 10:46:30 UTC 2015
Hi Neutron folk!
I'd like to give an update on and encourage wide review of my work on
a type of network that connects VMs through IP routing instead of
through bridging and tunneling at L2. I believe the core Neutron
pieces of this are now complete and ready for detailed review and
The change at  creates and describes a new 'routed' value for
provider:network_type. It means that a compute host handles data
to/from the relevant TAP interfaces by routing it, and specifically
that those TAP interfaces are not bridged. It is the job of a
particular mechanism driver and agent implementation to set up the
required routing rules, and my team's Calico project  is one
example of that, although not the only possible example.
The DHCP agent needs enhancement to provide DHCP service to routed TAP
interfaces, and the change for that is at .
A devstack plugin is included in the Calico repository at . Using
this it is possible to see 'routed' networking in action, using the
Calico mechanism driver and agent, simply by running devstack with the
following in local.conf:
enable_plugin calico https://github.com/Metaswitch/calico routed
Demonstration steps once stack.sh completes are suggested at .
FYI I also plan to propose a networking-calico project (or continue
proposing, given ), to contain the Calico mechanism driver and
devstack plugin pieces that are currently in , so that all of
Calico's OpenStack-specific code is under the Neutron big tent. But I
believe that can be decoupled from review of the core Neutron changes
Please do let me know if you have thoughts or comments on this.
More information about the OpenStack-dev