aboutsummaryrefslogtreecommitdiffstats
path: root/environments/major-upgrade-composable-steps-docker.yaml
AgeCommit message (Collapse)AuthorFilesLines
2017-11-13Update ansible before the ansible upgrade tasksMarius Cornea1-1/+2
In case an ansible update is available during the upgrade then the ansible package gets updated to a new version by the ansible tasks. This could potentially lead to issues as the one described in LP#1729546. This change updates the ansible package via yum before starting the ansible upgrade tasks in order to avoid having ansible updating itself. Related-bug: 1729546 Change-Id: I2ea0aa1f670053578996018663c9fa52dec14b77 (cherry picked from commit 0c1ac1d752aaf88832b34e165f7d147e2304ff1c)
2017-10-09Remove package if service stopped and disabledmarios1-0/+1
Adds a UpgradeRemoveUnusedPackages param to use in the ansible when conditional for the removal Adds package removal to step2 right after a service is stopped and disabled on step2. Package updates happen in step3 so ideally remove before that. The package removal task has ignore_errors true so dependencies or other issue removing packages will not fail the upgrade workflow. Also adds this to the upgrade environment files for visibility and defaulting false Change-Id: Ie4e4a2d41f7752c5a13507a7c15c6f68e203cfca Related-Bug: 1701501 (cherry picked from commit ce0ef2fa207698c1ae61c1620fe3c5e8d1c7bfca)
2017-10-07Support for Ocata-Pike live-migration over sshOliver Walsh1-0/+1
In Ocata all live-migration over ssh is performed on the default ssh port (22). In Pike the containerized live-migration over ssh is on port 2022 as the docker host's sshd is using port 22. To allow live migration during upgrade we need to temporarily pin the Pike computes to port 22 and in the final converge we can switch over to port 2022. This also changes the default port to 2022 for baremetal computes in Pike to enable live-migration between baremetal and containerized computes. Change-Id: Icb9bfdd9a99dc1dce28eb95c50a9a36bffa621b1 Depends-On: I0b80b81711f683be539939e7d084365ff63546d3 Closes-Bug: 1714171 (cherry picked from commit 17fd16b9f266e1aa67bf03ebdf309e89d668ada2)
2017-08-11Consolidate puppet/docker deployments with one deploy steps workflowSteven Hardy1-4/+1
If we consolidate these we can focus on one implementation (the new ansible based one used for docker-steps) Change-Id: Iec0ad2278d62040bf03613fc9556b199c6a80546 Depends-On: Ifa2afa915e0fee368fb2506c02de75bf5efe82d5
2017-06-29Install ansible-pacemaker on O->P upgradeJiri Stransky1-0/+2
This has been omitted in Ocata image, so we need to install this in O->P upgrade again. Change Ic8ce72133c47a4c90d581a0925213877b11a471e adds it to the image, so that we can stop installing it on P->Q upgrade, and start using it for minor updates too. Change-Id: I893792e8d82c716b2f3e7b8878b25ba89ea724f1 Co-Authored-By: Marius Cornea <mcornea@redhat.com> Partial-Bug: #1701208
2017-05-04Add StackUpdateType to set hiera on upgradeSteven Hardy1-0/+1
This will enable those consuming the stack_update_type hieradata set by this parameter to differentiate an update from a major upgrade Change-Id: I38469f4b7d04165ea5371aeb0cbd2e9349d70c79
2017-03-22Only set EnableConfigPurge on major upgradesSteven Hardy1-0/+1
Bug #1611800 fixed an upgrade issue by enabling purging configs for some services, but this causes issues such as longer updates and restarting services in the minor update case, so only do this for major upgrades, and default to false. Related-Bug: #1611800 Closes-Bug: #1674858 Change-Id: Iff7d715f6730c5633f1146008504b4309ef3133d
2017-03-06Enable composable upgrades for docker service templatesSteven Hardy1-0/+10
This aligns the docker based services with the new composable upgrades architecture we landed for ocata, and does a first-pass adding upgrade_tasks for the services (these may change, atm we only disable the service on the host). To run the upgrade workflow you basically do two steps: openstack overcloud deploy --templates \ -e environments/major-upgrade-composable-steps-docker.yaml This will run the ansible upgrade steps we define via upgrade_tasks then run the normal docker PostDeploySteps to bring up the containers. For the puppet workflow there's then an operator driven step where compute nodes (and potentially storage nodes) are upgrades in batches and finally you do: openstack overcloud deploy --templates \ -e environments/major-upgrade-converge-docker.yaml In the puppet case this re-applies puppet to unpin the nova RPC API so I guess it'll restart the nova containers this affects but otherwise will be a no-op (we also disable the ansible steps at this point. Depends-On: I9057d47eea15c8ba92ca34717b6b5965d4425ab1 Change-Id: Ia50169819cb959025866348b11337728f8ed5c9e