Bug 1419749

Summary: [RFE] Composable Minor Updates [for RHOSP12] (Ansible based, in composable fashion) (Ansible based, hybrid environment support)
Product: Red Hat OpenStack Reporter: Jaromir Coufal <jcoufal>
Component: rhosp-directorAssignee: mathieu bultel <mbultel>
Status: CLOSED CURRENTRELEASE QA Contact: Yurii Prokulevych <yprokule>
Severity: unspecified Docs Contact:
Priority: high    
Version: 12.0 (Pike)CC: achernet, augol, dbecker, egafford, jschluet, mandreou, mburns, mcornea, morazi, rhel-osp-director-maint, sasha, sathlang, sbaker, sclewis, shardy, tvignaud
Target Milestone: Upstream M3Keywords: FutureFeature, ZStream
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: 2018-02-01 17:04:47 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: 1447127    
Bug Blocks: 1415556, 1442136    

Description Jaromir Coufal 2017-02-06 23:32:26 UTC
Re-use work which was done for composable upgrades and adapt same procedure for updates in order to isolate errors and minimize amount of duplication in procedures.

Comment 3 Jaromir Coufal 2017-03-13 05:10:43 UTC
*** Bug 1391705 has been marked as a duplicate of this bug. ***

Comment 6 Steven Hardy 2017-04-26 16:22:00 UTC
Note I am already working on patches to enable this for the docker based architecture - it's probably possible to adjust the eventual (ansible based) model there to also handle updates on the host, but I've not looked at that yet.

It's not really as simple as reusing tasks from composable upgrades though, as all those really do is stop services, and packaging already restarts them for us in most cases.

IMHO having a parallel effort to rework the current yum_update.sh model into ansible probably isn't worthwhile so we'll need to work together, as I think we'll need upgrades integrated with the container deployment (just updating things on the host is no longer enough, we have to restart containers with the services in, vs have packaging handle restarts as is the case today).

WIP patches here:

https://review.openstack.org/#/c/454816/
https://review.openstack.org/#/c/456254/
https://review.openstack.org/#/c/456307/
https://review.openstack.org/#/c/456308
https://review.openstack.org/#/c/456309/
https://review.openstack.org/#/c/456310/
https://review.openstack.org/#/c/456311
https://review.openstack.org/#/c/459390/

The end goal is to have a playbook we can run end-to-end (all steps) on each node in a rolling fashion, and depending on how we run it it may be possible to enable operators to run it one step at a time.

Comment 7 Sofer Athlan-Guyot 2017-05-31 12:03:39 UTC
https://review.openstack.org/#/c/462211
https://review.openstack.org/#/c/467581

and keeping yum_update.sh for non-containerized.

Comment 8 Jaromir Coufal 2017-06-12 19:50:45 UTC
*** Bug 1419748 has been marked as a duplicate of this bug. ***

Comment 12 Amit Ugol 2017-12-13 09:32:10 UTC
100% test execution, no blockers or serious issues with this feature.