Bug 1392075

Summary:	deployment of RHOSP 9 with keystone v3
Product:	Red Hat OpenStack	Reporter:	bigswitch <rhosp-bugs-internal>
Component:	rhosp-director	Assignee:	Angus Thomas <athomas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Amit Ugol <augol>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0 (Mitaka)	CC:	dbecker, josorior, mburns, morazi, nkinder, rhel-osp-director-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-11-21 19:40:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description bigswitch 2016-11-04 18:13:47 UTC

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:

Comment 1 bigswitch 2016-11-16 18:56:57 UTC

Would appreciate if you could help us to know how to deploy with keystone v3 endpoints

Comment 2 Juan Antonio Osorio 2017-10-31 15:15:02 UTC

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.

Comment 3 Nathan Kinder 2017-11-21 19:40:48 UTC

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.