[openstack-dev] [Network] Devstack+Quantum without namespaces

Gary Kotton gkotton at redhat.com
Wed Apr 24 10:06:45 UTC 2013

On 04/24/2013 11:16 AM, Maru Newby wrote:
> It appears that when I configure Devstack with Q_USE_NAMESPACES=False on a single-nic box, the resulting routing configuration is given two default routes (the original route and one added by quantum l3 agent for the floating ip range) and that prohibits external connectivity.  This addition happens as soon as the l3 agent is started, and the subsequent configuration of tempest will fail (due to a lack of external connectivity) where package installation is required.  Manually deleting the route added by quantum restores connectivity on the host, though private ip connectivity is lost.
> I apologize if I am missing something in the docs, but is there a way to reliably bring up devstack+quantum without namespaces?  Is a second nic required?  Note that this doesn't have to be production-grade (the docs are clear that running the l3 and dhcp agents on the same node is discouraged), as my goal here is only for a usable test environment.

This can be addressed by setting a static route prior to running the 
quantum services. The l3 agent will create a default route - hence the 
network issues.

> Thanks in advance,
> Maru
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

More information about the OpenStack-dev mailing list