<font face="arial" size="2"><p>Eldar,</p>
<p> </p>
<p>I'm having some trouble finding the diff for your implementation of approach #1. Any chance you can share it on the list?</p>
<p> </p>
<p>Thanks</p>
<p> </p>
<p>"Erik Carlin" <erik.carlin@rackspace.com> said:<br /><br />> Cool. Got it. Floating IPs or what Amazon calls Elastic IPs. How are you<br />> solving the cross L2 problem?<br />> <br />> Erik<br />> <br />> Sent from my iPhone<br />> <br />> On Apr 15, 2011, at 7:28 PM, "Eldar Nugaev" <enugaev@griddynamics.com><br />> wrote:<br />> <br />> > Hi Erik<br />> ><br />> > Thank you for response!<br />> > Yes, you are absolutely right OpenStack API already support shared IP<br />> groups.<br />> > Suppose there are some misunderstanding, because I wrote about floating IPs.<br />> ><br />> > I want to have API for association IPs from floating IPs pool with<br />> > particular VM.<br />> ><br />> > At this moment we have #1 implementation as a path in our RPM repo<br />> > http://yum.griddynamics.net/. And going to make the merge proposal to<br />> > trunk.<br />> ><br />> > Also we going to create blueprint about #3 and attach branch to it.<br />> ><br />> > Eldar<br />> ><br />> > On Sat, Apr 16, 2011 at 2:34 AM, Erik Carlin<br />> <erik.carlin@rackspace.com> wrote:<br />> >> Eldar -<br />> >><br />> >> The OpenStack API already supports sharing IPs between instances<br />> (although<br />> >> this may be an extension?). What exact behavior are you after? More<br />> >> important than the way in which we expose via the API is how it's<br />> >> implemented. It's important to note that this is extremely network<br />> >> topology dependent. Sharing IPs today requires L2 adjacency so other<br />> VMs<br />> >> can GARP for the IP. L2 doesn't work at scale so you need another<br />> >> mechanism. I'm pretty sure the way AWS does it is to have a separate<br />> pool<br />> >> of IPs and inject /32 routes higher up that route towards the<br />> appropriate<br />> >> VM IP. What are your thoughts around how this would be implemented?<br />> >><br />> >> Multiple people are working towards an independent Network as a Service<br />> >> external to nova so it may make sense to plug this requirement in there.<br />> >><br />> >> Erik<br />> >><br />> >> On 4/11/11 8:31 AM, "Eldar Nugaev" <enugaev@griddynamics.com><br />> wrote:<br />> >><br />> >>> Hello everyone,<br />> >>><br />> >>> We going to add possibility to assigning floating IP addresses in<br />> >>> OpenStack API.<br />> >>> Our goal reproduce AWS behavior when creating instance automatically<br />> >>> assigns any free floating IP or add methods to OpenStack API for<br />> >>> allocation and association API addresses.<br />> >>><br />> >>> At this time we see three way:<br />> >>><br />> >>> 1. FLAG --auto_assign_floating_ip (default=False)<br />> >>> 2. Optional parameter "auto_assign_floating_ip" in existing "create"<br />> >>> method<br />> >>> 3. OpenStack API add floating_ip - allocate_floating_ip,<br />> >>> associate_floating_ip<br />> >>><br />> >>> What way is more suitable at this time?<br />> >>><br />> >>> --<br />> >>> Eldar<br />> >>> Skype: eldar.nugaev<br />> >>><br />> >>> _______________________________________________<br />> >>> Mailing list: https://launchpad.net/~openstack<br />> >>> Post to : openstack@lists.launchpad.net<br />> >>> Unsubscribe : https://launchpad.net/~openstack<br />> >>> More help : https://help.launchpad.net/ListHelp<br />> >><br />> >><br />> >><br />> >> Confidentiality Notice: This e-mail message (including any attached or<br />> >> embedded documents) is intended for the exclusive and confidential use of<br />> the<br />> >> individual or entity to which this message is addressed, and unless<br />> otherwise<br />> >> expressly indicated, is confidential and privileged information of<br />> Rackspace.<br />> >> Any dissemination, distribution or copying of the enclosed material is<br />> prohibited.<br />> >> If you receive this transmission in error, please notify us immediately<br />> by e-mail<br />> >> at abuse@rackspace.com, and delete the original message.<br />> >> Your cooperation is appreciated.<br />> >><br />> >><br />> ><br />> ><br />> ><br />> > --<br />> > Eldar<br />> > Skype: eldar.nugaev<br />> <br />> <br />> Confidentiality Notice: This e-mail message (including any attached or<br />> embedded documents) is intended for the exclusive and confidential use of the<br />> individual or entity to which this message is addressed, and unless otherwise<br />> expressly indicated, is confidential and privileged information of Rackspace.<br />> Any dissemination, distribution or copying of the enclosed material is<br />> prohibited.<br />> If you receive this transmission in error, please notify us immediately by e-mail<br />> at abuse@rackspace.com, and delete the original message.<br />> Your cooperation is appreciated.<br />> <br />> <br />> _______________________________________________<br />> Mailing list: https://launchpad.net/~openstack<br />> Post to : openstack@lists.launchpad.net<br />> Unsubscribe : https://launchpad.net/~openstack<br />> More help : https://help.launchpad.net/ListHelp<br />></p></font>