Write the compute upgrade script for tripleo major upgrade workflow
authormarios <marios@redhat.com>
Mon, 22 Feb 2016 15:18:16 +0000 (17:18 +0200)
committermarios <marios@redhat.com>
Fri, 26 Feb 2016 10:19:12 +0000 (12:19 +0200)
commit55f603b7364387e8c7f9b6b67747a5fddf6e91d4
treea3208ba0dfcd40345c0a5b900966a9ae808a1521
parentf8633a42e24b2f777f6f03d09af07346724c15b5
Write the compute upgrade script for tripleo major upgrade workflow

As part of the major upgrade workflow non-controller nodes are to
be updated by the operator, out-of-band and only after an initial
heat stack-update that invokes the upgrade of the controller nodes.

This review adds a ComputeDeliverUpgradeConfigDeployment_Step3
SoftwareDeploymentGroup to be applied only to compute nodes, and
that depends on the controllers having been upgraded after
ControllerPacemakerUpgradeConfig_Step2.

Its purpose is to deliver but not invoke the upgrade script on
compute nodes to /root/tripleo_upgrade_node.sh .

The non-controller nodes will then be upgraded later by an
operator that will run the script provided for that purpose, like
at https://review.openstack.org/#/c/284722/1 for example.

Change-Id: Ic6115fc8cf5320abfcf500112ff563bde8b88661
extraconfig/tasks/major_upgrade_compute.sh [new file with mode: 0644]
extraconfig/tasks/major_upgrade_pacemaker.yaml