fb748ba307
This aligns the docker based services with the new composable upgrades architecture we landed for ocata, and does a first-pass adding upgrade_tasks for the services (these may change, atm we only disable the service on the host). To run the upgrade workflow you basically do two steps: openstack overcloud deploy --templates \ -e environments/major-upgrade-composable-steps-docker.yaml This will run the ansible upgrade steps we define via upgrade_tasks then run the normal docker PostDeploySteps to bring up the containers. For the puppet workflow there's then an operator driven step where compute nodes (and potentially storage nodes) are upgrades in batches and finally you do: openstack overcloud deploy --templates \ -e environments/major-upgrade-converge-docker.yaml In the puppet case this re-applies puppet to unpin the nova RPC API so I guess it'll restart the nova containers this affects but otherwise will be a no-op (we also disable the ansible steps at this point. Depends-On: I9057d47eea15c8ba92ca34717b6b5965d4425ab1 Change-Id: Ia50169819cb959025866348b11337728f8ed5c9e
11 lines
455 B
YAML
11 lines
455 B
YAML
resource_registry:
|
|
# FIXME(shardy) do we need to break major_upgrade_steps.yaml apart to
|
|
# enable docker specific logic, or is just overridding PostUpgradeSteps
|
|
# enough (as we want to share the ansible tasks steps etc)
|
|
OS::TripleO::PostDeploySteps: ../puppet/major_upgrade_steps.yaml
|
|
parameter_defaults:
|
|
UpgradeLevelNovaCompute: auto
|
|
UpgradeInitCommonCommand: |
|
|
#!/bin/bash
|
|
# Ocata to Pike, put any needed host-level workarounds here
|