← Back to team overview

openstack team mailing list archive

Re: Floating IP in OpenStack API

 

Eldar -

The OpenStack API already supports sharing IPs between instances (although
this may be an extension?).  What exact behavior are you after?  More
important than the way in which we expose via the API is how it's
implemented.  It's important to note that this is extremely network
topology dependent.  Sharing IPs today requires L2 adjacency so other VMs
can GARP for the IP.  L2 doesn't work at scale so you need another
mechanism.  I'm pretty sure the way AWS does it is to have a separate pool
of IPs and inject /32 routes higher up that route towards the appropriate
VM IP.  What are your thoughts around how this would be implemented?

Multiple people are working towards an independent Network as a Service
external to nova so it may make sense to plug this requirement in there.

Erik

On 4/11/11 8:31 AM, "Eldar Nugaev" <enugaev@xxxxxxxxxxxxxxxx> wrote:

>Hello everyone,
>
>We going to add possibility to assigning floating IP addresses in
>OpenStack API.
>Our goal reproduce AWS behavior when creating instance automatically
>assigns any free floating IP or add methods to OpenStack API for
>allocation and association API addresses.
>
>At this time we see three way:
>
>1. FLAG --auto_assign_floating_ip (default=False)
>2. Optional parameter "auto_assign_floating_ip" in existing "create"
>method
>3. OpenStack API add floating_ip - allocate_floating_ip,
>associate_floating_ip
>
>What way is more suitable at this time?
>
>-- 
>Eldar
>Skype: eldar.nugaev
>
>_______________________________________________
>Mailing list: https://launchpad.net/~openstack
>Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~openstack
>More help   : https://help.launchpad.net/ListHelp



Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@xxxxxxxxxxxxx, and delete the original message.
Your cooperation is appreciated.




Follow ups

References