Bug 1261633

Summary:	RFE: enable users to change hostnames for overcloud deployments
Product:	Red Hat OpenStack	Reporter:	Jon Thomas <jthomas>
Component:	python-rdomanager-oscplugin	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	yeylon <yeylon>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	hbrock, jraju, jslagle, mburns, racedoro, rhel-osp-director-maint, srevivo, vaggarwa
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-11 11:36:21 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:
Embargoed:

Description Jon Thomas 2015-09-09 19:33:00 UTC

Need to be able to set the overcloud name either via template or command line in order to customize hostnames. Currently it is hardcoded to be "overcloud".


This looks like a cross component rfe. It looks like at least these locations are hardcoded for overcloud. 
 

/usr/lib/python2.7/site-packages/rdomanager_oscplugin/v1/overcloud_deploy.py:409:        stack_name = "overcloud"
/usr/lib/python2.7/site-packages/rdomanager_oscplugin/v1/overcloud_deploy.py:438:            orchestration_client, "overcloud")
/usr/lib/python2.7/site-packages/rdomanager_oscplugin/v1/overcloud_deploy.py:587:            'OS_CLOUDNAME': 'overcloud',

Changing these and it appears the install succeeds up until cloud init finishes and puppet starts. So likely there is something in puppet templates that needs to be changed.

Comment 3 Jon Thomas 2015-09-09 19:37:21 UTC

related https://bugzilla.redhat.com/show_bug.cgi?id=1259003

Comment 9 Mike Burns 2016-04-07 20:50:54 UTC

This bug did not make the OSP 8.0 release.  It is being deferred to OSP 10.

Comment 11 Mike Burns 2016-04-11 11:36:21 UTC


*** This bug has been marked as a duplicate of bug 1278854 ***