We needed to setup something similar when we split out the nova-network service to a different host than nova-api in cactus, so that instances could get to the metadata service. It was pretty simple to make quagga work, but then we needed to add a rule to bypass NAT. Since this was just for the metadata service, it was a tightly scoped rule, but in your case, you'll probably want something that covers your whole intranet. You'll probably still want NAT for internet bound traffic. -nld
2012/4/19 Jérôme Gallard <jeronimo...@gmail.com>: > Hi everyone, > > I would like to know if someone has already tried to setup routing > configurations with nova-network. > > >From my understanding, nova-network only deals with NAT, but I am > thinking about configurations to directly routes my virtual networks > on my intranet. > > I am thinking to develop a new driver for the network manager which > can configure a RIP router (Quagga, ...). > > Any feedbacks ? > > Thanks. > > Regards, > Jérôme > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
