No-op Puppet for upgrades/migrations according to composable roles
Our previous no-ops stopped working because the Puppet run resources moved under a different entry in resource registry. This is now fixed to follow the latest way. Change-Id: Ia5598385ddca185bfbf10e2d3babb53f6f77d1ac Closes-Bug: #1626452
This commit is contained in:
parent
75c20d5b5d
commit
4422fb97c8
@ -3,8 +3,4 @@ resource_registry:
|
||||
OS::TripleO::Tasks::UpdateWorkflow: ../extraconfig/tasks/mitaka_to_newton_aodh_data_migration.yaml
|
||||
|
||||
# no-op the rest
|
||||
OS::TripleO::ControllerPostDeployment: OS::Heat::None
|
||||
OS::TripleO::ComputePostDeployment: OS::Heat::None
|
||||
OS::TripleO::ObjectStoragePostDeployment: OS::Heat::None
|
||||
OS::TripleO::BlockStoragePostDeployment: OS::Heat::None
|
||||
OS::TripleO::CephStoragePostDeployment: OS::Heat::None
|
||||
OS::TripleO::PostDeploySteps: OS::Heat::None
|
||||
|
@ -3,8 +3,4 @@ parameter_defaults:
|
||||
|
||||
resource_registry:
|
||||
OS::TripleO::Tasks::UpdateWorkflow: ../extraconfig/tasks/major_upgrade_pacemaker_init.yaml
|
||||
OS::TripleO::ControllerPostDeployment: OS::Heat::None
|
||||
OS::TripleO::ComputePostDeployment: OS::Heat::None
|
||||
OS::TripleO::ObjectStoragePostDeployment: OS::Heat::None
|
||||
OS::TripleO::BlockStoragePostDeployment: OS::Heat::None
|
||||
OS::TripleO::CephStoragePostDeployment: OS::Heat::None
|
||||
OS::TripleO::PostDeploySteps: OS::Heat::None
|
||||
|
@ -3,8 +3,4 @@ parameter_defaults:
|
||||
|
||||
resource_registry:
|
||||
OS::TripleO::Tasks::UpdateWorkflow: ../extraconfig/tasks/major_upgrade_pacemaker.yaml
|
||||
OS::TripleO::ControllerPostDeployment: OS::Heat::None
|
||||
OS::TripleO::ComputePostDeployment: OS::Heat::None
|
||||
OS::TripleO::ObjectStoragePostDeployment: OS::Heat::None
|
||||
OS::TripleO::BlockStoragePostDeployment: OS::Heat::None
|
||||
OS::TripleO::CephStoragePostDeployment: OS::Heat::None
|
||||
OS::TripleO::PostDeploySteps: OS::Heat::None
|
||||
|
Loading…
Reference in New Issue
Block a user