[openstack-dev] [heat] suggestion for lock/protect stack blueprint

Steven Hardy shardy at redhat.com
Wed Apr 8 13:53:35 UTC 2015

On Wed, Apr 08, 2015 at 12:43:06PM +0000, KOFFMAN, Noa (Noa) wrote:
> Hey,
> I would like to suggest a blueprint to allow locking/protecting a 
> stack. Similar to: nova server "lock" or glance-image "--is-protected" 
> flag.
> Once a stack is locked, the only operation allowed on the stack is 
> "unlock" - heat engine should reject any stack operations and ignore 
> signals that modify the stack (such as scaling).
> The lock operation should have a "lock_resources" flag (default = True):
> When True: perform heat lock and enable lock/protect for each stack 
> resource that supports it (nova server, glance image,...).
> when False: perform heat lock - which would lock the stack and all 
> nested stacks (actions on resources will not be effected).

This sounds like a reasonable requirement to me, particularly if there are
existing "lock" operations supported by other openstack services.

We might consider making this a stack "action", e.g like suspend/resume -
actions are intended for stack-wide operations which affect the stack state
but not it's definition, so it seems like potentially a good fit.


More information about the OpenStack-dev mailing list