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
On 10/2/2014 10:30 PM, Christopher Yeoh wrote:
On Thu, 02 Oct 2014 15:57:55 -0500
Matt Riedemann mrie...@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
If you can add and delete interfaces it seems like being able to list them is
useful. You can get the info you need from the networks list when you get the
instance, but “nova interface-list” seems like a useful addition if we have
“interface-attach” and “interface-detach”, so in this case I
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
os-attach-interfacees is actually a a forward port of:
http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/contrib/attach_interfaces.py
which is a compute action that is valid for both nova-network and neutron:
On 10/2/2014 4:34 PM, Vishvananda Ishaya wrote:
os-attach-interfacees is actually a a forward port of:
http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/compute/contrib/attach_interfaces.py
which is a compute action that is valid for both nova-network and neutron:
On Thu, 02 Oct 2014 15:57:55 -0500
Matt Riedemann mrie...@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
