[openstack-dev] [nova] Volume attachment APIs CRUD inconsistencies
annegentle at justwriteclick.com
Sat Dec 12 02:38:06 UTC 2015
On Fri, Dec 11, 2015 at 7:33 PM, Matt Riedemann <mriedem at linux.vnet.ibm.com>
> On 12/11/2015 1:48 PM, Sam Matzek wrote:
>> The CRUD operations for Nova volume attachments have inconsistencies
>> between documentation and implementation. Additionally, the read/get
>> operation is implemented twice under different URIs. What is Nova's
>> direction for volume attachment APIs and how should the following
>> discrepancies be resolved?
>> The current state of affairs is:
>> CREATE (volume attach) is documented twice under two different URIs: 
>> and , but only os-volume_attachments  is implemented .
Matt, can you look a little deeper into what happened to
os-volume_attachments? I'm worried we've missed one of the extensions.
As for the docs, I thought we put in redirects from v2 to v2.1 but I need
> Attach volume as an action on the servers URI appears to have been part
>> of the Nova V3 API, but its implementation no longer exists.
>> Is it the future direction to have volume attach and detach done as
>> server actions?
>> READ is implemented twice and documented twice under two different URIs:
>> os-volume_attachments  and server details 
>> The two implementations do not return the same information and the only
>> bit of information that is common between them is the volume ID.
>> Why do we have two implementations and is one preferred over the other?
>> Should one be deprecated and eventually removed with all enhancements
>> going into the other?
>> UPDATE is implemented  but not documented.
>> DELETE (detach) only appears to be implemented and documented once: 
>> A blueprint proposal exists  to enhance the attach and update APIs to
>> set and modify the delete_on_termination flag. The discrepancies in the
>> create and read operations calls into question whether the update change
>> should be on the PUT /servers API to match the server's read  or if
>> the os-volume_attachments update API should be modified to line up with
>> os-volume_attachments read.
>>  http://developer.openstack.org/api-ref-compute-v2.1.html#attach
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> Several of the different paths you're pointing out are v2 legacy (e.g.
> anything with *-v2-ext.html). Anything with v2.1 is, well, the v2.1 API and
> is current.
> The code is very similar in most cases between v2 and v2.1. The main
> differences with v2.1 are (1) jsonschema validation on the front-end and
> (2) microversion support. More info is here .
> As for docs, there are a lot of missing docs or incorrect docs in the
> compute API. There is an etherpad  on gaps to fill there, patches are
>  http://docs.openstack.org/developer/nova/#compute-api-references
>  https://etherpad.openstack.org/p/nova-v2.1-api-doc
> Matt Riedemann
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev