<div dir="ltr">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.<div>
<br></div><div style>To see whether that happens:</div><div style>iptables -t nat -L | grep -e ^DNAT -e ^SNAT<br></div><div style><br></div><div style>-- Sandro</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Apr 3, 2013 at 12:35 PM, Nux! <span dir="ltr"><<a href="mailto:nux@li.nux.ro" target="_blank">nux@li.nux.ro</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I'm currently testing Grizzly on EL6 from <a href="http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/epel-6/" target="_blank">http://repos.fedorapeople.org/<u></u>repos/openstack/openstack-<u></u>grizzly/epel-6/</a><br>
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.<br>
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...<br>
<br>
Any ideas?<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Sent from the Delta quadrant using Borg technology!<br>
<br>
Nux!<br>
<a href="http://www.nux.ro" target="_blank">www.nux.ro</a><br>
______________________________<u></u>_________________<br>
cloud mailing list<br>
<a href="mailto:cloud@lists.fedoraproject.org" target="_blank">cloud@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/cloud" target="_blank">https://admin.fedoraproject.<u></u>org/mailman/listinfo/cloud</a><br>
</font></span></blockquote></div><br></div>