Excerpts from Zane Bitter's message of 2014-12-01 13:05:42 -0800:
> On 13/11/14 13:59, Clint Byrum wrote:
> > I'm not sure we have the same understanding of AMQP, so hopefully we can
> > clarify here. This stackoverflow answer echoes my understanding:
> >
> > http://stackoverflow.com/questions/1784
On 13/11/14 13:59, Clint Byrum wrote:
I'm not sure we have the same understanding of AMQP, so hopefully we can
clarify here. This stackoverflow answer echoes my understanding:
http://stackoverflow.com/questions/17841843/rabbitmq-does-one-consumer-block-the-other-consumers-of-the-same-queue
Not
Arg, sorry for the spam, mail.app was still trying to send it multiple times
for some reason...
-Josh
From: Joshua Harlow
To: OpenStack Development Mailing List (not for usage questions)
Sent: Friday, November 14, 2014 11:45 AM
Subject: Re: [openstack-dev] [Heat] Using Job Queues
Sounds like this is tooz[1] ;)
The api for tooz (soon to be an oslo library @
https://review.openstack.org/#/c/122439/) is around coordination and
'service-group' like behavior so I hope we don't have duplicates of this in
'oslo.healthcheck' instead of just using/contributing to tooz instead.
Sounds like this is tooz[1] ;)
The api for tooz (soon to be an oslo library @
https://review.openstack.org/#/c/122439/) is around coordination and
'service-group' like behavior so I hope we don't have duplicates of this in
'oslo.healthcheck' instead of just using/contributing to tooz instead.
Sounds like this is tooz[1] ;)
The api for tooz (soon to be an oslo library @
https://review.openstack.org/#/c/122439/) is around coordination and
'service-group' like behavior so I hope we don't have duplicates of this in
'oslo.healthcheck' instead of just using/contributing to tooz instead.
> -Original Message-
> From: Joshua Harlow [mailto:harlo...@outlook.com]
> Sent: Thursday, November 13, 2014 10:50 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Heat] Using Job Queues for timeout ops
>
> On N
> -Original Message-
> From: Clint Byrum [mailto:cl...@fewbar.com]
> Sent: Thursday, November 13, 2014 8:00 PM
> To: openstack-dev
> Subject: Re: [openstack-dev] [Heat] Using Job Queues for timeout ops
>
> Excerpts from Zane Bitter's message of 2014-11-13 09:55
On Nov 13, 2014, at 4:08 PM, Clint Byrum wrote:
> Excerpts from Joshua Harlow's message of 2014-11-13 14:01:14 -0800:
>> On Nov 13, 2014, at 7:10 AM, Clint Byrum wrote:
>>
>>> Excerpts from Joshua Harlow's message of 2014-11-13 00:45:07 -0800:
A question;
How is using something
Excerpts from Joshua Harlow's message of 2014-11-13 14:01:14 -0800:
> On Nov 13, 2014, at 7:10 AM, Clint Byrum wrote:
>
> > Excerpts from Joshua Harlow's message of 2014-11-13 00:45:07 -0800:
> >> A question;
> >>
> >> How is using something like celery in heat vs taskflow in heat (or at
> >> l
On Nov 13, 2014, at 7:10 AM, Clint Byrum wrote:
> Excerpts from Joshua Harlow's message of 2014-11-13 00:45:07 -0800:
>> A question;
>>
>> How is using something like celery in heat vs taskflow in heat (or at least
>> concept [1]) 'to many code change'.
>>
>> Both seem like change of similar l
On Nov 13, 2014, at 10:59 AM, Clint Byrum wrote:
> Excerpts from Zane Bitter's message of 2014-11-13 09:55:43 -0800:
>> On 13/11/14 09:58, Clint Byrum wrote:
>>> Excerpts from Zane Bitter's message of 2014-11-13 05:54:03 -0800:
On 13/11/14 03:29, Murugan, Visnusaran wrote:
> Hi all,
Excerpts from Zane Bitter's message of 2014-11-13 09:55:43 -0800:
> On 13/11/14 09:58, Clint Byrum wrote:
> > Excerpts from Zane Bitter's message of 2014-11-13 05:54:03 -0800:
> >> On 13/11/14 03:29, Murugan, Visnusaran wrote:
> >>> Hi all,
> >>>
> >>> Convergence-POC distributes stack operations b
ack.org
Subject: Re: [openstack-dev] [Heat] Using Job Queues for timeout ops
On 13/11/14 09:58, Clint Byrum wrote:
> Excerpts from Zane Bitter's message of 2014-11-13 05:54:03 -0800:
>> On 13/11/14 03:29, Murugan, Visnusaran wrote:
>>> Hi all,
>>>
>>> Converg
On 13/11/14 09:58, Clint Byrum wrote:
Excerpts from Zane Bitter's message of 2014-11-13 05:54:03 -0800:
On 13/11/14 03:29, Murugan, Visnusaran wrote:
Hi all,
Convergence-POC distributes stack operations by sending resource actions
over RPC for any heat-engine to execute. Entire stack lifecycle
On 11/13/2014 09:58 AM, Clint Byrum wrote:
> Excerpts from Zane Bitter's message of 2014-11-13 05:54:03 -0800:
>> On 13/11/14 03:29, Murugan, Visnusaran wrote:
> [snip]
>>> 3.Migrate heat to use TaskFlow. (Too many code change)
>>
>> If it's just handling timed triggers (maybe this is closer to #
Excerpts from Joshua Harlow's message of 2014-11-13 00:45:07 -0800:
> A question;
>
> How is using something like celery in heat vs taskflow in heat (or at least
> concept [1]) 'to many code change'.
>
> Both seem like change of similar levels ;-)
>
I've tried a few times to dive into refactor
@redhat.com]
> Sent: Thursday, November 13, 2014 3:49 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev] [Heat] Using Job Queues for timeout ops
>
> On 13/11/14 09:31, Jastrzebski, Michal wrote:
> > Guys, I don't think we want to get into this cluster m
Excerpts from Zane Bitter's message of 2014-11-13 05:54:03 -0800:
> On 13/11/14 03:29, Murugan, Visnusaran wrote:
> > Hi all,
> >
> > Convergence-POC distributes stack operations by sending resource actions
> > over RPC for any heat-engine to execute. Entire stack lifecycle will be
> > controlled b
On 13/11/14 09:31, Jastrzebski, Michal wrote:
Guys, I don't think we want to get into this cluster management mud. You say
let's
make observer...and what if observer dies? Do we do observer to observer? And
then
there is split brain. I'm observer, I've lost connection to worker. Should I
resta
n recover from error and retry if there is
> a notification available.
>
>
> -Vishnu
>
> -Original Message-
> From: Zane Bitter [mailto:zbit...@redhat.com]
> Sent: Thursday, November 13, 2014 7:05 PM
> To: openstack-dev@lists.openstack.org
> Subject: Re: [openstack-dev
: Thursday, November 13, 2014 7:05 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Heat] Using Job Queues for timeout ops
On 13/11/14 06:52, Angus Salkeld wrote:
> On Thu, Nov 13, 2014 at 6:29 PM, Murugan, Visnusaran
> mailto:visnusaran.muru...@hp.com>>
On 13/11/14 03:29, Murugan, Visnusaran wrote:
Hi all,
Convergence-POC distributes stack operations by sending resource actions
over RPC for any heat-engine to execute. Entire stack lifecycle will be
controlled by worker/observer notifications. This distributed model has
its own advantages and di
On 13/11/14 06:52, Angus Salkeld wrote:
On Thu, Nov 13, 2014 at 6:29 PM, Murugan, Visnusaran
mailto:visnusaran.muru...@hp.com>> wrote:
Hi all,
__ __
Convergence-POC distributes stack operations by sending resource
actions over RPC for any heat-engine to execute. Entire stac
-dev] [Heat] Using Job Queues for timeout ops
On Thu, Nov 13, 2014 at 6:29 PM, Murugan, Visnusaran
mailto:visnusaran.muru...@hp.com>> wrote:
Hi all,
Convergence-POC distributes stack operations by sending resource actions over
RPC for any heat-engine to execute. Entire stack lifecycle w
On Thu, Nov 13, 2014 at 6:29 PM, Murugan, Visnusaran <
visnusaran.muru...@hp.com> wrote:
> Hi all,
>
>
>
> Convergence-POC distributes stack operations by sending resource actions
> over RPC for any heat-engine to execute. Entire stack lifecycle will be
> controlled by worker/observer notificatio
wrong.
-Vishnu
From: Joshua Harlow [mailto:harlo...@outlook.com]
Sent: Thursday, November 13, 2014 2:15 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Heat] Using Job Queues for timeout ops
A question;
How is using something like celery in heat vs tas
A question;
How is using something like celery in heat vs taskflow in heat (or at least
concept [1]) 'to many code change'.
Both seem like change of similar levels ;-)
What was your metric for determining the code change either would have (out of
curiosity)?
Perhaps u should look at [2], alth
28 matches
Mail list logo
