aboutsummaryrefslogtreecommitdiffstats
path: root/puppet/extraconfig
diff options
context:
space:
mode:
authorJames Slagle <jslagle@redhat.com>2017-06-07 14:03:38 -0400
committerJames Slagle <jslagle@redhat.com>2017-06-07 14:03:38 -0400
commitd48299cb505e8b051689207e031eb67df11237ab (patch)
tree053dbe1fabf478ef527de8fcc181162404ef7399 /puppet/extraconfig
parent1968d4042e7818ccacf49af110f60b6f617c3a82 (diff)
Use Deployment actions for blacklist
Instead of using the Heat condition directly on the Deployment resources, use it to set the action list to an empty list when the server is blacklisted. This has a couple advantages over the previous approach in that the actual resources are not deleted and recreated when servers are added and removed from the blacklist. Recreating the resources can be problematic, as it would then force the Deployments to re-run when a server is removed from the blacklist. That is likely not always desirable, especially in the case of NetworkDeloyment. Additionally, you will still see the resources for a blacklisted server in the stack, just with an empty set of actions. This has the benefit of preserving the history of the previous time the Deployment was triggered. implements blueprint disable-deployments Change-Id: I3d0263a6319ae4871b1ae11383ae838bd2540d36
Diffstat (limited to 'puppet/extraconfig')
0 files changed, 0 insertions, 0 deletions