Hide Forgot
Description of problem: Would like to know deployment of keystone v3 using RHOSP 9 , Right now default deployment still show as V2. Need to manually change to v3 after deployment. Version-Release number of selected component (if applicable): RHOSP9 How reproducible: Deployment of RHOSP9 Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Would appreciate if you could help us to know how to deploy with keystone v3 endpoints
So, unfortunately not all services support keystone v3. what you could do is configure cinder and nova to use keystone v3. And add a v3 endpoint in a further step. So to configure cinder and nova, you would have an environment file with the following content: parameter_defaults: NovaComputeExtraConfig: nova::keystone::authtoken::auth_version: v3 cinder::keystone::authtoken::auth_version: v3 controllerExtraConfig: nova::keystone::authtoken::auth_version: v3 cinder::keystone::authtoken::auth_version: v3 and finally after the deployment you could manually add the keystone endpoint. OSP11 and specially 12 have better support for keystone v3 though.
The real answer for this issue is to use a more current OSP version if you want broad v3 support. There has been a shift towards v3 as a default, and v2 support has even been removed in the upstream Queens release. If you need to configure services for v3 (where it is a service that actually supports v3), you can follow the directions in comment#2. Closing this as CURRENTRELEASE.