On 03/04/2013 05:45 PM, Guilherme Russi wrote: > Found the problem, when I did the step: ovs-vsctl add-port br-ex eth2, > it stopped my lan communication. The l3 agent makes changes to the routing table. This may cause a conflict with the default gateway. I would suggest having a static route for the management traffic (I guess that your could have been received via DHCP). Thanks Gary > > Any idea? > > > > 2013/3/4 Guilherme Russi <luisguilherme.cr at gmail.com > <mailto:luisguilherme.cr at gmail.com>> > > Hello guys, > > I'm installing the openstack folsom again, but now I have a > controller node in a proper physical machine and the network node > in another one, but which of them I execute the quantum-networking > script? I'm following this manual > http://docs.openstack.org/folsom/basic-install/content/basic-install_network.html > and I'm trying to execute at the network node, but I got error > when execute it. When I type keystone tenant-list and quantum > net-list I got the error [Errno 111] Unable to communicate with > identity service. > My novarc is configured at the network node too. > > Thanks. > > Guilherme. > > > > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack at lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack/attachments/20130304/c297b942/attachment.html>