From 02b413d18bb715cd7c8d9bf243cd2e777c432865 Mon Sep 17 00:00:00 2001 From: Steven Hardy Date: Thu, 5 Mar 2015 17:27:46 -0500 Subject: overcloud stepped deployment environment When combined with --with-steps added to devtest_overcloud: https://review.openstack.org/#/c/162109/ this enables stepped deployments using heat hooks. This environment file will break on all *StepN resources in every *NodesPostDeployment resource, on both create and update. Change-Id: Ibab567f0a37b832ea2b5966288ad55b5682c31ab --- environments/overcloud-steps.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 environments/overcloud-steps.yaml (limited to 'environments/overcloud-steps.yaml') diff --git a/environments/overcloud-steps.yaml b/environments/overcloud-steps.yaml new file mode 100644 index 00000000..99f73688 --- /dev/null +++ b/environments/overcloud-steps.yaml @@ -0,0 +1,10 @@ +# Specifies hooks/breakpoints where overcloud deployment should stop +# Allows operator validation between steps, and/or more granular control. +# Note: the wildcards relate to naming convention for some resource suffixes, +# e.g see puppet/*-post-puppet.yaml, enabling this will mean we wait for +# a user signal on every *Deployment_StepN resource defined in those files. +resource_registry: + resources: + "*NodesPostDeployment": + "*Deployment_Step*": + hooks: [pre-create, pre-update] -- cgit 1.2.3-korg