Bug 1396229

Summary:	[RFE] Clarify Custom Overcloud Naming and Impact on overcloudrc
Product:	Red Hat OpenStack	Reporter:	Bradford Nichols <bradnichols>
Component:	python-tripleoclient	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Amit Ugol <augol>
Severity:	medium	Docs Contact:
Priority:	low
Version:	unspecified	CC:	aschultz, augol, bradnichols, brad, dbecker, dmatthew, hbrock, jcoufal, jschluet, jslagle, mbarnett, mburns, morazi, rbrady, rhel-osp-director-maint, rhos-flags, ukalifon
Target Milestone:	z3	Keywords:	FutureFeature, TestOnly, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tripleoclient-9.2.0-2.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-11-27 11:46:27 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 Bradford Nichols 2016-11-17 18:25:26 UTC

As part of the recovery and rebuild of a cloud, or deployment of a new cloud form the same undercloud,  a new name can be chosen for the cloud. This lead to the overcloudrc file of endpoints to be renamed as well. This caused some confusion. 

a. Enhance the documentation to indicate that the name of the overcloudrc file is dependent on the cloud name 
Make sure it is clear that changing cloud name results in a new name for the overcloudrc

b. Print out the name of the resulting overcloudrc file at the end of the deployment for the user 

c. Put a standard prefix on all overcloudrc files so that they are always easily identifable for what they are
For example automatically name all overcloud rcfiles ‘overcloud<stackname if not ‘overcloud’>rc.

Existing resources:
https://access.redhat.com/solutions/2709791 After openstack overcloud deploy of an overcloud with a non-default name, cannot find overcloudrc file

Comment 1 Alex Schultz 2017-08-02 15:06:35 UTC

So the default stack name is overcloud which results in overcloudrc. It seems that we should just display the generated filename in a summary at the end of the deployment similar to what we do for the undercloud to clear up this configuration.

Comment 9 Dougal Matthews 2018-06-13 09:46:24 UTC

Upstream this was resolved by outputting the rc file location at the end of a deployment. Is that satisfactory?

Comment 11 Jon Schlueter 2018-06-27 17:23:48 UTC

According to our records, this should be resolved by python-tripleoclient-9.2.1-12.el7ost.  This build is available now.

Comment 13 Bradford Nichols 2018-07-02 17:19:48 UTC

To the questions in #9, yes this is satisfactory.

Comment 15 Ryan Brady 2018-08-20 13:59:23 UTC

Amit, as the QA contact can you provide the QA_Ack?

Comment 16 Ryan Brady 2018-08-20 14:00:13 UTC

Michael, this bug requires a PM_ACK.

Comment 19 Udi Kalifon 2018-11-27 08:29:38 UTC

Verified:
openstack-tripleo-common-8.6.6-2.el7ost.noarch
python-tripleoclient-9.2.6-2.el7ost.noarch

 Stack hahaha CREATE_COMPLETE

Started Mistral Workflow tripleo.deployment.v1.get_horizon_url. Execution ID: b5e3eba3-27fb-4ace-aabc-0f6b9fd09ea6
Overcloud Endpoint: https://10.0.0.101:13000/
Overcloud Horizon Dashboard URL: https://10.0.0.101:443/dashboard
Overcloud rc file: /home/stack/hahaharc
Overcloud Deployed