Ok, no problem :)
Renat Akhmerov
@ Mirantis Inc.
On 16 Apr 2014, at 12:43, Joshua Harlow harlo...@yahoo-inc.com wrote:
I have stricken the word micro and language from my vocabulary. Begone
evil demons!! Haha :)
Sent from my really tiny device...
On Apr 15, 2014, at 10:35 PM, Renat
Some notes:
Even though we use YAQL now our design is flexible enough to plug other ELs in.
If it tells you something in Amazon SWF a component that makes a decision about
a further route is called Decider.
This discussion about conditionals is surely important but it doesn’t matter
too much if
Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Mistral][TaskFlow] Mistral-TaskFlow Summary
Some notes:
* Even though we use YAQL now our design is flexible enough to plug other
ELs
On 16 Apr 2014, at 00:18, Joshua Harlow harlo...@yahoo-inc.com wrote:
Decider sounds like it could work also as a name, although it seems from
dataflow like work its called a switch or gate, either or I guess.
That’s fine. It doesn’t matter too much to me personally.
As far as the
I have stricken the word micro and language from my vocabulary. Begone evil
demons!! Haha :)
Sent from my really tiny device...
On Apr 15, 2014, at 10:35 PM, Renat Akhmerov
rakhme...@mirantis.commailto:rakhme...@mirantis.com wrote:
On 16 Apr 2014, at 00:18, Joshua Harlow
Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Mistral][TaskFlow] Mistral-TaskFlow Summary
We prototyped Mistral / TaskFlow integration and have a follow-up
discussions.
SUMMARY: Mistral (Workflow Service) can embed TaskFlow as a workflow
Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Mistral][TaskFlow] Mistral-TaskFlow Summary
The more the better :)
If seriously, this one is less detailed and rather focuses on high-level things
, April 11, 2014 at 9:55 AM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Mistral][TaskFlow] Mistral-TaskFlow Summary
We prototyped Mistral / TaskFlow integration and have a follow-up
, 2014 at 9:55 AM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org (mailto:openstack-dev@lists.openstack.org)
Subject: [openstack-dev] [Mistral][TaskFlow] Mistral-TaskFlow Summary
We prototyped Mistral / TaskFlow integration and have a follow
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Mistral][TaskFlow] Mistral-TaskFlow Summary
They are all parts of conditional transitions: every task should have a number
of possible transitions; each transition consist of a reference to the task we
want to transit
We prototyped Mistral / TaskFlow integration and have a follow-up discussions.
SUMMARY: Mistral (Workflow Service) can embed TaskFlow as a workflow library,
with some required modifications to function resliently as a service, and for
smooth integration. However, the TaskFlow flow controls are
)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Friday, April 11, 2014 at 9:55 AM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Mistral][TaskFlow
12 matches
Mail list logo
