Excerpts from Steve Baker's message of 2014-06-02 14:37:25 -0700:
> On 31/05/14 07:01, Zane Bitter wrote:
> > On 29/05/14 19:52, Clint Byrum wrote:
> >
> >> update-failure-recovery
> >> ===
> >>
> >> This is a blueprint I believe Zane is working on to land in Juno. It
> >> will
Steve Baker wrote on 06/02/2014 05:37:25 PM:
> > BTW You missed off another strategy that we have discussed in the
> > past, and which I think Steve Baker might(?) be working on: retrying
> > failed calls at the client level.
> >
> As part of the client-plugins blueprint I'm planning on implement
On 31/05/14 07:01, Zane Bitter wrote:
> On 29/05/14 19:52, Clint Byrum wrote:
>
>> update-failure-recovery
>> ===
>>
>> This is a blueprint I believe Zane is working on to land in Juno. It
>> will
>> allow us to retry a failed create or update action. Combined with the
>> separa
On 29/05/14 19:52, Clint Byrum wrote:
Multiple Stacks
===
We could break the stack up between controllers, and compute nodes. The
controller will be less likely to fail because it will probably be 3 nodes
for a reasonably sized cloud. The compute nodes would then live in their
own st
Excerpts from Mike Spreitzer's message of 2014-05-30 05:42:43 +0530:
> Clint Byrum wrote on 05/29/2014 07:52:07 PM:
>
> > I am writing to get some brainstorming started on how we might mitigate
> > some of the issues we've seen while deploying large stacks on Heat. I am
> > sending this to the de
Clint Byrum wrote on 05/29/2014 07:52:07 PM:
> I am writing to get some brainstorming started on how we might mitigate
> some of the issues we've seen while deploying large stacks on Heat. I am
> sending this to the dev list because it may involve landing fixes rather
> than just using different
Hello!
I am writing to get some brainstorming started on how we might mitigate
some of the issues we've seen while deploying large stacks on Heat. I am
sending this to the dev list because it may involve landing fixes rather
than just using different strategies. The problems outlined here are
well
