path: root/environments/overcloud-steps.yaml
diff options
authorSteven Hardy <shardy@redhat.com>2015-03-05 17:27:46 -0500
committerSteven Hardy <shardy@redhat.com>2015-05-22 21:30:57 +0100
commit02b413d18bb715cd7c8d9bf243cd2e777c432865 (patch)
tree6f30afff1d8602743d0bf04d0ab9960197aee219 /environments/overcloud-steps.yaml
parent631b1afee180317e4eca5980e82238265f1a7049 (diff)
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
Diffstat (limited to 'environments/overcloud-steps.yaml')
1 files changed, 10 insertions, 0 deletions
diff --git a/environments/overcloud-steps.yaml b/environments/overcloud-steps.yaml
new file mode 100644
index 0000000..99f7368
--- /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.
+ resources:
+ "*NodesPostDeployment":
+ "*Deployment_Step*":
+ hooks: [pre-create, pre-update]