dependency.
Ton Ngo,
From: Zane Bitter
To: openstack-dev@lists.openstack.org,
Date: 03/18/2014 09:45 AM
Subject: Re: [openstack-dev] [Heat] Stack breakpoint
On 17/03/14 21:18, Mike Spreitzer wrote:
> Zane Bitter wrote on 03/17/2014 07:03:25 PM:
>
> >
On 17/03/14 21:18, Mike Spreitzer wrote:
Zane Bitter wrote on 03/17/2014 07:03:25 PM:
> On 17/03/14 17:03, Ton Ngo wrote:
> > - How to handle resources with timer, e.g. wait condition:
pause/resume
> > timer value
>
> Handle it by only allowing pauses before and after. In most cases I'm
Zane Bitter wrote on 03/17/2014 07:03:25 PM:
> On 17/03/14 17:03, Ton Ngo wrote:
> > - How to handle resources with timer, e.g. wait condition:
pause/resume
> > timer value
>
> Handle it by only allowing pauses before and after. In most cases I'm
> not sure what it would mean to pause _during
On 17/03/14 17:03, Ton Ngo wrote:
(reposting as new thread)
I would like to revisit with more details an idea that was mentioned in the
last design summit and hopefully get some feedback.
The scenario is troubleshooting a failed template.
Currently we can stop on the point of failure by disabl
(reposting as new thread)
I would like to revisit with more details an idea that was mentioned in the
last design summit and hopefully get some feedback.
The scenario is troubleshooting a failed template.
Currently we can stop on the point of failure by disabling rollback: this
works well for s
Ton, could you repost this as a new thread? It has very little to do
with the referenced thread.
Excerpts from Ton Ngo's message of 2014-03-17 12:10:33 -0700:
> I would like to revisit with more details an idea that was mentioned in the
> last design summit and hopefully get some feedback.
>
> Th
I would like to revisit with more details an idea that was mentioned in the
last design summit and hopefully get some feedback.
The scenario is troubleshooting a failed template.
Currently we can stop on the point of failure by disabling rollback: this
works well for stack-create; stack-update re
