Bug 1388255

Summary:	Disable tripleo update on already created overcloud nodes during scale out
Product:	Red Hat OpenStack	Reporter:	Andreas Karis <akaris>
Component:	openstack-tripleo	Assignee:	Brad P. Crochet <brad>
Status:	CLOSED WONTFIX	QA Contact:	Arik Chernetsky <achernet>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	akaris, aschultz, brad, jbuchta, mburns, mcornea, morazi, pneedle, rhel-osp-director-maint, sputhenp
Target Milestone:	async	Flags:	aschultz: needinfo? (akaris)
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-01 16:46:19 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 Andreas Karis 2016-10-24 21:18:14 UTC

Description of problem:
Looking for a way to disable tripleo update on already created overcloud nodes during a scale out of nodes with OpenStack Director. Director should only deploy new nodes (CREATE) and modify mapping in /etc/hosts on all nodes

Version-Release number of selected component (if applicable):
OSP 7

Additional info:
The customer does not seem to use Director to update existing nodes - they do have ansible to do so, and would prefer to continue to use ansible.