Bug 1391705

Summary:	[RFE] The minor update process for overcloud should be allowed to run in phases.
Product:	Red Hat OpenStack	Reporter:	Alexander Chuzhoy <sasha>
Component:	rhosp-director	Assignee:	Lukas Bezdicka <lbezdick>
Status:	CLOSED DUPLICATE	QA Contact:	Amit Ugol <augol>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	11.0 (Ocata)	CC:	augol, dbecker, jcoufal, lbezdick, mburns, morazi, rhel-osp-director-maint, sathlang, sclewis, yprokule
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	12.0 (Pike)
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-03-13 05:10:43 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 Alexander Chuzhoy 2016-11-03 20:03:01 UTC

rhel-osp-director:   [RFE] The minor update process for overcloud should be allowed to run in phases.


Currently, the minor update is handled via single command. 
This makes it less convenient to check things in the middle of the update and pause/resume the update.
Would be great to have the option to split the update into phases, for example to have the option to run update for a subset of nodes or a single node.

Comment 1 Lukas Bezdicka 2016-12-19 15:08:29 UTC

Issue here is how to know when the update is for example security update that is only needed to run on compute nodes or update that has to run on multiple/all types of nodes as it has configuration change with dependencies?

Comment 9 Jaromir Coufal 2017-03-13 05:10:43 UTC

Merging two RFEs into one.

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