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

Walter A. Boring IV walter.boring at hpe.com
Mon Feb 22 16:50:20 UTC 2016

On 02/20/2016 02:42 PM, Duncan Thomas wrote:
> On 20 Feb 2016 00:21, "Walter A. Boring IV" <walter.boring at hpe.com 
> <mailto:walter.boring at hpe.com>> wrote:
> > 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 think there's a slightly different argument here. We aren't taking 
> away the v2 API, probably ever. Clients that are satisfied with it can 
> continue to use it, as it is, forever. For clients that aren't trying 
> to do anything beyond the current basics will quite possibly be happy 
> with that. Consumers have no reason to change over without compelling 
> value from the change - that will come from what we implement on top 
> of microversions, or not. Unlike the v1 transition, we aren't trying 
> to get rid of v2, just stop changing existing semantics of it.

I'm more concerned with us not getting OpenStack projects themselves to 
not use the new features/fixes we are going to make after microversions 
land.  If we force folks to use a new endpoint, then it's the same 
problem we had getting OS projects to migrate from v1 to v2.  That took 
years.   :(

> __________________________________________________________________________
> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160222/272f5e28/attachment.html>

More information about the OpenStack-dev mailing list