Bug 1485413

Summary:	[RFE] Fast Forward Upgrade RHOSP10 to RHOSP13
Product:	Red Hat OpenStack	Reporter:	Maria Bracho <mbracho>
Component:	rhosp-director	Assignee:	Lukas Bezdicka <lbezdick>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Marius Cornea <mcornea>
Severity:	high	Docs Contact:
Priority:	high
Version:	13.0 (Queens)	CC:	achernet, asimonel, brault, ccamacho, dbecker, ealcaniz, lyarwood, mbracho, mburns, mcornea, morazi, pmorey, rhel-osp-director-maint, sathlang, sclewis, smerrow, srelf, vcojot, yroblamo
Target Milestone:	zstream	Keywords:	FutureFeature, Triaged, ZStream
Target Release:	13.0 (Queens)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-03 11:33:59 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:
Bug Depends On:	1488566, 1523776, 1539052, 1556992, 1566294
Bug Blocks:	1419948, 1458798, 1465537, 1466922, 1488065, 1488066, 1488067, 1488068, 1488069, 1508762, 1541050, 1541051, 1541053, 1541054, 1541056, 1544752

Description Maria Bracho 2017-08-25 15:37:58 UTC

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Red Hat Bugzilla Rules Engine 2017-10-04 15:42:59 UTC

This bugzilla has been removed from the release and needs to be reviewed for Triaging and release planning for an appropriate Target Milestone.

Comment 7 Maria Bracho 2017-11-16 13:37:58 UTC

Description of the request:
As a customer, I want to upgrade between long life releases RHOSP 10 to RHOSP 13. 

The solution shall include steps that can be controlled by the operator to plan for minimum disruption during specific time windows. Upgrading in place with the same equipment is necessary when the logistics and resources to acquire additional hardware are prohibitive. Upgrading to a supported version of OpenStack (RHOSP 13) is the main goal, given the Long Life release approach, this requires not stopping the upgrade in RHOSP 11 or 12. In case the Fast Forward Upgrade is not successful, the operator shall follow steps to return to the starting point RHOSP 10 for another attempt.
Key customers (particularly Telcos) require approaches with minimum downtime. 

Version-Release number of selected component (if applicable):
RHOSP 10, RHOSP 13

Comment 8 Maria Bracho 2017-11-16 13:38:14 UTC

Description of the request:
As a customer, I want to upgrade between long life releases RHOSP 10 to RHOSP 13. 

The solution shall include steps that can be controlled by the operator to plan for minimum disruption during specific time windows. Upgrading in place with the same equipment is necessary when the logistics and resources to acquire additional hardware are prohibitive. Upgrading to a supported version of OpenStack (RHOSP 13) is the main goal, given the Long Life release approach, this requires not stopping the upgrade in RHOSP 11 or 12. In case the Fast Forward Upgrade is not successful, the operator shall follow steps to return to the starting point RHOSP 10 for another attempt.
Key customers (particularly Telcos) require approaches with minimum downtime. 

Version-Release number of selected component (if applicable):
RHOSP 10, RHOSP 13

Comment 19 Martin Magr 2018-07-17 12:36:45 UTC

*** Bug 1466922 has been marked as a duplicate of this bug. ***