On 09-Jan-15 19:19, Zane Bitter wrote:
On 09/01/15 01:07, Angus Salkeld wrote:
I am not in favor of the --continue as an API. I'd suggest responding to
resource timeouts and if there is no response from the task, then
re-start (continue)
the task.
Yeah, I am not in favour of a new API
On Fri, Jan 09, 2015 at 04:07:51PM +1000, Angus Salkeld wrote:
On Fri, Jan 9, 2015 at 3:22 PM, Murugan, Visnusaran
visnusaran.muru...@hp.com wrote:
Steve,
A
My reasoning to have a a**--continuea** like functionality was to run it
as a periodic task and
On 09/01/15 01:07, Angus Salkeld wrote:
I am not in favor of the --continue as an API. I'd suggest responding to
resource timeouts and if there is no response from the task, then
re-start (continue)
the task.
Yeah, I am not in favour of a new API either. In fact, I believe we
already have
Steve,
Auto recovery is the plan. Engine failure should be detected by way of
heartbeat or recover partially realised stack on engine startup in case of
a single engine scenario.
--continue command was just a additional helper api.
[image: --]
Visnusaran Murugan
[image:
to realize a partially
completed stack.
Your thoughts.
From: vishnu [mailto:ckmvis...@gmail.com]
Sent: Friday, January 9, 2015 10:08 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Heat] Precursor to Phase 1 Convergence
Steve,
Auto recovery
completed stack.
Your thoughts.
*From:* vishnu [mailto:ckmvis...@gmail.com]
*Sent:* Friday, January 9, 2015 10:08 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Heat] Precursor to Phase 1 Convergence
Steve,
Auto recovery
On Thu, Jan 08, 2015 at 09:53:02PM +0530, vishnu wrote:
Hi Zane,
I was wondering if we could push changes relating to backup stack removal
and to not load resources as part of stack. There needs to be a capability
to restart jobs left over by dead engines.A
something like heat
Hi Zane,
I was wondering if we could push changes relating to backup stack removal
and to not load resources as part of stack. There needs to be a capability
to restart jobs left over by dead engines.
something like heat stack-operation --continue [git rebase --continue]
Had a chat with shady
