Open Stack

From: Aaron Rosen <aaronorosen at gmail.com<mailto:aaronorosen at gmail.com>>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, August 6, 2014 at 11:11 AM
To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] Group Based Policy and the way forward




On Wed, Aug 6, 2014 at 12:59 AM, Gary Kotton <gkotton at vmware.com<mailto:gkotton at vmware.com>> wrote:


From: Aaron Rosen <aaronorosen at gmail.com<mailto:aaronorosen at gmail.com>>
Reply-To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, August 6, 2014 at 10:09 AM

To: OpenStack List <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] Group Based Policy and the way forward


On Tue, Aug 5, 2014 at 11:18 PM, Gary Kotton <gkotton at vmware.com<mailto:gkotton at vmware.com>> wrote:


On 8/5/14, 8:53 PM, "Russell Bryant" <rbryant at redhat.com<mailto:rbryant at redhat.com>> 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
creation?


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 :)

I agree, I had actually proposed this here: https://blueprints.launchpad.net/nova/+spec/nova-api-quantum-create-port<https://urldefense.proofpoint.com/v1/url?u=https://blueprints.launchpad.net/nova/%2Bspec/nova-api-quantum-create-port&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=eH0pxTUZo8NPZyF6hgoMQu%2BfDtysg45MkPhCZFxPEq8%3D%0A&m=nxi%2BsVOGOwFKN8cKE9T4thh6hF%2Fbbz59EZEBQvd1lkE%3D%0A&s=50f7fe08f64d0d647ee97a8da6f91091e380cca72e84d06fa9c57c62dbb4e4ee>  :),   though there are some issues we need to solve in neutron first -- allowing the mac_address on the port to be updated in neutron. This is required for bare metal support as when the port is created we don't know which physical mac will need to be mapped to the port.

[gary] agreed

>
>--
>Russell Bryant
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140806/dc841886/attachment.html>