From 58c6988751c6d6b55cfc22aa87bc4f45b6509c2b Mon Sep 17 00:00:00 2001 From: Steven Hardy Date: Fri, 2 Dec 2016 13:58:24 +0000 Subject: Run upgrade steps before post-deploy config For some upgrade scenarios, e.g all-in-one deployments, it may be possible to run the upgrade steps, then apply puppet in one stack update, so reverse the order here. For normal deployments the upgrade steps are mapped to OS::Heat::None so this will have no effect. Partially-Implements: blueprint overcloud-upgrades-per-service Change-Id: I3c78751349a6ac2bc5dff82f67bffe13750ac21c --- environments/major-upgrade-all-in-one.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 environments/major-upgrade-all-in-one.yaml (limited to 'environments') diff --git a/environments/major-upgrade-all-in-one.yaml b/environments/major-upgrade-all-in-one.yaml new file mode 100644 index 00000000..69d72edd --- /dev/null +++ b/environments/major-upgrade-all-in-one.yaml @@ -0,0 +1,8 @@ +# We run the upgrade steps without disabling the OS::TripleO::PostDeploySteps +# this means you can do a major upgrade in one pass, which may be useful +# e.g for all-in-one deployments where we can upgrade the compute services +# at the same time as the controlplane +# Note that it will be necessary to pass a mapping of OS::Heat::None again for +# any subsequent updates, or the upgrade steps will run again. +resource_registry: + OS::TripleO::UpgradeSteps: ../puppet/major_upgrade_steps.yaml -- cgit 1.2.3-korg