On 01/14/2015 01:47 AM, Ton Ngo wrote:
Hi Tomas,
I think your patch is a great start so we can prototype quickly; I am
trying it out right now. We can break up the implementation into several
parts that can be updated more or less independently based on the feedback.
Ton,
Hey ever
@lists.openstack.org
Date: 01/13/2015 09:20 AM
Subject:Re: [openstack-dev] [Heat] Where to keep data about stack
breakpoints?
On 01/13/2015 01:15 AM, Ton Ngo wrote:
> I was also thinking of using the environment to hold the breakpoint,
> similarly to parameters. The CLI a
onality.
From: Steven Hardy
To: "OpenStack Development Mailing List (not for usage questions)"
Date: 01/12/2015 02:40 PM
Subject: Re: [openstack-dev] [Heat] Where to keep data about stack
breakpoints?
On Mon, Jan 12, 2015 at 05:10:47PM -0
On 13/01/15 11:58, Tomas Sedovic wrote:
I also had a chat with Steve Hardy and he suggested adding a STOPPED
state to the stack (this isn't in the spec). While not strictly
necessary to implement the spec, this would help people figure out that
the stack has reached a breakpoint instead of just w
On 01/12/2015 07:05 PM, Steven Hardy wrote:
On Mon, Jan 12, 2015 at 04:29:15PM +0100, Tomas Sedovic wrote:
Hey folks,
I did a quick proof of concept for a part of the Stack Breakpoint spec[1]
and I put the "does this resource have a breakpoint" flag into the metadata
of the resource:
https://r
On 01/12/2015 10:36 PM, Zane Bitter wrote:
On 12/01/15 10:49, Ryan Brown wrote:
On 01/12/2015 10:29 AM, Tomas Sedovic wrote:
Hey folks,
I did a quick proof of concept for a part of the Stack Breakpoint
spec[1] and I put the "does this resource have a breakpoint" flag into
the metadata of the r
Re: [openstack-dev] [Heat] Where to keep data about stack
breakpoints?
On Mon, Jan 12, 2015 at 05:10:47PM -0500, Zane Bitter wrote:
> On 12/01/15 13:05, Steven Hardy wrote:
> >>>I also had a chat with Steve Hardy and he suggested adding a STOPPED
state
> >&g
On Mon, Jan 12, 2015 at 05:10:47PM -0500, Zane Bitter wrote:
> On 12/01/15 13:05, Steven Hardy wrote:
> >>>I also had a chat with Steve Hardy and he suggested adding a STOPPED state
> >>>to the stack (this isn't in the spec). While not strictly necessary to
> >>>implement the spec, this would help
On 12/01/15 13:05, Steven Hardy wrote:
>I also had a chat with Steve Hardy and he suggested adding a STOPPED state
>to the stack (this isn't in the spec). While not strictly necessary to
>implement the spec, this would help people figure out that the stack has
>reached a breakpoint instead of jus
On 12/01/15 10:49, Ryan Brown wrote:
On 01/12/2015 10:29 AM, Tomas Sedovic wrote:
Hey folks,
I did a quick proof of concept for a part of the Stack Breakpoint
spec[1] and I put the "does this resource have a breakpoint" flag into
the metadata of the resource:
https://review.openstack.org/#/c/1
On Mon, Jan 12, 2015 at 04:29:15PM +0100, Tomas Sedovic wrote:
> Hey folks,
>
> I did a quick proof of concept for a part of the Stack Breakpoint spec[1]
> and I put the "does this resource have a breakpoint" flag into the metadata
> of the resource:
>
> https://review.openstack.org/#/c/146123/
>
On 01/12/2015 10:29 AM, Tomas Sedovic wrote:
> Hey folks,
>
> I did a quick proof of concept for a part of the Stack Breakpoint
> spec[1] and I put the "does this resource have a breakpoint" flag into
> the metadata of the resource:
>
> https://review.openstack.org/#/c/146123/
>
> I'm not sure w
12 matches
Mail list logo
