Excerpts from Cory Benfield's message of 2014-10-24 06:38:44 -0700: > All, > > Project Calico  is an open source approach to virtual networking based on > L3 routing as opposed to L2 bridging. In order to accommodate this approach > within OpenStack, we've just submitted 3 blueprints that cover > > - minor changes to nova to add a new VIF type  > - some changes to neutron to add DHCP support for routed interfaces  > - an ML2 mechanism driver that adds support for Project Calico . > > We feel that allowing for routed network interfaces is of general use within > OpenStack, which was our motivation for submitting  and . We also > recognise that there is an open question over the future of 3rd party ML2 > drivers in OpenStack, but until that is finally resolved in Paris, we felt > submitting our driver spec  was appropriate (not least to provide more > context on the changes proposed in  and ). > > We're extremely keen to hear any and all feedback on these proposals from the > community. We'll be around at the Paris summit in a couple of weeks and > would love to discuss with anyone else who is interested in this direction.
I'm quite interested in this, as we've recently been looking at how to scale OpenStack on bare metal servers beyond the limits of a single flat L2 network. We have a blueprint for it in TripleO as well: https://blueprints.launchpad.net/tripleo/+spec/l3-network-segmentation Hopefully you will be at the summit and can attend our scheduled session, which I believe will be some time on Wednesday. We're basically just planning on having routers configured out of band and just writing a Nova filter to ensure that the compute host has a property which matches the network names requested with a server. But if we could automate that too, that would make for an even more automatic and scalable solution. _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev