Description of problem:
For mitaka , there is new V3 endpoint and devstack support for v3.
- Test all new cinder features using the Vc3 api (cinder client)
- Decide if we should make it default going forward in OSP9
$ cinder --os-volume-api-version 3.1 --api-version
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Is there any dependencies for v3 API in JS6.0?
That is the recommended API now (although the base v3 is exactly the same as v2 if you’re not using microversions), but there is no impact on our drivers. Its really optional
Eric - can you confirm v3 is the default for OSP-10? once we confirm v3 is already the default for OSP10, I think we can close this one out.
Rajini - I would like remove the JS6 dependency. Is there any other reason this bug was marked as a blocker for the others 3 in addition to the JS6 tracker?
(In reply to Paul Grist from comment #5)
> Eric - can you confirm v3 is the default for OSP-10? once we confirm v3 is
> already the default for OSP10, I think we can close this one out.
Yes, Cinder ships with v3 enabled for OSP10. Director will need to create an endpoint for it.
Your merged patch at https://github.com/openstack/tripleo-heat-templates/commit/1e7bab9653afe37c1e87242c227b45530d013814 appears to address this issue. Can you verify that this patch successfully creates the endpoints for Cinder's v3 API in Keystone?
Thanks for your work!
that patch only partly addresses the issue. However, the issue should be addressed by this commit which has merged already https://github.com/openstack/tripleo-heat-templates/commit/f34c6a601317b7783885eed6ce16927d7e9337d8 this enabled the creation of the keystone endpoints via puppet, and thus will create the cinder_v3 endpoint with the info provided by the commit you mentioned
Per josorior, this bug is addressed in the current build of TripleO. Marking as MODIFIED in the current build.
Is api v3 should already be as the default option?
As you can see from api.log the default is still v2
2016-10-26 16:20:18.501 31610 INFO eventlet.wsgi.server [req-20f185dc-31a9-455f-86f7-1999f22c7c4c 47360029279740eebb60219fab042b52 2783390679524d3d97a70e10c8f7656b - default default] 172.17.1.18 "GET /v2/2783390679524d3d97a70e10c8f7656b/volumes/detail HTTP/1.1" status: 200 len: 253 time: 0.7082100
(In reply to lkuchlan from comment #13)
> Is api v3 should already be as the default option?
> As you can see from api.log the default is still v2
> From cinder/api.log:
> 2016-10-26 16:20:18.501 31610 INFO eventlet.wsgi.server
> [req-20f185dc-31a9-455f-86f7-1999f22c7c4c 47360029279740eebb60219fab042b52
> 2783390679524d3d97a70e10c8f7656b - default default] 172.17.1.18 "GET
> /v2/2783390679524d3d97a70e10c8f7656b/volumes/detail HTTP/1.1" status: 200
> len: 253 time: 0.7082100
You will have to opt in to the v3 API by adding "--os-volume-api-version 3" to the cinder CLI command. The client uses still v2 by default.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.