[openstack-dev] Fwd: Blueprint information
ravivsn at gmail.com
Wed Jul 31 17:41:40 UTC 2013
The blueprint proposed to assign auto floating IP during port creation.
Since auto floating IP is supported in nova-network, +1 to implement the
same in Neutron.
Can you share with us the concerns in implementing in Neutron?
On Wed, Jul 31, 2013 at 12:57 AM, Salvatore Orlando <sorlando at nicira.com>wrote:
> Hi Ofer,
> Basically this operation consists in ensuring that an instance, when it's
> booted, is also associated with a floating IP address, and therefore
> publicly accessible.
> I discussed this topic a couple months ago with another developer, but I
> am now unable to find the chat in the openstack-dev IRC logs.
> The bottom line is that even if this is registered as a neutron blueprint,
> we are not really sure Neutron is the right place to perform orchestration
> And this operation falls into this category - since it involves, creating
> a port, ensuring the network for that port is associated with a router,
> allocating a floating IP, and associating it with the port.
> Currently all the orchestration operations are performed in the module
> which configures instances networking, which is part of nova. This module
> (nova.network.quantumv2.api) uses the quantum API.
> I reckon this blueprint should be implemented there performing the
> operations listed above.
> On 28 July 2013 16:16, Ofer Blaut <oblaut at redhat.com> wrote:
>> Hi, I am interested in helping out with QE efforts on upstream
>> OpenStack, specifically around Neutron.
>> I'm trying to understand the following blueprint,can you please point me
>> to more detailed design
>> Ofer Blaut
>> 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