Delivers upgrade scripts where upgrade steps are disabled
authormarios <marios@redhat.com>
Fri, 13 Jan 2017 11:06:14 +0000 (13:06 +0200)
committerMarios Andreou <marios@redhat.com>
Fri, 10 Feb 2017 10:26:43 +0000 (10:26 +0000)
commited220aecf5ce45d50896054fd3dc2216bcffce20
treed76d4dcabffaad97459ce18764deca4958da0dbe
parent9df292885088b36f27ad65e16fe1d63198a5fe7d
Delivers upgrade scripts where upgrade steps are disabled

This delivers a /root/tripleo_upgrade_node.sh to those nodes
that have the disable_upgrade_deployment flag set to true.
They will later be upgraded manually by the operator who will
invoke the script delivered here using upgrade-non-controller.sh

We can also deliver any service specific upgrade configuration,
such as configuring nova-compute to use the placement API as this
is required in order for placement to be configured and installed
during the subsequent upgrade steps for controller services.

This removes the compute and swift specific upgrade scripts as
they are now merged into the common
tripleo_upgrade_node.sh - removing any hard coded
reference to a particular role name (compute/objectstorage) and
only relying on the disable_upgrade_deployment is roles_data.yaml

Change-Id: I4531a4038b78087ef4a1a62c35f1328822427817
Co-Authored-By: Mathieu Bultel <mbultel@redhat.com>
extraconfig/tasks/major_upgrade_compute.sh [deleted file]
extraconfig/tasks/major_upgrade_object_storage.sh [deleted file]
extraconfig/tasks/major_upgrade_pacemaker_init.j2.yaml [deleted file]
extraconfig/tasks/tripleo_upgrade_node.sh [new file with mode: 0644]
overcloud.j2.yaml
puppet/major_upgrade_steps.j2.yaml
puppet/post.j2.yaml
roles_data.yaml