<div dir="ltr">This feature will be available in neutron for the Icehouse release, and will cause a floating IP to be created everytime a VM is booted.<div>However, it is unlikely that feature will be backported.</div><div>
<br></div><div>For Havana users, the best workaround so far, in my opinion, is:</div><div>1) create a port on a subnet connected to a router</div><div> Note: the router must have a gateway set</div><div>2) create a floating IP on the external network associating it to the port created at #1</div>
<div> Note: the external network must be the same at the one where the router's gateway is connected</div><div>3) boot the VM using the port created at #1 (--nic port-id=xxx)</div><div><br></div><div>Regards,</div>
<div>Salvatore</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 10 December 2013 16:50, Rick Jones <span dir="ltr"><<a href="mailto:rick.jones2@hp.com" target="_blank">rick.jones2@hp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 12/10/2013 12:29 AM, Jitendra Kumar Bhaskar wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am doing d same but I am looking to attach floating IP at boot time.<br>
And not getting where I need to change ?<br>
</blockquote>
<br></div>
It would not be "automagic" but rather than have nova allocate the port out of neutron, you can instead allocate the port yourself explicitly via neutron, then pass that port id through the floatingip-create and then boot the instance with that port id rather than with the network id.<br>
<br>
Then I suspect the chances are reasonably good that as the guest OS boots in the instance, the floater will be associated.<br>
<br>
rick jones<br>
agrees though that "full automagic" would be nice.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Regards*<br>
Jitendra Bhaskar*<div class="im"><br>
<br>
<br>
<br>
<br>
<br>
<br>
On Tue, Dec 10, 2013 at 12:45 PM, 郭龙仓 <<a href="mailto:guolongcang.work@gmail.com" target="_blank">guolongcang.work@gmail.com</a><br></div><div class="im">
<mailto:<a href="mailto:guolongcang.work@gmail.com" target="_blank">guolongcang.work@<u></u>gmail.com</a>>> wrote:<br>
<br>
floating ip is implemented through NAT , so , once your instance was<br>
assigned an internal ip successfully , then you can assign floating<br>
ip to it . but , in order to assign floating IP to instance at boot<br>
time, maybe you need to modify some code.<br>
<br>
<br>
2013/12/9 Jitendra Kumar Bhaskar <<a href="mailto:jitendra.b@pramati.com" target="_blank">jitendra.b@pramati.com</a><br></div>
<mailto:<a href="mailto:jitendra.b@pramati.com" target="_blank">jitendra.b@pramati.com</a><u></u>>><div class="im"><br>
<br>
Hi Stackers<br>
<br>
Is it possible to assign floating IP to instance at boot time in<br>
Hanana ?<br>
<br></div>
Regards*<br>
Jitendra Bhaskar*<div class="im"><br>
<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Mailing list:<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br></div>
<mailto:<a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.<u></u>openstack.org</a>><br>
Unsubscribe :<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><div class="im"><br>
<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
<br>
______________________________<u></u>_________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack</a><br>
</div></div></blockquote></div><br></div>