Re: [openstack-dev] [Magnum][Heat] Expression of Bay Status

2015-03-11 Thread Adrian Otto
In summary, we have decided to use the usage notification events emitted by heat (http://tinyurl.com/oultjm5). This should allow us to detect stack action completions, and errors (with reasons) which should be enough for a Bay implementation that does not need to poll. Stack timeouts can be

Re: [openstack-dev] [Magnum][Heat] Expression of Bay Status

2015-03-11 Thread Jay Lau
2015-03-10 23:21 GMT+08:00 Hongbin Lu hongbin...@gmail.com: Hi Adrian, On Mon, Mar 9, 2015 at 6:53 PM, Adrian Otto adrian.o...@rackspace.com wrote: Magnum Team, In the following review, we have the start of a discussion about how to tackle bay status:

Re: [openstack-dev] [Magnum][Heat] Expression of Bay Status

2015-03-10 Thread Zane Bitter
On 09/03/15 23:47, Angus Salkeld wrote: On Tue, Mar 10, 2015 at 8:53 AM, Adrian Otto adrian.o...@rackspace.com mailto:adrian.o...@rackspace.com wrote: Magnum Team, In the following review, we have the start of a discussion about how to tackle bay status:

Re: [openstack-dev] [Magnum][Heat] Expression of Bay Status

2015-03-10 Thread Hongbin Lu
Hi Adrian, On Mon, Mar 9, 2015 at 6:53 PM, Adrian Otto adrian.o...@rackspace.com wrote: Magnum Team, In the following review, we have the start of a discussion about how to tackle bay status: https://review.openstack.org/159546 I think a key issue here is that we are not subscribing to

[openstack-dev] [Magnum][Heat] Expression of Bay Status

2015-03-09 Thread Adrian Otto
Magnum Team, In the following review, we have the start of a discussion about how to tackle bay status: https://review.openstack.org/159546 I think a key issue here is that we are not subscribing to an event feed from Heat to tell us about each state transition, so we have a low degree of

Re: [openstack-dev] [Magnum][Heat] Expression of Bay Status

2015-03-09 Thread OTSUKA , Motohiro
Hi Adrian. Anyway, I think `Taskflow` is useful to manage jobs which take a long time. So if we don’t use taskflow to manage bay status, we should use this to manage k8s resources. -- OTSUKA, Motohiro Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Tuesday, March 10, 2015 at

Re: [openstack-dev] [Magnum][Heat] Expression of Bay Status

2015-03-09 Thread Angus Salkeld
On Tue, Mar 10, 2015 at 8:53 AM, Adrian Otto adrian.o...@rackspace.com wrote: Magnum Team, In the following review, we have the start of a discussion about how to tackle bay status: https://review.openstack.org/159546 I think a key issue here is that we are not subscribing to an event