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.
However, it is unlikely that feature will be backported.
For Havana users, the best workaround so far, in my opinion, is:
1) create a port on a subnet connected to a router
Note: the router must have a gateway set
2) create a floating IP on the external network associating it to the port
created at #1
Note: the external network must be the same at the one where the
router's gateway is connected
3) boot the VM using the port created at #1 (--nic port-id=xxx)
Regards,
Salvatore
On 10 December 2013 16:50, Rick Jones <rick.jon...@hp.com> wrote:
> On 12/10/2013 12:29 AM, Jitendra Kumar Bhaskar wrote:
>
>> I am doing d same but I am looking to attach floating IP at boot time.
>> And not getting where I need to change ?
>>
>
> 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.
>
> Then I suspect the chances are reasonably good that as the guest OS boots
> in the instance, the floater will be associated.
>
> rick jones
> agrees though that "full automagic" would be nice.
>
>
>> Regards*
>> Jitendra Bhaskar*
>>
>>
>>
>>
>>
>>
>>
>> On Tue, Dec 10, 2013 at 12:45 PM, 郭龙仓 <guolongcang.w...@gmail.com
>> <mailto:guolongcang.w...@gmail.com>> wrote:
>>
>> floating ip is implemented through NAT , so , once your instance was
>> assigned an internal ip successfully , then you can assign floating
>> ip to it . but , in order to assign floating IP to instance at boot
>> time, maybe you need to modify some code.
>>
>>
>> 2013/12/9 Jitendra Kumar Bhaskar <jitendr...@pramati.com
>> <mailto:jitendr...@pramati.com>>
>>
>>
>> Hi Stackers
>>
>> Is it possible to assign floating IP to instance at boot time in
>> Hanana ?
>>
>> Regards*
>> Jitendra Bhaskar*
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> <mailto:openstack@lists.openstack.org>
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
>> openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
>> openstack
>>
>>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
