Dmitri,
Right now https://etherpad.openstack.org/p/mistral-poc is the only place where
we described it. It shouldn’t be considered a specification, it was rather a
playground where we tried to shape up our ideas. We’ll fix it using our latest
ideas and changes captured in the code and create an
On 15 Feb 2014, at 04:01, Nikolay Makhotkin wrote:
> Dmitri, in our concerns under word 'input' we assume a block 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?
Ok, I see.
Do we have a spec that describes this?
Lets spell it out and describe the whole picture of input, output, parameters,
and result.
DZ>
On Feb 14, 2014, at 1:01 PM, Nikolay Makhotkin wrote:
> Dmitri, in our concerns under word 'input' we assume a block contains the
> info about
Dmitri, in our concerns under word 'input' we assume a block 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
I like output, too. But it should go with 'input'
In summary, there are two alternatives.
Note that I moved task-parameters under parameters. Ok with this?
actions:
my-action
input:
foo: bar
task-parameters:
flavor_id:
image_
“output” looks nice!
Renat Akhmerov
@ Mirantis Inc.
On 14 Feb 2014, at 20:26, Nikolay Makhotkin wrote:
> Current DSL snippet:
> actions:
>my-action
> parameters:
> foo: bar
> response: # just agreed to change to 'results'
> select: '$.server_id'
Current DSL snippet:
actions:
my-action
parameters:
foo: bar
response: # just agreed to change to 'results'
select: '$.server_id'
store_as: v1
'result' sounds better than 'response' and, I think, more fit to action
description.
And I suggest
On 14 Feb 2014, at 15:02, Dmitri Zimine wrote:
> Current DSL snippet:
> actions:
>my-action
> parameters:
> foo: bar
> response: # just agreed to change to 'results’
Just a note: “response” indentation here is not correct, it’s not a parameter
called “response”
We touched this on review https://review.openstack.org/#/c/73205/, 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:
