From: Aaron Rosen <<>>
Reply-To: OpenStack List 
Date: Wednesday, August 6, 2014 at 10:09 AM
To: OpenStack List 
Subject: Re: [openstack-dev] [Neutron] Group Based Policy and the way forward

On Tue, Aug 5, 2014 at 11:18 PM, Gary Kotton 
<<>> wrote:

On 8/5/14, 8:53 PM, "Russell Bryant" 
<<>> wrote:

>On 08/05/2014 01:23 PM, Gary Kotton wrote:
>> Ok, thanks for the clarification. This means that it will not be done
>> automagically as it is today ­ the tenant will need to create a Neutron
>> port and then pass that through.
>FWIW, that's the direction we've wanted to move in Nova anyway.  We'd
>like to get rid of automatic port creation, but can't do that in the
>current stable API.

Can you elaborate on what you mean here? What are the issues with port

Having nova-compute create ports for neutron is problematic if timeouts occur 
between nova and neutron as you have to garbage collect neutron ports in nova 
to cleanup (which was the cause of several bug in the cache handing allowing 
ports to leak into the info_cache in nova).  Pushing this out to the tenant is 
less orchestration nova has to do.

[gary] my take on this is that we should allocate this via the n-api and not 
via the nova compute (which is far too late in the process. But that is another 
discussion :)

>Russell Bryant
>OpenStack-dev mailing list

OpenStack-dev mailing list<>

OpenStack-dev mailing list

Reply via email to