Isn't that the normal behavior (and not even Grizzly specific)? Since the nodes are not normally reachable from outside, the public IP can only be reached if it's configured on the controller. The controller will then map the floating IP to the internal node IP through NAT.
To see whether that happens:
iptables -t nat -L | grep -e ^DNAT -e ^SNAT
-- Sandro
On Wed, Apr 3, 2013 at 12:35 PM, Nux! <nux@xxxxxxxxx> 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?
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/cloud
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud
