Introduce a UpgradeScriptDeliveryWorfklow as part of tripleo upgrades
authormarios <marios@redhat.com>
Wed, 2 Mar 2016 16:09:59 +0000 (18:09 +0200)
committermarios <marios@redhat.com>
Thu, 3 Mar 2016 11:30:48 +0000 (13:30 +0200)
commitc78a215ae9cd02a47e46b4d302f2a275ccce1693
tree048c7c8b396fa18533633870cac7e1b0b83055fc
parenta54e0b973b296204139d6ff2816902ee96f0b309
Introduce a UpgradeScriptDeliveryWorfklow as part of tripleo upgrades

This splits the upgrade script delivery out of the UpgradeWorkflow
and into a new task which delivers the upgrade script for
compute and object-storage nodes. This is intended to be the first
part of the upgrades process, since we need to upgrade swift nodes
before the controllers and then only one at a time. So this will
deliver the upgrade script which can be invoked by the operator
using the existing script in tripleo-common
'upgrade-non-controller.sh'.

This can be invoked by passing the -e
environments/major-upgrade-script-delivery.yaml (added here) to
the openstack overcloud deploy command.

Change-Id: I20a0d4978e907111404f8108c502ab53b69a3296
environments/major-upgrade-script-delivery.yaml [new file with mode: 0644]
extraconfig/tasks/major_upgrade_object_storage.sh [new file with mode: 0644]
extraconfig/tasks/major_upgrade_pacemaker.yaml
extraconfig/tasks/major_upgrade_script_delivery.yaml [new file with mode: 0644]