tripleo-heat-templates/environments/major-upgrade-composable-steps-docker.yaml
marios 5cbe298f59 Remove the heat upgrade steps for Q upgrade workflow
This removes most of the Heat driver upgrade workflow, including
the script delivery and stepwise upgrade tasks with invocation
of ansible via heat

For Q upgrades the operator should use
    openstack overcloud upgrade --init-upgrade --container-registry-file file
    openstack overcloud upgrade --nodes Controller
etc.

Depends-On: I54f8fc57b758e34c620d607be15d2291d545ff6f
Change-Id: I75f087dc456c50327c3b4ad98a1f89a7e012dc68
2018-02-09 18:41:04 +02:00

16 lines
480 B
YAML

resource_registry:
OS::TripleO::DeploymentSteps: OS::Heat::None
OS::TripleO::Tasks::*PreConfig: OS::Heat::None
OS::TripleO::Tasks::*PostConfig: OS::Heat::None
parameter_defaults:
EnableConfigPurge: false
StackUpdateType: UPGRADE
UpgradeLevelNovaCompute: auto
UpgradeInitCommonCommand: |
#!/bin/bash
set -eu
# Pike to Queens, put any needed host-level workarounds here
yum update -y ansible
MigrationSshPort: 22
UpgradeRemoveUnusedPackages: false