Winson, thanks for the etherpad to gather different opinions.
Dmitri, I think it's ok we discuss here, make more people get
involved, we could use etherpad for summary.
On Wed, Jun 17, 2015 at 2:22 AM, W Chan wrote:
> Here's the etherpad link. I replied to the comments/feedbacks there.
> Please
Here's the etherpad link. I replied to the comments/feedbacks there.
Please feel free to continue the conversation there.
https://etherpad.openstack.org/p/mistral-resume
__
OpenStack Development Mailing List (not for usage que
> So in an error state we will create new executor and just re run it
> Thanks Limor
>
>
>
> -Original Message-
> From: Lingxian Kong [mailto:anlin.k...@gmail.com]
> Sent: Tuesday, June 16, 2015 5:47 AM
> To: OpenStack Development Mailing List (not for usage ques
From: Lingxian Kong [mailto:anlin.k...@gmail.com]
Sent: Tuesday, June 16, 2015 5:47 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Mistral] Proposal for the Resume Feature
Thanks Winson for the write-up, very detailed infomation. (the format was good)
I&#
Thanks Winson for the write-up, very detailed infomation. (the format was good)
I'm totally in favor of your idea, actually, I really think you
proposal is complementary to my proposal in
https://etherpad.openstack.org/p/vancouver-2015-design-summit-mistral,
please see 'Workflow rollback/recovery'
Resending to see if this fixes the formatting for outlines below.
I want to continue the discussion on the workflow "resume" feature.
Resuming from our last conversation @
http://lists.openstack.org/pipermail/openstack-dev/2015-March/060265.html.
I don't think we should limit how users resume.
I want to continue the discussion on the workflow "resume" feature.
Resuming from our last conversation @
http://lists.openstack.org/pipermail/openstack-dev/2015-March/060265.html.
I don't think we should limit how users resume. There may be different
possible scenarios. User can fix the environm
Hi,
Thanks guys for bringing this topic up to discussion. In my opinion, this
feature is extremely important and will move Mistral further to being a truly
useful tool. I think it’s one of the “must have” feature of Mistral.
> On 31 Mar 2015, at 08:56, Dmitri Zimine wrote:
>
> @Lingxian Kong
Thanks Winson for the summary.
@Lingxian Kong
> The context for a task is used
> internally, I know the aim for this feature is to make it very easy
> and convinient for users to see the details for the workflow exection,
> but what users can do next with the context? Do you have a plan to
> cha
On Fri, Mar 27, 2015 at 11:20 AM, W Chan wrote:
> We assume WF is in paused/errored state when 1) user manually pause the WF,
> 2) pause is specified on transition (on-condition(s) such as on-error), and
> 3) task errored.
>
> The resume feature will support the following use cases.
> 1) User resu
We assume WF is in paused/errored state when 1) user manually pause the WF,
2) pause is specified on transition (on-condition(s) such as on-error), and
3) task errored.
The resume feature will support the following use cases.
1) User resumes WF from manual pause.
2) In the case of task failure, us
11 matches
Mail list logo
