Floating ip get set on the wrong physical server

Gary Kotton gkotton at redhat.com
Wed Apr 3 11:27:49 UTC 2013

On 04/03/2013 01:35 PM, Nux! wrote:
> Hello,
> I'm currently testing Grizzly on EL6 from 
> http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-6/
> I'm using packstack to deploy it on 3 physical machines, one of them 
> acts also as controller, the other 2 are just nova-compute instances.
> The problem starts when adding a floating IP to an instance, in my 
> case the floating (public) IP gets set on the controller, whereas the 
> instance is running on another physical server...
> Any ideas?

On which host is the nova-network running? This is what performs the 
SNAT (i.e. the floating IP support). In nova you can run this on each 
compute node for HA and scalability.

More information about the cloud mailing list