Re: [openstack-dev] [FaaS] Function as a service in OpenStack

2017-05-06 Thread Dmitri Zimine
loud-self-healing/ [3] Integration points (aka packs) On Sat, May 6, 2017 at 12:25 PM, Dmitri Zimine <> wrote: > > > From: Lingxian Kong <> > Reply-To: "OpenStack Development Mailing List (not fo

Re: [openstack-dev] [mistral] Who's interested in attending PTG?

2016-10-14 Thread Dmitri Zimine
StackStorm is game for PGT: Winson will likely be there for Mistral F2F: from what we see now it’s quite a few things where F2F get-together can help & accelerate. So if Renat you’re in, we have 3 companies. Cheers, Dmitri.

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

2015-10-17 Thread Dmitri Zimine
Tony, You can also connect Mistral with Ansible via StackStorm and Ansible integration pack: 1) StackStorm 2) StackStorm is open-source Apache 2.0 “wrapper” around Mistral workflow service that

Re: [openstack-dev] [mistral][yaql] Addressing task result using YAQL function

2015-09-05 Thread Dmitri Zimine
that renaming the task is a source of too many frustrating errors :) What other think? DZ. On Sep 3, 2015, at 4:23 AM, Renat Akhmerov <> wrote: > >> On 02 Sep 2015, at 21:01, Dmitri Zimine <> wrote: >> >> Agree, >>

Re: [openstack-dev] [mistral][yaql] Addressing task result using YAQL function

2015-09-02 Thread Dmitri Zimine
Agree, with one detail: make it explicit - task(task_name). res - we often see folks confused by result of what (action, task, workflow) although we cleaned up our lingo: action-output, task-result, workflow-output…. but still worth being explicit. And full result is being thought as the

Re: [openstack-dev] [Mistral][Murano] What's the latest/greatest on YAQL?

2015-08-13 Thread Dmitri Zimine
Goirand wrote: On 06/30/2015 07:09 AM, Dmitri Zimine wrote: Thanks Stan, This release is few more months. How soon? Are you planning to support 0.2 in the meantime? We are really pressed on this transition to 1.0. For instance. Number 1 user error while dealing with YAQL

Re: [openstack-dev] [mistral] [murano] An online YAQL evaluator

2015-08-04 Thread Dmitri Zimine
Awesome! Really. Thank you folks for doing this. I am so much looking forward to moving it to 1.0 with more built-in functions and more power to extend it... Note that Mistral has a few extensions, like `str`, `len`, which are not in the scope of evaluator. DZ On Aug 2, 2015, at 12:44

Re: [openstack-dev] [mistral] BPMN support

2015-08-04 Thread Dmitri Zimine
Hi Noy, The short answer is No, BPMN is currently not supported, and No, we didn’t hear requests to support it yet. It is architecturally feasible but is a substantial effort, and not on the current roadmap. The longer answer is: Both Mistral DSL and BPMN come from the common root of

Re: [openstack-dev] [murano] [mistral] [yaql] Prepare to Yaql 1.0 release

2015-08-04 Thread Dmitri Zimine
This is great news Alex, was looking forward to it, will be happy to migrate Mistral. Some heads-up on what syntactically changed would be much appreciated to pass on to our users; we likely will catch much of them with Mistral tests, but some may bubble up. DZ. On Jul 27, 2015, at 2:04

Re: [openstack-dev] [murano] [mistral] [yaql] Prepare to Yaql 1.0 release

2015-08-04 Thread Dmitri Zimine
) for that Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis On Tue, Aug 4, 2015 at 9:57 PM, Dmitri Zimine wrote: This is great news Alex, was looking forward to it, will be happy to migrate Mistral. Some heads-up on what syntactically changed

Re: [openstack-dev] [Mistral][Murano] What's the latest/greatest on YAQL?

2015-06-29 Thread Dmitri Zimine
, it’s a pretty important thing that we’d like to clarify as soon as possible. Any input from Murano team? Renat Akhmerov @ Mirantis Inc. On 26 Jun 2015, at 06:01, Dmitri Zimine wrote: Folks, it’s been some time,what’s the news: * Is Murano moving YAQL

[openstack-dev] [Mistral][Murano] What's the latest/greatest on YAQL?

2015-06-25 Thread Dmitri Zimine
Folks, it’s been some time,what’s the news: * Is Murano moving YAQL 1.0 in this cycle? * What’s your recommendation for this cycle - stay on 0.2.6 or move on? * Any progress on documentation? Thanks, DZ __ OpenStack

Re: [openstack-dev] [Mistral] Proposal for the Resume Feature

2015-06-16 Thread Dmitri Zimine
+1 great write-up Winson, I propose we move the discussion to an etherpad, and flash out details there so it won’t get lost in a long thread. Winson would you care to create one and post here? Re: ‘error state’: I think it’s not absolutely necessary: pause/resume can be done without enabling

[openstack-dev] [Mistral] remind me about with_items concurrency

2015-05-13 Thread Dmitri Zimine
Folks, pls remind me where we ended up with ‘concurrency’? In the current implementation concurrency is a task policy (and not sure how much we tested it, not with unit testing/automated testing). Also I recall discussing/ going back and forth re if concurrency is a task policy or it belongs

Re: [openstack-dev] [mistral] Break_on in Retry policy

2015-04-22 Thread Dmitri Zimine
may be not quite - please advice how it works in these cases 1) if break-on expression contains the reference to task result, like break-on: % $ = true % but action returns ERROR and task payload is None (desired behavior: don’t puke, evaluate to false and don’t break) 2) if

Re: [openstack-dev] [Mistral] [Murano] Mistral devstack installation is failing in murano gate job

2015-04-13 Thread Dmitri Zimine
My 2c: Yes Mistral moved to YAQL 1.0 based on Murano team recommendations :) some questions/comments before we decide how to proceed: 1) Let’s clarify the impact: this problem doesn’t affect Murano directly; but it impacts Murano-Congress-Mistral initiative, correct? Is this a voting gate?

[openstack-dev] [Mistral] Upgrading to YAQL 1.0

2015-04-06 Thread Dmitri Zimine
Renat, following up on the IRC meeting: I recalled one more item, and registered a blueprint - think it’s good timing to do it in Kilo if YAQL 1.0 is announced; so I propose it for Kilo-rc1; One question is when YAQL 1.0 is going to

[openstack-dev] [Mistral] Propose Winson Chan m4dcoder for core team

2015-04-06 Thread Dmitri Zimine
Hi folks, I’d like to propose Winson Chan (m4dcoder) to become Mistral core team member. Winson brings unique mix of field experience implementing Mistral workflows in user environments, and solid development skills. He has been contributing to Mistral since Mar 2014. Winson did a 23

Re: [openstack-dev] [openstack][Mistral] DSL improvements - certain and incubating

2015-04-02 Thread Dmitri Zimine
Team, thanks for your input so far, I flashed out one more section, please take a look and comment DZ. On Mar 25, 2015, at 9:41 AM, Dmitri Zimine

[openstack-dev] [TC][Mistral] Workflow Service project proposal

2015-04-02 Thread Dmitri Zimine
the proposal at your earliest convenience, happy to answer questions and give more information here, or IRC on the #openstack-mistral. Thanks, Dmitri Zimine (irc dzimine) on behalf of Mistral contributors. [1]

Re: [openstack-dev] [Mistral] Proposal for the Resume Feature

2015-03-30 Thread Dmitri Zimine
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 change

[openstack-dev] [openstack][Mistral] DSL improvements - certain and incubating

2015-03-25 Thread Dmitri Zimine
Folks, we are discussing DSL improvements, based on Mistral field use and lessons learned. Please join: comment on the document welcome, extra ideas, preferably based on your experience writing Mistral workflows. The summary is in the doc, it contains two sections: 1) certain improvements,

[openstack-dev] [Mistral] Mistral sublime plugin available

2015-03-13 Thread Dmitri Zimine
Mistral team got an exciting contribution: our good friend and industry veteran GP De Ciantis had built a sublime plugin for Mistral DSL - workbooks, workflows, etc. Check it out, and enjoy writing Mistral workflows! Thanks GP for an excellent

Re: [openstack-dev] [Mistral] Changing expression delimiters in Mistral DSL

2015-02-18 Thread Dmitri Zimine
16:06, Dmitri Zimine wrote: 2) Use functions, like Heat HOT or TOSCA: HOT templates and TOSCA doesn’t seem to have a concept of typed variables to borrow from (please correct me if I missed it). But they have functions: function: { function_name: {foo: [parameter1, parameter 2], bar:xxx

Re: [openstack-dev] [Mistral] Changing expression delimiters in Mistral DSL

2015-02-18 Thread Dmitri Zimine
2015, at 03:06, Dmitri Zimine wrote: SUMMARY: We are changing the syntax for inlining YAQL expressions in Mistral YAML from {1+$.my.var} (or “{1+$.my.var}”) to % 1+$.my.var % Below I explain the rationale and the criteria for the choice. Comments

[openstack-dev] [Mistral] Changing expression delimiters in Mistral DSL

2015-02-16 Thread Dmitri Zimine
SUMMARY: We are changing the syntax for inlining YAQL expressions in Mistral YAML from {1+$.my.var} (or “{1+$.my.var}”) to % 1+$.my.var % Below I explain the rationale and the criteria for the choice. Comments and suggestions welcome. DETAILS: - We faced a

Re: [openstack-dev] [Murano][Heat][Mistral] Use and adoption of YAQL

2015-02-06 Thread Dmitri Zimine
and adopted OpenStack development process and tools but the work is still in progress. Any help from Mistral team and/or other YAQL adopters is appreciated. Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis On Thu, Jan 15, 2015 at 10:54 PM, Dmitri Zimine dzim

[openstack-dev] [Murano][Heat][Mistral] Use and adoption of YAQL

2015-01-15 Thread Dmitri Zimine
Folks, We use YAQL in Mistral for referencing variables, expressing conditions, etc. Murano is using it extensively, I saw Heat folks thought of using it, at least once :) May be others... We are learning that YAQL incredibly powerful comparing to alternatives like Jinja2 templates used in

[openstack-dev] [Mistral] Access to worklfow/task results without implicit publish

2014-12-22 Thread Dmitri Zimine
The problem: Refer to workflow / action output without explicitly re-publishing the output values. Why we want it: to reduce repetition, and to make modifications in the place values are used, not where they are obtained (and not in multiple places). E.g., as an editor of a workflow, when I

Re: [openstack-dev] [Mistral] For-each

2014-12-19 Thread Dmitri Zimine
Thanks Angus. One obvious thing is we either make it somewhat consistent, or name it differently. These looks similar, at least on the surface. I wonder if the feedback we’ve got so far (for-each is confusing because it brings wrong expectations) is applicable to Heat, too. Another

Re: [openstack-dev] [Mistral] Plans to load and performance testing

2014-12-19 Thread Dmitri Zimine
Anastasia, any start is a good start. 1 api 1 engine 1 executor, list-workbooks what exactly doest it mean: 1) is mistral deployed on 3 boxes with component per box, or all three are processes on the same box? 2) is list-workbooks test running while workflow executions going on? How many?

Re: [openstack-dev] [Mistral] For-each

2014-12-18 Thread Dmitri Zimine
Based on the feedback so far, I updated the document and added some more details from the comments and discussions. We still think for-each as a keyword confuses people by setting up some behavior expectations (e.g., it will run sequentially, you can work with data inside the loop, you can

Re: [openstack-dev] [Mistral] RFC - Action spec CLI

2014-12-17 Thread Dmitri Zimine
The problem with existing syntax is it is not defined: there is no docs on inlining complex variables [*], and we haven’t tested it for anything more than the simplest cases: I will be

Re: [openstack-dev] [Mistral] For-each

2014-12-15 Thread Dmitri Zimine
I had a short user feedback sessions with Patrick and James, the short summary is: 1) simplify the syntax to optimize for the most common use case 2) 'concurrency' is the best word - but bring it out of for-each to task level, or task/policies 3) all-permutation - relatively rare case, either

Re: [openstack-dev] [Mistral] Global Context and Execution Environment

2014-12-12 Thread Dmitri Zimine
Winson, Lakshmi, Renat: It looked good and I began to write down the summary: But than realized that it’s not safe to assume from the action, that the global context will be supplied as part of API call. Check it out in the etherpad.

Re: [openstack-dev] Mistral - Real Time integration

2014-10-30 Thread Dmitri Zimine
Hi Raanan, 1) yes, the workflow execution can be triggered by the REST API call. 2) yes the Mistral is the closest in OpenStack for the higher-level automation and integration across operations and with external systems. Are you coming to OpenStack summit by any chance? Your comments expose

[openstack-dev] [Mistral] Moving docs from wiki to mistral/doc

2014-10-07 Thread Dmitri Zimine
Folks, I have moved the DSL and API docs to the project (up on review). Now it contains enough examples to get going, also see doc/ for some useful hints. Renat, Nikolay, if you find any omissions please add; and once we are happy let’s remove the DSL and API wiki to avoid confusion.

Re: [openstack-dev] [mistral] Mistral 0.2 planning

2014-10-02 Thread Dmitri Zimine
Thanks Renat for running and capturing. One addition - allocate time for bug fixes, we’ll have quite a few :) DZ. On Oct 2, 2014, at 9:56 PM, Renat Akhmerov wrote: Hi, Mistral team has selected blueprints for Mistral 0.2 which is currently scheduled for 10/31/2014

[openstack-dev] [Mistral] callback on workflow completion

2014-09-17 Thread Dmitri Zimine
Use case: The client software fires the workflow execution and needs to be know when the workflow is complete. There is no good pool strategy as workflow can take arbitrary time from ms to days. Callback notification is needed. Solution is a webhook Option 1: pass callback URL as part of

[openstack-dev] [Mistral] how to make Mistral build after keystone-pythonclient

2014-08-29 Thread Dmitri Zimine
Once we got dependencies on keystone-python client, Mistral doesn’t build for me on Mac. Before, I installed a new openssl (1.0.1h) - keystone authentication didn’t work with out it, remember? enykeev suggested to return to the old stock openssl, it worked. but this sort of sucks to switch

[openstack-dev] [mistral] Mistral API v2 - discussion

2014-08-21 Thread Dmitri Zimine
Hi Stackers, we are discussing the API, v2. The core team captured the initial thoughts here (most recent): and here: Have a

[openstack-dev] [Mistral] Mistral milestone 0.1 blueprint review

2014-08-13 Thread Dmitri Zimine
Renat, team: The current plan of record on 0.1 here, Some suggested adjustments: Pls use the doc to comment/disccuss and let’s decide by next

[openstack-dev] [Mistral] Small questions re executor

2014-06-24 Thread Dmitri Zimine
Got some questions while fixing a bug * We must convey the action ERROR details back to the engine, and to the end user. Log is not sufficient. How exactly? Via context? Via extra parameters to convey_execution_results? Need a field in the model.

[openstack-dev] [Mistral] Start task, and support for 'requires' / reverse workflow.

2014-06-19 Thread Dmitri Zimine Angus asked: Why do we even need start: start-task? Can't we parse the workbook and figure out what to run? Tasks at the bottom of the tree have no on-{fail,success} and then follow upwards until you find a task that is not referenced by anything. Yes

[openstack-dev] [Mistral] Community meeting reminder - 06/02/2014

2014-06-02 Thread Dmitri Zimine
Hi, This is a reminder about the community meeting in IRC June 02 at 16.00 UTC at #openstack-meeting. Agenda: Review action items Current status (quickly by team members) Further plans Open discussion You can also find it at as well as

[openstack-dev] [Mistral] Mistral roadmap notes, from Atlanta summit (rough)

2014-05-20 Thread Dmitri Zimine
We shared and discussed the directions on Mistral development session, and work through the list of smaller post POC steps, placing them on the roadmap. The notes are here: Renat and I developed shared understanding on most of them. Next

Re: [openstack-dev] [Mistral] Cleaning up configuration settings

2014-05-16 Thread Dmitri Zimine
+1 for breaking down the configuration by modules. Not sure about names for configuration group. Do you mean just using the same group name? or more? IMO groups are project specific; it doesn’t always make sense to use the same group name in the context of different projects. Our requirement

[openstack-dev] [Search] Search project - update Atlanta'14

2014-05-16 Thread Dmitri Zimine
Hi folks, Last summit we proposed Search project for OpenStack[1]. We didn't get much traction and other things took priorities, so the project didn't take off during Havana cycle. Now - before and during the summit - more people expressed keen interest. Some of us met on the summit and

[openstack-dev] [Mistral][TaskFlow] Integration plan

2014-05-15 Thread Dmitri Zimine
Renat, Joshua, Dmitri and Timur discussed the integration path for Mistral and TaskFlow. Quick summary - guys please correct any mistakes or omissions: Taskflow - Mistral integration plan 1) Mistral: define the set of workflow primitives, define correspondent DSL - Driven by user

[openstack-dev] [Mistral] Why keystone token validation fails in PyCharm, and how to fix it

2014-05-12 Thread Dmitri Zimine
The problem: Keystone authentication on MAC works from command line, but fails when run from PyCharm. And I want to run PyCharm to debug! The root cause: Keystone uses openssl cms which is only available in new openssl. I installed openssl via brew, and got it in /usr/local/bin. Terminal

Re: [openstack-dev] [mistral] [taskflow] Mistral TaskFlow integration summary

2014-04-24 Thread Dmitri Zimine
Ivan, any update/progress on this? Thanks, DZ. On Apr 15, 2014, at 10:21 AM, Joshua Harlow wrote: Well Ivan afaik is thinking through it, but being a community project its not exactly easy to put estimations or timelines on things (I don't control Ivan, or

[openstack-dev] [Mistral][TaskFlow] Mistral-TaskFlow Summary

2014-04-11 Thread Dmitri Zimine
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] [Mistral][Taskflow] meet on IRC to talk over TaskFlow/Mistral integration

2014-04-03 Thread Dmitri Zimine
IRC to discuss Joshua, 2000 UTC doesn't quite work for Renat and Kirill (3 am their time). The overlap is: PST (UTC-7) UTC NOVT (UTC+7) 04pm (16:00)11pm (23:00)6am (06:00) 10pm (22:00)05am (05:00)12pm (12:00) Kirill's

[openstack-dev] [Mistral] Next crack at real workflows

2014-04-02 Thread Dmitri Zimine
Two more workflows drafted - cloud cron, and lifecycle, version 1. The mindset questions are: 1) is DSL syntax expressive, and capable and convenient to handle real use cases? 2) most importantly: what are the implied workflow capabilities which make it all work? * Take a look here:

Re: [openstack-dev] [Mistral] How Mistral handling long running delegate tasks

2014-04-01 Thread Dmitri Zimine
Even more responses inline :) On Mar 31, 2014, at 8:44 PM, Joshua Harlow wrote: More responses inline :) From: Dmitri Zimine Date: Monday, March 31, 2014 at 5:59 PM To: Joshua Harlow Cc: OpenStack Development Mailing List

Re: [openstack-dev] [Mistral][TaskFlow] Long running actions

2014-04-01 Thread Dmitri Zimine
On Apr 1, 2014, at 3:43 AM, Renat Akhmerov wrote: On 25 Mar 2014, at 01:51, Joshua Harlow 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

[openstack-dev] [Mistral] Review reminder

2014-04-01 Thread Dmitri Zimine
We agreed to review this and if/when OK, fix the murano-cli. Can you guys please take a look? DZ ___ OpenStack-dev mailing list

Re: [openstack-dev] [Mistral] Engine overview and proposal

2014-03-31 Thread Dmitri Zimine
I am in the full agreement with the proposed approach (risked to copy below, let's see if email handles your diagrams): * Single Engine handles multiple executions asynchronously, in non-blocking way. * Persistence access only from API and/or Engine, Engine writes, API reads. * Action runes

Re: [openstack-dev] [Mistral] How Mistral handling long running delegate tasks

2014-03-31 Thread Dmitri Zimine
/TaskFlow#Retries (new feature!) This is nice. I would call it a 'repeater': running a sub flow several times with various data for various reasons is reacher then 'retry'. What about the 'retry policy' on individual task? From: Dmitri Zimine Reply-To: OpenStack Development

[openstack-dev] [Mistral] Community meeting reminder - 03/30/2014

2014-03-30 Thread Dmitri Zimine
on top of TaskFlow prototype - summary, next steps Open discussion Looking forward to see you there. Dmitri Zimine @ StackStorm PS. Hope Renat is coming back this week. ___ OpenStack-dev mailing list http

[openstack-dev] [Mistral] How Mistral handling long running delegate tasks

2014-03-27 Thread Dmitri Zimine
Following up on and this explains how Mistral handles long running delegate tasks. Note that a 'passive' workflow engine can handle both normal tasks and delegates the same way. I'll also put that on ActionDesign wiki, after discussion.

Re: [openstack-dev] [Mistral][TaskFlow] Long running actions

2014-03-26 Thread Dmitri Zimine
other options to schedule tasks in TaskFlow, if we have too many of these workflows with long running tasks, seems like it'll become a memory issue for mistral... On Thu, Mar 20, 2014 at 3:07 PM, Dmitri Zimine wrote: For the 'asynchronous manner' discussion see http

Re: [openstack-dev] [Mistral] task update at end of handle_task in executor

2014-03-26 Thread Dmitri Zimine
My understanding is: it's the engine which finalizes the task results, based on the status returned by the task via convey_task_result call.

[openstack-dev] [Mistral] Community meeting minutes - 03/24/2014

2014-03-24 Thread Dmitri Zimine
Hi folks, thanks for taking part in Mistral meeting on #openstack-meeting Here is the minutes and the full log. Minutes Log:

[openstack-dev] [Mistral][TaskFlow] Long running actions

2014-03-20 Thread Dmitri Zimine
For the 'asynchronous manner' discussion see; 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,

Re: [openstack-dev] [openstack][Mistral] Adding new core reviewers

2014-03-19 Thread Dmitri Zimine
(design, reviews, code). Dmitri Zimine (i-dz at launchpad). Dmitri joined the project about 2 months ago. Since then he’s made a series of important high-quality commits, a lot of valuable reviews and, IMO most importantly, he has a solid vision of the project in general (requirements, use

Re: [openstack-dev] [Mistral] Actions design BP

2014-03-13 Thread Dmitri Zimine
Thanks Renat for a clear design summary, thanks Joshua for the questions, +1 to let's move TaskFlow vs Mistral discussion to separate thread, and my questions/comments on below: - Async actions: how do results of async action

Re: [openstack-dev] [Mistral] Local vs. Scalable Engine

2014-03-13 Thread Dmitri Zimine
We have access to all configuration parameters in the context of May be you don't pass it but just instantiate it where you need it? Or I may misunderstand what you're trying to do... DZ PS: can you generate and update mistral.config.example to include new oslo messaging options? I

Re: [openstack-dev] [Mistral] Crack at a Real life workflow

2014-03-06 Thread Dmitri Zimine
of that real-world workflow look like? Then we can ask ourselves, does the DSL make this better or worse? Would we need to expose things like email handlers, or leave that to the general python libraries? $0.02 -S On 03/05/2014 10:50 PM, Dmitri Zimine wrote: Folks, I took a crack

Re: [openstack-dev] [Mistral] Crack at a Real life workflow

2014-03-06 Thread Dmitri Zimine
I just moved the sample to Git; let's leverage git review for specific comments on the syntax. DZ On Mar 6, 2014, at 10:36 PM, Dmitri Zimine wrote: Folks, thanks for the input

[openstack-dev] [Mistral] Crack at a Real life workflow

2014-03-05 Thread Dmitri Zimine
Folks, I took a crack at using our DSL to build a real-world workflow. Just to see how it feels to write it. And how it compares with alternative tools. This one automates a page from OpenStack operation guide:

Re: [openstack-dev] [Mistral] Renaming events to triggers and move them out of Workflow

2014-02-27 Thread Dmitri Zimine
Agree on both. On Feb 26, 2014, at 8:51 PM, Renat Akhmerov wrote: Hi team, When I tell peopleI about Mistral I always have a hard time explaining why we use term “event” for declaring ways to start workflows. For example, take a look at the following snippet:

Re: [openstack-dev] [Mistral] Understanding parameters for tasks and actions

2014-02-26 Thread Dmitri Zimine
My understanding, correct me if I'm missing the intention: Action are defined as code, aka REST_API or SEND_EMAIL. These are base actions, they are analogous to function definitions. Tasks is a set of parameters for the action. Actions can be also defined declaratively, under Services, based

Re: [openstack-dev] [Mistral] Renaming action types

2014-02-26 Thread Dmitri Zimine
+1 Should we use VERB_NOUN pattern? Or relax it for some obvious? I can't figure a good VERB_NOUN for HTTP. REQUEST_HTTP is dull. BTW it's interesting that we assume that a service can contain only actions of the same type. DZ On Feb 26, 2014, at 1:10 AM, Nikolay Makhotkin

Re: [openstack-dev] [Mistral] Defining term DSL

2014-02-26 Thread Dmitri Zimine
We do use the term DSL, I invite you guys to clarify, how exactly. Based on the terminology from [1], it's not part of the model, but the language that describes the model in the file. And theoretically this may be not the only language to express the workflow. Once the file is parsed, we

[openstack-dev] [Mistral] What is the model?

2014-02-26 Thread Dmitri Zimine
As a learning exercise, I was trying to extract the intend behind the DSL and current code. Giving that many things are still moving, I filled up the blanks with imagination. Here is my understanding on where you are going:

Re: [openstack-dev] [Mistral]

2014-02-25 Thread Dmitri Zimine
I have created a blueprint to capture the intention to simplify calling standard actions: DZ On Feb 11, 2014, at 7:40 AM, Dmitri Zimine wrote: Yes it makes sense, let's draft how it may look

Re: [openstack-dev] [Mistral] Local vs. Scalable Engine

2014-02-24 Thread Dmitri Zimine
I agree with Winson's points. Inline. On Feb 24, 2014, at 8:31 PM, Renat Akhmerov wrote: On 25 Feb 2014, at 07:12, W Chan wrote: As I understand, the local engine runs the task immediately whereas the scalable engine sends it over the message

Re: [openstack-dev] [Mistral] Porting executor and engine to oslo.messaging

2014-02-24 Thread Dmitri Zimine
Winson, While you're looking into this and working on the design, may be also think through other executor/engine communications. We talked about executor communicating to engine over 3 channels (DB, REST, RabbitMQ) which I wasn't happy about ;) and put it off for some time. May be it can be

[openstack-dev] [Mistral] Notes on action YAML declaration and naming

2014-02-14 Thread Dmitri Zimine
We touched this on review, and fixed a bit, bringing it up here to further discuss at slightly higher level. Let's go over a tiny bit of YAML definition, clarifying terminology on the way. Current DSL snippet: actions: my-action parameters:

Re: [openstack-dev] [Mistral] Notes on action YAML declaration and naming

2014-02-14 Thread Dmitri Zimine
: vm_id parameters: foo: bar On Fri, Feb 14, 2014 at 12:36 PM, Renat Akhmerov wrote: On 14 Feb 2014, at 15:02, Dmitri Zimine wrote: Current DSL snippet: actions: my-action parameters: foo

Re: [openstack-dev] [Mistral] Notes on action YAML declaration and naming

2014-02-14 Thread Dmitri Zimine
contains the info about how the input data will be taken for corresponding task from initial context. So, it will be a kind of expression (e.g. YAQL). Renat, am I right? On Fri, Feb 14, 2014 at 9:51 PM, Dmitri Zimine wrote: I like output, too. But it should go

[openstack-dev] [Mistral]

2014-02-11 Thread Dmitri Zimine
Do we have (or think about) a shorthand to calling REST_API action, without defining a service? FULL DSL: Services: TimeService: type: REST_API parameters: baseUrl: key:my_api_key actions: get-time:

Re: [openstack-dev] [Mistral]

2014-02-11 Thread Dmitri Zimine
to an action type rather than the action itself”. Does that make sense? Renat Akhmerov @ Mirantis Inc. On 11 Feb 2014, at 16:23, Dmitri Zimine wrote: Do we have (or think about) a shorthand to calling REST_API action, without defining a service? FULL DSL: Services

[openstack-dev] [Mistral] Comments on DSL

2014-02-04 Thread Dmitri Zimine
Ops! missed [openstack-dev], fixing… Following up from yesterday's community meeting I am still catching up with the project, still miss a lot of context. Put my questions and comments on DSL definition: Let's review, and thanks for

[openstack-dev] [Mistral] Comments on DSL

2014-02-04 Thread Dmitri Zimine
Following up from yesterday's community meeting I am still catching up with the project, still miss a lot of context. Put my questions and comments on DSL definition: Let's review, and thanks for helping us get up to speed. DZ