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

Sean McGinnis sean.mcginnis at gmx.com
Mon Feb 22 14:22:18 UTC 2016

On Mon, Feb 22, 2016 at 12:40:48PM +0800, Thomas Goirand wrote:
> I'd vote for the extra round trip and implementation of caching whenever
> possible. Using another endpoint is really annoying, I already have
> specific stuff for cinder to setup both v1 and v2 endpoint, as v2
> doesn't fully implements what's in v1. BTW, where are we with this? Can
> I fully get rid of the v1 endpoint, or will I still experience some
> Tempest failures?
> Thomas Goirand (zigo)

This would really surprise me as /v2 was mostly a full copy of /v1, to
some degree. If you see anything missing please file a bug. I am not
aware of anything myself.

/v1 would have been gone by know according to our original deprecation
plan. We've since realized we can't ever fully get rid of it, but there
should be no reason to still need to set it up if you have v2.

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

More information about the OpenStack-dev mailing list