https://etherpad.openstack.org/p/mitaka-heat-hooks-notifications * Hooks are a big step forward to allowing users to quiesce workloads. But the current interface kind of sucks. The hooks trigger almost silently, and have to be polled. If they get set by accident, you'll likely never figure out why your stack is timing out. Some things to consider:
* A notification mechanism for hooks (Zaqar?). Related: https://review.openstack.org/232967
* A way to set hooks temporarily (so that even when you use PATCH and keep the same environment, they don't stick around)
* More types of hooks ("post-" hooks? "pre-delete"?)
* Hooks between batches of rolling ASG/RG updates. Or just pre- and post- hooks on whole (nested) stack updates?
* Resolve the issue with pre-update hooks running whether or not the resource in question is to be updated. (Can this even be resolved?) Define hook types with the desired behaviour w.r.t replace-on-update.
* Incorporating hooks in convergence
