Re: [openstack-dev] [mistral] bugfix for "Fix concurrency issues by using READ_COMMITTED" unveils / creates a different bug

2015-12-09 Thread KOFFMAN, Noa (Noa)
Hi, I have reproduced this issue multiple times before your fix was merged. In order to reproduce I used a workflow with multiple async actions, and resumed all of them at the same time. I just created a ticket in launchpad [1], with the workflow used and the mistral engine logs. [1] -

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

2015-04-09 Thread KOFFMAN, Noa (Noa)
://freenode.net), we'll gladly help you with that. Best regards, Pavlo Shchelokovskyy Software Engineer Mirantis Inc www.mirantis.comhttp://www.mirantis.com On Wed, Apr 8, 2015 at 3:43 PM, KOFFMAN, Noa (Noa) noa.koff...@alcatel-lucent.commailto:noa.koff...@alcatel-lucent.com wrote: Hey, I would

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

2015-04-08 Thread KOFFMAN, Noa (Noa)
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