[openstack-dev] [Neutron] Blueprint -- Floating IP Auto Association
emagana at plumgrid.com
Thu Nov 14 18:27:52 UTC 2013
Thanks Steven for working on this topic!
I would prefer the second approach, although there were some discussions
during the summit about moving all calls to Neutron instead of having nova
Anyway, just providing my two cents
From: Salvatore Orlando <sorlando at nicira.com>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org>
Date: Thursday, November 14, 2013 3:21 AM
To: OpenStack List <openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [Neutron] Blueprint -- Floating IP Auto
I see three Steven Weston on Launchpad. If you give me your LP ID, I will
assign the blueprint to you.
This is a nova parity item and i'd like to raise the priority to High.
It would be also good to hear from you about the implementation approach.
In the past we debated two alternatives: passing a special attribute to a
port in order to create a floating IP for it too, or orchestrating the
operation from the nova side.
The first option has the cons of adding a side effect to a REST API call
(which is not advisable), and might be a bit complex when the network where
the port is on is attached to multiple routers.
The latter option has the cons of requiring two neutron API calls.
The input of the whole community on this topic will be very appreciated.
On 14 November 2013 05:47, Steven Weston <steven-weston at live.com> wrote:
> Thanks for the responses on this. I definitely still interested in
> implementing the functionality described in this blueprint, but have been
> reluctant to start on it since I did not get a response.
> Yes, please assign it to me and I will get started on it right away! I do not
> seem to have the capability to assign it to myself.
> From: Jaume Devesa [mailto:devvesa at gmail.com]
> Sent: Wednesday, November 13, 2013 10:32 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Neutron] Blueprint -- Floating IP Auto
> Hi all,
> I see it has been passed two weeks since first mail in this thread and that
> blueprint still without assignee. I also think this is a good option for my
> first blueprint. However, I can not assign blueprints to myself, only bugs.
> Can anybody assign to me?
> Steven: if you still interested in it, please tell us. You asked for it first
> and it will be yours.
> On 5 November 2013 07:21, Salvatore Orlando <sorlando at nicira.com> wrote:
>> I don't think there has been any development in the past 6 months.
>> A few people have shown interest in it in the past, but the blueprint has
>> currently no assignee.
>> So If you want to work on it, feel free to assign to yourself.
>> To quickly sum up the discussion around this blueprint, it could be
>> implemented in two ways:
>> - providing automation in the neutron API (creating the floating IP together
>> with the port)
>> - automating the operation on the orchestration side (nova-api in this case).
>> There are pro and cons in both solutions. In my humble opinion, the only
>> thing I would care of is that the existing operation in the Neutron API stay
>> "atomic" as they are.
>> On 30 October 2013 08:46, Steven Weston <steven-weston at live.com> wrote:
>>> Does anybody know what the status of this Blueprint is?
>>> I am new to the neutron developer community and I am looking for a first
>>> project this might be a good place to start. But the last update was in
>>> March of this year, so I don¹t know if the specifications have been locked
>>> down yet.
>>> Steven Weston
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
_______________________________________________ OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev