On Apr 1, 2014, at 3:43 AM, Renat Akhmerov rakhme...@mirantis.com wrote:
On 25 Mar 2014, at 01:51, Joshua Harlow harlo...@yahoo-inc.com wrote:
The first execution model I would call the local execution model, this model
involves forming tasks and flows and then executing them inside an
Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Mistral][TaskFlow] Long running actions
On 25 Mar 2014, at 01:51, Joshua Harlow
harlo...@yahoo-inc.commailto:harlo...@yahoo-inc.com wrote
Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Mistral][TaskFlow] Long running actions
On Apr 1, 2014, at 3:43 AM, Renat Akhmerov
rakhme...@mirantis.commailto:rakhme...@mirantis.com wrote:
On 25 Mar 2014
Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Mistral][TaskFlow] Long running actions
On Apr 1, 2014, at 3:43 AM, Renat Akhmerov rakhme...@mirantis.com wrote:
On 25 Mar 2014, at 01:51, Joshua Harlow harlo...@yahoo-inc.com wrote
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Tuesday, April 1, 2014 at 2:59 PM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Mistral][TaskFlow] Long running actions
(not for usage questions)
openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Mistral][TaskFlow] Long running actions
Will advise soon, out sick with not so fun case of poison oak, will reply
next week (hopefully) when I'm less incapacitated...
Sent from my really tiny device
-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Mistral][TaskFlow] Long running actions
=== Long-running delegate [1] actions ==
Yes, the third model of lazy / passive engine is needed.
Obviously workflows contain a mix of different tasks, so this 3rd model should
handle both normal tasks
On 03/21/2014 12:33 AM, W Chan wrote:
Can the long running task be handled by putting the target task in the
workflow in a persisted state until either an event triggers it or
timeout occurs? An event (human approval or trigger from an external
system) sent to the transport will rejuvenate
Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Mistral][TaskFlow] Long running actions
Will advise soon, out sick with not so fun case of poison oak, will reply next
week (hopefully) when I'm
Don't forget HA issues. Mistral can be restarted at any moment and need to
be able to proceed from the place it was interrupted on another instance.
In theory it can be addressed by TaskFlow but I'm not sure it can be done
without complete redesign of it
On Fri, Mar 21, 2014 at 8:33 AM, W Chan
Valid concerns. It would be great to get Joshua involved in this discussion. If
it’s possible to do in TaskFlow he could advise on how exactly.
Renat Akhmerov
@ Mirantis Inc.
On 21 Mar 2014, at 16:23, Stan Lagun sla...@mirantis.com wrote:
Don't forget HA issues. Mistral can be restarted at
Will advise soon, out sick with not so fun case of poison oak, will reply next
week (hopefully) when I'm less incapacitated...
Sent from my really tiny device...
On Mar 21, 2014, at 3:24 AM, Renat Akhmerov
rakhme...@mirantis.commailto:rakhme...@mirantis.com wrote:
Valid concerns. It would be
For the 'asynchronous manner' discussion see http://tinyurl.com/n3v9lt8; I'm
still not sure why u would want to make is_sync/is_async a primitive concept
in a workflow system, shouldn't this be only up to the entity running the
workflow to decide? Why is a task allowed to be sync/async,
Can the long running task be handled by putting the target task in the
workflow in a persisted state until either an event triggers it or timeout
occurs? An event (human approval or trigger from an external system) sent
to the transport will rejuvenate the task. The timeout is configurable by
14 matches
Mail list logo
