summaryrefslogtreecommitdiffstats
path: root/environments
diff options
context:
space:
mode:
authorSteven Hardy <shardy@redhat.com>2016-12-02 13:58:24 +0000
committerSteven Hardy <shardy@redhat.com>2016-12-19 11:04:47 +0000
commit58c6988751c6d6b55cfc22aa87bc4f45b6509c2b (patch)
treedbb5051fad4067b53d4b63fc76225f8cd0e69e75 /environments
parentb8a4e40cf2281036d4fb1f8db48ce16625b2edac (diff)
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
Diffstat (limited to 'environments')
-rw-r--r--environments/major-upgrade-all-in-one.yaml8
1 files changed, 8 insertions, 0 deletions
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