58c6988751
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
9 lines
490 B
YAML
9 lines
490 B
YAML
# 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
|