[openstack-dev] [cinder] adding a new /v3 endpoint for api-microversions

Knight, Clinton Clinton.Knight at netapp.com
Mon Feb 22 14:46:09 UTC 2016

On 2/22/16, 9:33 AM, "Sean McGinnis" <sean.mcginnis at gmx.com> wrote:

>On Sun, Feb 21, 2016 at 07:59:17PM +0200, Duncan Thomas wrote:
>> So we can't get users to change endpoints, or write our libraries to
>> sensible defaults, but we're somehow going to magically get consumers
>>to do
>> the much harder job of doing version probes in their code/libraries so
>> they don't get surprised by unexpected results? This seems to be
>> nuts. If 'they' can't change endpoints (and we can't make the libraries
>> write just do the right thing without needing to change endpoints) then
>> are 'they' expected to do the probing magic that will be required at
>> unpredictable poin tin the future, but which you'll get away without
>> then?
>> This would also make us inconsistent with the other projects that have
>> implemented microversions - so we're changing a known working pattern,
>> try to avoid the problem of a user having to get their settings right if
>> they want new functionality, and hoping this doesn't introduce entirely
>> predictable and foreseeable bugs in the future that can't actually be
>> except by checking/changing every client library out there? There's no
>> that's a sensible API design.
>> --
>> Duncan Thomas
>I've spent the weekend thoroughly convincing myself one way or the
>other. The reality is, either one can _work_.
>I've asked Scott to proceed with the /v3 endpoint though. Ultimately,
>that is the safest route we can take to protect end users from
>accidentally doing something bad.
>A key thing here is that /v2 is not going away. So to an end user that
>doesn't know or doesn't care, things will just keep on working the way
>it has always worked and they don't need to worry.
>As far as the argument that some folks are still using /v1 - from my
>perspective they will need to migrate any way. So whether that is going
>to /v2 or /v3, it really won't make much of a difference there.

Ideally it would make no difference.  Like we did in Manila, you can
document for users that /v3 at the 3.0 microversion is functionally
identical to /v2.  So anyone still on /v1 can jump to /v3 with no extra
effort over /v2.


>Sean (smcginnis)
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>>OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>OpenStack Development Mailing List (not for usage questions)
>Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe

More information about the OpenStack-dev mailing list