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

Arkady_Kanevsky at DELL.com Arkady_Kanevsky at DELL.com
Mon Feb 22 01:39:37 UTC 2016

With nova and Keystone both at v3 is helps to consistent versioning across all projects.
Still need documentation for transition clients from one API version to next.
With new functionality not available in previous version it should be easier than API changes.

-----Original Message-----
From: Walter A. Boring IV [mailto:walter.boring at hpe.com]
Sent: Friday, February 19, 2016 4:18 PM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [cinder] adding a new /v3 endpoint for api-microversions

>> But, there are no such clients today. And there is no library that
>> does this yet. It will be 4 - 6 months (or even more likely 12+)
>> until that's in the ecosystem. Which is why adding the header
>> validation to existing
>> v2 API, and backporting to liberty / kilo, will provide really
>> substantial coverage for the concern the bswartz is bringing forward.
> Yeah, I have to agree with that. We can certainly have the protection
> out in time.
> The only concern there is the admin who set up his Kilo initial
> release cloud and doesn't want to touch it for updates. But they
> likely have more pressing issues than this any way.
>> -Sean

Not that I'm adding much to this conversation that hasn't been said already, but I am pro v2 API, purely because of how painful and long it's been to get the official OpenStack projects to adopt the v2 API from v1. I know we need to be sort of concerned about other 'client's
that call the API, but for me that's way down the lists of concerns.
If we go to v3 API, most likely it's going to be another 3+ years before folks can use the new Cinder features that the microversioned changes will provides. This in effect invalidates the microversion capability in Cinder's API completely.


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...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160222/1cff8537/attachment.html>

More information about the OpenStack-dev mailing list