[openstack-dev] [nova] why do we have os-attach-interfaces in the v3 API?

Gary Kotton gkotton at vmware.com
Fri Oct 3 08:29:03 UTC 2014


Hi,
In the V2 API the attach interface is a blocking operation. This is
problematic. I posted a patch for the V3 to be non blocking -
https://review.openstack.org/#/c/103094/ (as we cannot break existing
API¹s). I would prefer that you do not remove the V3 api. I am not sure
what you mean by saying that we are not parodying to Neutron. The Neutron
API is invoked when the attach is done, that is, a Neutron port needs to
be created.
Thanks
Gary

On 10/2/14, 11:57 PM, "Matt Riedemann" <mriedem at linux.vnet.ibm.com> wrote:

>The os-interface (v2) and os-attach-interfaces (v3) APIs are only used
>for the neutron network API, you'll get a NotImplemented if trying to
>call the related methods with nova-network [1].
>
>Since we aren't proxying to neutron in the v3 API (v2.1), why does
>os-attach-interfaces [2] exist?  Was this just an oversight?  If so,
>please allow me to delete it. :)
>
>[1] 
>http://git.openstack.org/cgit/openstack/nova/tree/nova/network/api.py?id=2
>014.2.rc1#n310
>[2] 
>http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compu
>te/plugins/v3/attach_interfaces.py?id=2014.2.rc1
>
>-- 
>
>Thanks,
>
>Matt Riedemann
>
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




More information about the OpenStack-dev mailing list