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

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

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

: result: select: '$.server_id' store_as: v1 this maps to result=action(parameters) On Feb 14, 2014, at 8:40 AM, Renat Akhmerov rakhme...@mirantis.com wrote: output looks nice! Renat Akhmerov @ Mirantis Inc. On 14 Feb 2014, at 20:26, Nikolay

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

Looks good. Thanks, Winson! Renat, What do you think? On Wed, Feb 26, 2014 at 10:00 AM, W Chan m4d.co...@gmail.com wrote: The following link is the google doc of the proposed engine/executor message flow architecture.

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

Hi, Renat! *Suggestions* *1*. Define input and output at task level like this: createVM: input: image_id: $.image_id output: vm_id Where output: vm_id is basically a replacement for store-as: vm_id at action level, i.e. it's a hint to Mistral to store the

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

Timur, '$' here is mean referrence to context at stage which it has been given to. '$.image_id' takes 'image_id' from current workflow execution context variable On Wed, Feb 26, 2014 at 12:30 PM, Nikolay Makhotkin nmakhot...@mirantis.com wrote: Hi, Renat! *Suggestions* *1*. Define input

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

Agree, I don't see any thing that makes sense with words 'REST' and 'API' too. On Wed, Feb 26, 2014 at 11:38 AM, Renat Akhmerov rakhme...@mirantis.comwrote: Folks, I'm proposing to rename these two action types REST_API and MISTRAL_REST_API to HTTP and MISTRAL_HTTP. Words REST and API don't

[openstack-dev] [Mistral] Defining term DSL

Due to the comment to https://review.openstack.org/#/c/75888/1 there is a quiestion: Do we use term DSL or something else? I think the word 'DSL' is more fit thing that we call 'workbook definition', some text describing workflows, services, tasks and actions. And processing module for this also

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

Yes, I also think this changes more refer to model than DSL On Fri, Feb 28, 2014 at 1:41 PM, Renat Akhmerov rakhme...@mirantis.comwrote: Yes. Guys, thanks for your feedback. I had a conversation with Dmitri today and realized you guys are right here. We should think about building basically

[openstack-dev] [Mistral] DSL model vs. DB model, renaming

Hi, team! Please look at the commit . Module 'mistral/model' now is responsible for object model representation which is used for accessing properties of actions, tasks etc. We have a name problem - looks like we should rename module 'mistral/model' since we have DB models and they are

Re: [openstack-dev] [Mistral] std:repeat action

Ok, Manas, I'll comment it very soon :) On Tue, Mar 4, 2014 at 6:47 AM, Manas Kelshikar ma...@stackstorm.comwrote: Ping! @Nikolay - Can you take a look at the etherpad discussion and provide comments. I am going to start working on option (I) as that is the one which seems to make most

Re: [openstack-dev] [Mistral] DSL model vs. DB model, renaming

should be able to avoid any confusion and whether or not model appears in the module name should not matter much. Thanks, Manas On Mon, Mar 3, 2014 at 8:43 AM, Nikolay Makhotkin nmakhot...@mirantis.com wrote: Hi, team! Please look at the commit . Module 'mistral/model' now

Re: [openstack-dev] [Mistral] DSL model vs. DB model, renaming

Manas, Renat, no problem :) The commit is sent already - https://review.openstack.org/#/c/75888/ On Thu, Mar 6, 2014 at 12:14 PM, Manas Kelshikar ma...@stackstorm.comwrote: I agree, let's rename data to spec and unblock the check-in. Nikolay - Sorry for the trouble :) On Mar 5, 2014 10:17

Re: [openstack-dev] [Mistral] Error on running tox

maybe something wrong with python2.6? .tox/py26/lib/python2.6/site-packages/mock.py, line 1201, in patched what if you try it on py27? On Wed, Mar 12, 2014 at 10:08 AM, Renat Akhmerov rakhme...@mirantis.comwrote: Ok. I might be related with oslo.messaging change that we merged in

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

In case of async tasks, executor keeps the task status at RUNNING, and a 3rd party system will call convey_task_resutls on engine. Yes, it is correct. With this approach (in case sync task), we set task state to SUCCESS if it returns a result, or ERROR if we can't see a result and exception

Re: [openstack-dev] [savanna] What's the recipe to build Oozie-4.0.0.tar.gz?

mailing listOpenStack-dev@lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Best Regards, Nikolay Makhotkin, Intern Software Engineer, Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev

[openstack-dev] [mistral] Team meeting minutes 09/29/2014

Thanks everyone for participating the meeting today! In case you’d like to see what we discussed, here’s Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-09-29-16.01.html Meeting full log:

[openstack-dev] [mistral] [fuel] Executor task affinity

Hi, folks! I drafted the document where we can see how task affinity will be applied to Mistral: https://docs.google.com/a/mirantis.com/document/d/17O51J1822G9KY_Fkn66Ul2fc56yt9T4NunnSgmaehmg/edit -- Best Regards, Nikolay @Mirantis Inc. ___

[openstack-dev] [mistral] Team meeting minutes 10/06/2014

Thanks everyone for participating the meeting today! In case you’d like to see what we discussed, here’s Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-10-06-16.00.html http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-10-06-16.00.html Meeting

Re: [openstack-dev] [Mistral] Event Subscription

Hi, Winson, This is great! But I have a question: 9. Operation in python-mistralclient to re-publish events for a given workflow execution (in case where client applications was downed and need the data to recover). How does Mistral know about all the events which it has already sent to

[openstack-dev] [mistral] Team meeting - 11/24/2014

This is a reminder about our team meeting scheduled for today 16.00 UTC. Agenda: - Review action items - Paris Summit results - Current status (progress, issues, roadblocks, further plans) - Release 0.2 progress - Open discussion -- Best Regards, Nikolay

[openstack-dev] [mistral] Team meeting minutes/log - 11/24/2014

Thanks for joining us today, Here are the links to the meeting minutes and full log: - Minutes - http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-11-24-16.00.html - Full log - *http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-11-24-16.00.log.html

[openstack-dev] [pecan] [WSME] Different content-type in request and response

Hi, folks! I try to create a controller which should receive one http content-type in request but it should be another content-type in response. I tried to use pecan and wsme decorators for controller's methods. I just want to receive text on server and send json-encoded string from server

Re: [openstack-dev] [Mistral] Query on creating multiple resources

Hi, Sushma! Can we create multiple resources using a single task, like multiple keypairs or security-groups or networks etc? Yes, we can. This feature is in the development now and it is considered as experimental - https://blueprints.launchpad.net/mistral/+spec/mistral-dataflow-collections

[openstack-dev] [mistral] Team meeting minutes/log 12/08/2014

Thanks for joining our team meeting today! * Meeting minutes: *http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-12-08-16.04.log.html http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-12-08-16.04.log.html* * Meeting log:

Re: [openstack-dev] [Mistral]

Guys, May be I misunderstood something here but what is the difference between this one and https://blueprints.launchpad.net/mistral/+spec/mistral-execution-environment ? On Tue, Dec 9, 2014 at 5:35 PM, Dmitri Zimine dzim...@stackstorm.com wrote: Winson, thanks for filing the blueprint:

[openstack-dev] [Mistral] For-each

Hi, Here is the doc with suggestions on specification for for-each feature. You are free to comment and ask questions. https://docs.google.com/document/d/1iw0OgQcU0LV_i3Lnbax9NqAJ397zSYA3PMvl6F_uqm0/edit?usp=sharing -- Best Regards, Nikolay ___

Re: [openstack-dev] [Mistral] Converging discussions on WF context and WF/task/action inputs

One thing that I strongly suggest is that we clearly define all reserved keys like “env”, “__actions” etc. I think it’d be better if they all started with the same prefix, for example, double underscore. I absolutely agree here. We should use specific keywords with __ prefix like we used

Re: [openstack-dev] [keystone] [nova]

AM, Nikolay Makhotkin wrote: Hi ! I investigated trust's use cases and encountered the problem: When I use auth_token obtained from keystoneclient using trust, I get *403* Forbidden error: *You are not authorized to perform the requested action.* Steps to reproduce: - Import v3

[openstack-dev] [keystone] [nova]

Hi ! I investigated trust's use cases and encountered the problem: When I use auth_token obtained from keystoneclient using trust, I get *403* Forbidden error: *You are not authorized to perform the requested action.* Steps to reproduce: - Import v3 keystoneclient (used keystone and

[openstack-dev] [mistral] Team meeting minutes 02/16/2015

Thanks for joining our team meeting today! * Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-02-16-16.00.html * Meeting log: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-02-16-16.00.log.html The next meeting is scheduled for Feb 23 at

Re: [openstack-dev] [keystone] [trusts] [all] How trusts should work by design?

Hello! Nova client's CLI parameter 'bypass_url' helps me. The client's API also has 'management_url' attribute, if this one is specified - the client doesn't reauthenticate. Also the most of clients have 'endpoint' argument, so client doesn't make extra call to keystone to retrieve new token and

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

Hi ! From those three I'd choose only { ... }, it looks better for YAML while '%' sign looks foreign for YAML. Moreover, it needs extra spaces for writing expressions: Compare: 1. %$.var + 1% 2. % $.var + 1 % 3. {$.var + 1} One more point from me: We can't do things just beacuse it is familiar

[openstack-dev] [keystone] [trusts] [all] How trusts should work by design?

and use it (but actually, we are not). Or am I misunderstanding trust's purpose? How are trusts should worked? [1] https://github.com/openstack/keystone/blob/master/keystone/token/controllers.py#L154-L156 Best Regards, Nikolay Makhotkin @Mirantis

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

Some suggestions from me: 1. y 1 + $.var # (short from yaql). 2. { 1 + $.var } # as for me, looks more elegant than % %. And visually it is more strong A also like p7 and p8 suggested by Renat. On Tue, Feb 17, 2015 at 11:43 AM, Renat Akhmerov rakhme...@mirantis.com wrote: One more: p9:

Re: [openstack-dev] [keystone] [nova]

...@redhat.com wrote: On 02/11/2015 12:16 PM, Nikolay Makhotkin wrote: No, I just checked it. Nova receives trust token and raise this error. In my script, I see: http://paste.openstack.org/show/171452/ And as you can see, token from trust differs from direct user's token. The original user

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

Ok, we will proceed with error-on and success-on. Thanks for the reply! -- Best Regards, Nikolay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

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

Hello, Recently we've found that break_on property of RetryPolicy is not working now. I tried to solve this problem but faced the another problem: How does 'break_on' supposed to work? Will 'break_on' change the task state to ERROR or SUCCESS? if ERROR, it means 'we interrupt all retry

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

Any more suggestions/thoughts here? Dmitri? More words: succeed-on / fail-on, success-expr / error-expr. -- Best Regards, Nikolay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

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

? Renat Akhmerov @ Mirantis Inc. On 21 Apr 2015, at 14:11, Nikolay Makhotkin nmakhot...@mirantis.com wrote: Any more suggestions/thoughts here? Dmitri? More words: succeed-on / fail-on, success-expr / error-expr. -- Best Regards, Nikolay

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

Hi, Dmitri! AFAIK, we made the decision that 'concurrency' is a policy (and our schema allows to add 'concurrency' property in DSL). On Wed, May 13, 2015 at 7:37 PM, Dmitri Zimine dzim...@stackstorm.com wrote: Folks, pls remind me where we ended up with ‘concurrency’? In the current

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

We are facing an issue with Mistral devstack installation in our gate job testing murano-congress-mistral integration (policy enforcement) [1] . Mistral devstack scripts are failing with following import error [2] Hi, Filip! Recently Mistral has moved to new YAQL, and it seems this

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

It would be good to see Winson as the core contributor in Mistral. +1 for Winson! On Tue, Apr 7, 2015 at 11:53 AM, Renat Akhmerov rakhme...@mirantis.com wrote: +1 with my both hands. Winson has been working on Mistral for about a year, was actively participating in the very first workflow

[openstack-dev] [mistral] Cancelling today's team meeting - 06/08/2015

Team, We decided to cancel today’s meeting because a number of key members won’t be able to attend. -- Best Regards, Nikolay @Mirantis Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [mistral] Proposing Lingxian Kong as a core reviewer

Hi, +1 for Lingxian! On Mon, Jun 22, 2015 at 7:08 PM, Nikolay Makhotkin nmakhot...@mirantis.com wrote: Hi, +1 for Lingxian! -- Best Regards, Nikolay -- Best Regards, Nikolay __ OpenStack Development Mailing List

Re: [openstack-dev] [Solum][Mistral] Help with a patch

Hi, Devdatta! Thank you for catching this and for the patch. I already reviewed it and it has been merged. -- Best Regards, Nikolay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [requirements] [global-requirements] [mistral] Using pika library

Hi, folks! Recently we've had the discussion with oslo.messaging team about acknowledge feature in RabbitMQ: http://lists.openstack.org/pipermail/openstack-dev/2015-July/068806.html After that Mistral team did the research about using *kombu *or *pika* library for implementation of remote

Re: [openstack-dev] [requirements] [global-requirements] [mistral] Using pika library

, Aug 19, 2015 at 7:21 AM, Nikolay Makhotkin nmakhot...@mirantis.com wrote: Hi, folks! Recently we've had the discussion with oslo.messaging team about acknowledge feature in RabbitMQ: http://lists.openstack.org/pipermail/openstack-dev/2015-July/068806.html After that Mistral team did

[openstack-dev] [mistral] Team meeting minutes

Thanks for joining the meeting today! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-08-24-16.01.html Meeting log: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-08-24-16.01.log.html The next meeting will be on Aug 3. You can post your

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

Hi guys! That's awesome! It is very useful for all us! -- Best Regards, Nikolay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [mistral] Team meeting reminder - 08/03/2015

Hi, This is a reminder that we’ll have a team meeting today at #openstack-meeting at 16.00 UTC. Agenda: - Review action items - Current status (progress, issues, roadblocks, further plans) - Liberty-2 release - Open discussion Add your own items either by replying to this email or

[openstack-dev] [mistral] Team meeting minutes

Thanks for joining the meeting today! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-07-27-16.01.html Meeting log: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-07-27-16.01.log.html The next meeting will be on Aug 3. You can post your

[openstack-dev] [mistral] Team meeting reminder - 07/20/2015

Hi, This is a reminder that we’ll have a team meeting today at #openstack-meeting at 16.00 UTC. Agenda: - Review action items - Current status (progress, issues, roadblocks, further plans) - Execution expiration policy discussion - Open discussion Add your own items either by

[openstack-dev] [mistral] Team meeting minutes/log - 07/20/2015

Thanks for joining the meeting today! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-07-20-16.00.html Meeting log: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-07-20-16.00.log.html The next meeting will be on July 27. You can post your

[openstack-dev] [oslo.messaging] [mistral] Acknowledge feature of RabbitMQ in oslo.messaging

Hi, I am using RabbitMQ as the backend and searched oslo.messaging for message acknowledgement feature but I found only [1] what is wrong using of acknowledgement since it acknowledges incoming message before it has been processed (while it should be done only after processing the message,

[openstack-dev] [mistral] Team meeting minutes

Thanks for joining the meeting today! Meeting minutes: *http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-09-07-16.00.html * Meeting log:

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

Hi, I also thought about that recently. So, I absolutely agree with this proposal. It would be nice to see this feature in Liberty. On Wed, Sep 2, 2015 at 2:17 PM, Renat Akhmerov wrote: > FYI > > Renat Akhmerov > @ Mirantis Inc. > > > > Begin forwarded message: > >

[openstack-dev] [pecan] [mistral] Pecan python3 compatibility

, something is wrong with HooksController and walk_controller method) Does pecan officially support python3 (especially, python3.4 or python3.5) or not? I didn't find any info about that in pecan repository. [1] http://paste.openstack.org/show/475041/ -- Best Regards, Nikolay Makhotkin @Mirantis

Re: [openstack-dev] [pecan] [mistral] Pecan python3 compatibility

> > > If value is a bounded method, you can replace value.im_class with > type(value.__self__). > > Yes. Python 3 does not support im_class attribute for methods. -- Best Regards, Nikolay __ OpenStack Development Mailing

[openstack-dev] [mistral] Cancelling team meeting today (09/28/2015)

Mistral Team, We’re cancelling today’s team meeting because a number of key members won’t be able to attend. The next one is scheduled for 5 Oct. Best Regards, Nikolay Makhotkin @Mirantis Inc. __ OpenStack Development

Re: [openstack-dev] [mistral] Define better terms for WAITING and DELAYED states

Thank you Robert for the explanation in details! >- RUNNING_DELAYED - a substate of RUNNING and it has exactly this >meaning: it’s generally running but delayed till some later time. >- WAITING - it is not a substate of RUNNING and hence it means a task >has not started yet > >

[openstack-dev] Mistral team meeting minutes - 12/07/2015

Hi, Thank you for coming us today! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-07-15.59.html Log: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-07-15.59.log.html Best Regards, Nikolay Makhotkin

[openstack-dev] [mistral] Mistral team meeting reminder

Hi, This is a reminder that we’ll have a team meeting today at #openstack- meeting at 16.00 UTC. Agenda: - Review action items - Current status (progress, issues, roadblocks, further plans) - M-2 status and planning - Open discussion -- Best Regards, Nikolay

[openstack-dev] [mistral] Mistral team meeting minutes 12/14/2015

Hi, Thank you guys to join us today! Meeting minutes - http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-14-16.01.html Meeting full log - http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-14-16.01.log.html Best Regards, Nikolay

Re: [openstack-dev] [mistal] Mistral logo ideas?

> > I like the idea of the logo being a stylized wind turbine. Perhaps it > could be > a turbine with a gust of wind. Then we can show that Mistral harnesses the > power of the wind :-) I like this idea! Combine Mistral functionality symbol with wind :) -- Best Regards, Nikolay

[openstack-dev] [OpenStack-Infra] [fuel-plugin-mistral] Request to add group member into the new Openstack project

Hi openstack-infra team, Kindly please add nmakhot...@mirantis.com to the following Gerrit ACL groups: https://review.openstack.org/#/admin/groups/1156,members https://review.openstack.org/#/admin/groups/1155,members (ref. https://review.openstack.org/#/c/238890/) -- Best Regards, Nikolay

[openstack-dev] [mistral] N. Makhotkin availability next 2 weeks

Hi team! I will be on vacation next 2 weeks right till 31 Jan. Please ping me via email if I am needed for reviewing some patches. -- Best Regards, Nikolay __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [mistral] Promoting Anastasia Kuznetsova to core reviewers

Hi, great work, Anastasia! +1 for you! On Fri, Jan 29, 2016 at 11:27 AM, Lingxian Kong wrote: > +1 from me, welcome Anastasia! > > On Fri, Jan 29, 2016 at 9:00 PM, Igor Marnat wrote: > >> Folks, >> I'm not a core reviewer, but if I was, I'd

[openstack-dev] [mistral] Mistral team meeting minutes

Thank you for attending the meeting today! Next meeting is scheduled on 22 Feb. It is non-working day in Russia so Renat, Anastasia and I very likely won't come to the meeting. Minutes: http://eavesdrop.openstack.org/meetings/mistral/2016/mistral.2016-02-15-16.00.html Log:

Re: [openstack-dev] [Mistral] Mistral with IPV6

Hi, Guy! I think there is the same issue as in ceilometerю Furthermore, Mistral and Ceilometer are using the same framework for constructing their Rest API. So, the fix probably should be the same. On Wed, Mar 9, 2016 at 4:15 PM, Paz, Guy (Nokia - IL) wrote: > > > Hello, > >

Re: [openstack-dev] [mistral] Promoting Hardik Parekh to core reviewers

Welcome to Mistral cores, Hardik Parekh! My vote is +1. On Tue, May 10, 2016 at 11:49 AM, Renat Akhmerov wrote: > I’d like to promote Hardik Parekh to Mistral core reviewers. > > He was #1 by number of commits and #3 by number of reviews in Mitaka cycle > and I think