So, in the upgrade-non-controller.sh script, we add download and execution of both the upgrade_tasks and deploy_steps playbooks with https://review.openstack.org/#/c/490847/ (tripleo-common).
The generated playbooks look like https://paste.fedoraproject.org/paste/gUi5Ckq2qoTT~ed5kItxRw/raw (while it lasts)... seems like most of the things we need for the compute and swift nodes are in the ugprade_tasks (e.g. stop openstack-nova-compute which we had to add recently into the tripleo_upgrade_node.sh).
Slight change in the proposal:
With the help of a utility function in https:/ /review. openstack. org/#/c/ 491749/ (python- tripleoclient) we can use the upgrade_tasks playbook generated by the tripleo- heat-templates at https:/ /review. openstack. org/#/c/ 490848/ (note: this depends on a few shardy tht reviews see shortlog).
So, in the upgrade- non-controller. sh script, we add download and execution of both the upgrade_tasks and deploy_steps playbooks with https:/ /review. openstack. org/#/c/ 490847/ (tripleo-common).
The generated playbooks look like https:/ /paste. fedoraproject. org/paste/ gUi5Ckq2qoTT~ ed5kItxRw/ raw (while it lasts)... seems like most of the things we need for the compute and swift nodes are in the ugprade_tasks (e.g. stop openstack- nova-compute which we had to add recently into the tripleo_ upgrade_ node.sh) .
Reviews: common) : https:/ /review. openstack. org/#/c/ 490847/ "Download and run upgrade/ deploy_ steps_playbooks for upgrade" >(tripleo- heat-templates) : https:/ /review. openstack. org/#/c/ 490848/ "Also write an upgrade_ (batch) _tasks playbook" (&see shortlog!)
|Depends- On:
-->(python- tripleo- client) : https:/ /review. openstack. org/#/c/ 491749/ "Adds when in upgrade_tasks playbook written by config download"
(tripleo-
|
|Depends-On:
|
--
|
|