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

rantis.com > <mailto:rakhme...@mirantis.com>] > Sent: Friday, August 14, 2015 11:51 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [mistral] [murano] An online YAQL evaluator > > I just read this thread so decided to a

[openstack-dev] [mistral] Team meeting minutes - 1/11/2016

Hi, Thank you for joining the meeting today. In case you’d like to see meeting minutes and log here they are: http://eavesdrop.openstack.org/meetings/mistral/2016/mistral.2016-01-11-16.00.html http://eavesdrop.

[openstack-dev] [mistral] Team meeting - 01/11/2016

Hi, We’ll have a team meeting today at our regular time 16.00 UTC at #openstack-meeting. Please join to discuss the project status. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Open discussion Renat Akhmerov @ Mirantis Inc. ___

[openstack-dev] [mistral] Cancelling team meeting today - 12/28/2015

Team, We’re cancelling the team meeting today since a number of key team members won’t be able to attend. Renat Akhmerov @ Mirantis Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openst

Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to match Mistral guidelines

gt;> >> >> *From:* Anastasia Kuznetsova [mailto:akuznets...@mirantis.com] >> *Sent:* Wednesday, December 09, 2015 1:13 PM >> *To:* OpenStack Development Mailing List (not for usage questions) >> *Subject:* Re: [openstack-dev] [mistral] Improving Mistral pep8 rules >>

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

n “Legacy Mode”. > > > > > > > > Hope you will find it useful. > > > > > > > > [1] http://yaqluator.com/ > > > > > > > > > > > > From: Renat Akhmerov [mailto:rakhme...@mirantis.com] > > Sent: Friday,

Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to match Mistral guidelines

kuznets...@mirantis.com>] > Sent: Wednesday, December 09, 2015 1:13 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to > match Mistral guidelines > > > > Hi Moshe, >

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

To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [mistral] [murano] An online YAQL evaluator > > > > I just read this thread so decided to add my 2 cents into the collection of > opinions. > > > > Guys, I tried it out a co

[openstack-dev] [mistral] [murano] [yaql] An online YAQL evaluator [was RE: [mistral] [murano] An online YAQL evaluator]

rantis.com] Sent: Friday, August 14, 2015 11:51 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral] [murano] An online YAQL evaluator I just read this thread so decided to add my 2 cents into the collection of opinions. Guys, I tried it out a

[openstack-dev] [mistral] Team meeting minutes - 12/21/2015

Thanks for joining our meeting today! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-12-21-16.00.html Meeting log:http://eavesdrop.openstack.org/meetings/mistral/2015/mistra

[openstack-dev] [mistral] Team meeting - 12/21/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) "Work queue" pattern in oslo.messaging (https://review.openstack.org/#/c/256342/

Re: [openstack-dev] [mistral] "Mistral HA and multi-regional support" meeting minutes

Moshe, thanks for sharing these meeting minutes. I am happy to help with gate and new functional tests (probably some destructive scenarios) which will help us to test Mistral HA. On Wed, Dec 16, 2015 at 8:01 PM, ELISHA, Moshe (Moshe) < moshe.eli...@alcatel-lucent.com> wrote: > Hi all, > > > > R

[openstack-dev] [mistral] "Mistral HA and multi-regional support" meeting minutes

Hi all, Renat and I had an action item to think about "Mistral HA and multi-regional support". No big surprises. These are the meeting minutes: Mistral Multi-Region: * A blueprint already exists [1] * Most topics were already discussed in Mitaka OpenStack summit and are described in the bluepri

[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 __

[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 __

Re: [openstack-dev] [mistral] bugfix for "Fix concurrency issues by using READ_COMMITTED" unveils / creates a different bug

Excerpts from ELISHA, Moshe (Moshe)'s message of 2015-12-07 08:29:44 -0800: > Hi all, > > The current bugfix I am working on[1] have unveiled / created a bug. > Test "WorkflowResumeTest.test_resume_different_task_states" sometimes fails > because "task4" is executed twice instead of once (See uni

Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to match Mistral guidelines

ed a blank line before it? > > > > Once the rules doc will be available I can work on adding these rules to > our pep8. > > > > > > *From:* Anastasia Kuznetsova [mailto:akuznets...@mirantis.com] > *Sent:* Wednesday, December 09, 2015 1:13 PM > *To:* OpenStack

Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to match Mistral guidelines

adding these rules to our pep8. From: Anastasia Kuznetsova [mailto:akuznets...@mirantis.com] Sent: Wednesday, December 09, 2015 1:13 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to match Mistral

Re: [openstack-dev] [mistral] bugfix for "Fix concurrency issues by using READ_COMMITTED" unveils / creates a different bug

List (not for usage questions) Subject: [openstack-dev] [mistral] bugfix for "Fix concurrency issues by using READ_COMMITTED" unveils / creates a different bug Hi all, The current bugfix I am working on[1] have unveiled / created a bug. Test “WorkflowResumeTest.test_resume_different_t

Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to match Mistral guidelines

Hi Moshe, Great idea! It is possible to prepare some additional code checks, for example you can take a look how it was done in Rally project [1]. Before starting such work in Mistral, I guess that we can describe our addition code style rules in our official docs (somewhere in "Developer Guide"

[openstack-dev] [mistral] Improving Mistral pep8 rules files to match Mistral guidelines

Hi all, Is it possible to add all / some of the special guidelines of Mistral (like blank line before return, period at end of comment, ...) to our pep8 rules file? This can save a lot of time for both committers and reviewers. Thanks! ___

[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] bugfix for "Fix concurrency issues by using READ_COMMITTED" unveils / creates a different bug

Hi all, The current bugfix I am working on[1] have unveiled / created a bug. Test "WorkflowResumeTest.test_resume_different_task_states" sometimes fails because "task4" is executed twice instead of once (See unit test output and workflow below). This happens because task2 on-complete is running

[openstack-dev] [mistral] Team meeting minutes - 11/30/2015

Thanks everyone for joining us! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-11-30-16.01.html Meeting log: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-11-30-16.01.log.html -- Best regards, Anastasia Kuznetsova __

[openstack-dev] [mistral] Team meeting minutes - 11/23/2015

Thanks everyone for very productive meeting! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-11-23-16.04.html Meeting log: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-11-23-16.04.log.html -- Best regards, Anastasia Kuznetsova _

[openstack-dev] [mistral] Team meeting - 11/23/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 backporting status Open discussion Renat Akhmerov @ Mirantis Inc.

Re: [openstack-dev] [mistral] Notifier about changes in the dsvm gates structure

Hi, Anastasia, First, thanks for writing down this, I can see that the way we do now may really make things unstable and hard to debug the Jenkins failures. I 100% agree with you about separating gate tests between Mistral repo and python-mistralclient repo, as a result, they won't interfere with

[openstack-dev] [mistral] Notifier about changes in the dsvm gates structure

Hello Everyone, This is a notifier about the fact that Mistral team is on the way of refactoring of current Jenkins dsvm gates infrastructure. The final goal is to have voting dsvm gates which will run on every commit to mistral and mistralclient repositories. What we have now: - mistral reposito

[openstack-dev] [mistral] Team meeting - 11/16/2015

Hi, This is just 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) Open discussion Put your own items at https://wiki.openstack.org/wiki/Meetings/MistralAgenda

[openstack-dev] [mistral] Team meeting minutes - 11/09/2015

Thanks for joining us today! Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-11-09-16.17.html Meeting log: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-1

[openstack-dev] [mistral] Team meeting - 11/09/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) Scoping Mitaka and Mitaka-1 Open discussion Feel free to add your topics at https://wiki.openstack.org/wiki/M

Re: [openstack-dev] [mistral] Planning and prioritizing session for Mitaka

Hi, Renat, thanks for bringing this, the time works for me as well. On Thu, Nov 5, 2015 at 3:23 PM, Renat Akhmerov wrote: > Team, > > We’ve done a great job at the summit discussing our most hot topics within > the project and a lot of important decisions were made. I would like to have > thoug

Re: [openstack-dev] [mistral] Planning and prioritizing session for Mitaka

Great. That works for ALU folks. -Original Message- From: Renat Akhmerov [mailto:rakhme...@mirantis.com] Sent: Thursday, November 05, 2015 9:23 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [mistral] Planning and prioritizing session for

[openstack-dev] [mistral] Planning and prioritizing session for Mitaka

Team, We’ve done a great job at the summit discussing our most hot topics within the project and a lot of important decisions were made. I would like to have though one more session in IRC to wrap up this by going over all the BPs/bugs we created in order to scope and prioritize them. I’m prop

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

Thanks for joining our team meeting today! In case you missed it or just want to catch up with Mistral activities here’s the meeting minutes and and full log. Minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-11-02-16.00.html

[openstack-dev] [mistral] Team meeting - 11/02/2015

Hi, I guest most people returned from the summit so I’d like to have a team meeting at our usual place and time: #openstack-meeting at 16.00 UTC Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Quickly highlight what we did at the summit Discuss major item

Re: [openstack-dev] [mistral] sort dir of executions, asc or desc?

Hi Lingxian, I am agree with you that from user's point of view it is more convenient to show execution in the descending order (latest created execution on the top), but all other get_all methods (for tasks, workflows, etc) return list of objects in the ascending order. I prefer to have consiste

[openstack-dev] [mistral] sort dir of executions, asc or desc?

Hi, guys, I found this bug[1] this morning which was fixed just now, and I have to say, it is my intention that to make the query executions result in descending order when I implemented the query pagination blueprint, which is different with workflows list result behavior. Because in user's persp

[openstack-dev] [mistral] Cancelling team meeting today - 10/26/2015

Team, We’re cancelling the meeting today due to the summit. I’ll see all of you who came to Tokyo very soon. Renat Akhmerov @ Mirantis Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: ope

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

Renat, Thanks for your valuable suggestions! Tony From: Renat Akhmerov [mailto:rakhme...@mirantis.com] Sent: Wednesday, October 21, 2015 2:35 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible

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

> On 19 Oct 2015, at 13:18, WANG, Ming Hao (Tony T) > wrote: > > I like your > option2(https://blueprints.launchpad.net/mistral/+spec/action-providers > ). J > Any schedule for this? Looks like it isn’t started yet. No particul

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

> On 20 Oct 2015, at 14:58, WANG, Ming Hao (Tony T) > wrote: > > Another question is: > If I use custom action to run Ansible, the Ansible playbook should be stored > on the same server of Mistral. Is it right? Depends on how this action is implemented (it can, for example, do ssh to other s

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

me server of Mistral. Is it right? > > > > Thanks, > > Tony > > > > From: Renat Akhmerov [mailto:rakhme...@mirantis.com] > Sent: Monday, October 19, 2015 2:58 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-d

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

t; > > From: Renat Akhmerov [mailto:rakhme...@mirantis.com] > Sent: Monday, October 19, 2015 2:58 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as > Ansible) in Mistral > > >

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

(not for usage questions) Subject: Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral On 19 Oct 2015, at 07:53, WANG, Ming Hao (Tony T) mailto:tony.a.w...@alcatel-lucent.com>> wrote: The “custom action” needs to re-install Mistral. If the Mistral serv

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

.action" is Mistral's custom action. Please help to double confirm. Thanks, Tony From: WANG, Ming Hao (Tony T) Sent: Monday, October 19, 2015 6:56 PM To: OpenStack Development Mailing List (not for usage questions) Subject: RE: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ans

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

> stderr: <% $.task1.stderr %> Thanks, Tony From: Dmitri Zimine [mailto:dzim...@stackstorm.com] Sent: Sunday, October 18, 2015 1:27 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral] How to call 3rd-party tools(such

[openstack-dev] [mistral] Cancelling team meeting today - 10/19/2015

Team, let’s cancel today’s meeting since we all have lots of pre-summit activities. Just in case if you still want to add your topics to discuss at the summit, here’s the link to the etherpad again: https://etherpad.openstack.org/p/mistral-tokyo-summit-2015

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

Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral On 19 Oct 2015, at 07:53, WANG, Ming Hao (Tony T) mailto:tony.a.w...@alcatel-lucent.com>> wrote: The “custom action” needs to re-install Mistr

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

> On 19 Oct 2015, at 07:53, WANG, Ming Hao (Tony T) > wrote: > > The “custom action” needs to re-install Mistral. > If the Mistral service is part of 3rd party OpenStack, it may be unacceptable > to let every user create his own customer action. What do you think? Yes, correct. It requires re

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

automation tools, such as Ansible. Is it right? Thanks, Tony From: Dmitri Zimine [mailto:dzim...@stackstorm.com] Sent: Sunday, October 18, 2015 1:27 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as

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

...@mirantis.com] Sent: Saturday, October 17, 2015 3:25 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral Hi, see my answers inline. On 16 Oct 2015, at 12:35, WANG, Ming Hao (Tony T

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

Tony, You can also connect Mistral with Ansible via StackStorm and Ansible integration pack: 1) StackStorm http://docs.stackstorm.com 2) https://github.com/StackStorm/st2contrib/tree/master/packs/ansible StackStorm is open-source Apache 2.0 “wrapper” around Mistral workflow service that integ

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

> On 16 Oct 2015, at 13:02, WANG, Ming Hao (Tony T) > wrote: > > Another question is: > If I want to call a user-defined script in Mistral, what action should be > used? > Still use “ssh std_action”? Yes, std.ssh action or std.ssh_proxied that allows to ssh through an VM with a floating ip

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

Hi, see my answers inline. > On 16 Oct 2015, at 12:35, WANG, Ming Hao (Tony T) > wrote: > > We have developed some Ansible playbooks for operation automation, and we are > investigating if we can change the automation engine from Ansible to Mistral > since Mistral has powerful workflow contro

[openstack-dev] [mistral][liberty][release] Mistral Liberty release (1.0.0) available

Hi, Mistral Official Liberty release versioned as 1.0.0 is now available. Look at the release page at Launchpad ([0]) to see release notes and detailed information about implemented blueprints and fixed bugs. There you can also download project tarballs (also published on pypi). Note that offi

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

nt Mailing List (not for usage questions) Subject: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral Dear Mistral developers and testers, We have developed some Ansible playbooks for operation automation, and we are investigating if we can change the automation e

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

Dear Mistral developers and testers, We have developed some Ansible playbooks for operation automation, and we are investigating if we can change the automation engine from Ansible to Mistral since Mistral has powerful workflow control. Could you please help to provide how to let Mistral call An

Re: [openstack-dev] [mistral] Team meeting minutes - 10/12/2015

Hi Lingxian, Yes, your understanding is correct. > * run_functional_tests.sh is just used locally, will not run tests depend on OpenStack. This script was written just for ability to run suite of api tempest tests locally (with turned off auth in Mistral and 'hacked' auth in tempest in our tests)

Re: [openstack-dev] [mistral] Team meeting minutes - 10/12/2015

Hi, Mistral guys, In last meeting, we have discussed deeply about Tempest usage in Mistral project and the functional testing mechanism, I have the understanding in terms of functional testing as below, * run_functional_tests.sh is just used locally, will not run tests depend on OpenStack. * in o

[openstack-dev] [mistral] Team meeting minutes - 10/12/2015

Hi, Thanks for joining team meeting today. Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-10-12-16.00.html Meeting log: http://eavesdrop.openstack.org/meetings/mistral/2015

[openstack-dev] [mistral] Team meeting - 10/12/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) Official Liberty Release health Bugfixing progress Documentation progress https://review.openstack.org/232507

Re: [openstack-dev] [mistral] [heat] Mistral Workflow resource type - resource signal handling

> On 08 Oct 2015, at 23:27, ELISHA, Moshe (Moshe) > wrote: > > Hi, > > I would like to propose a change in the behavior of the OS::Mistral::Workflow > resource signal. > > CURRENT: > The OS::Mistral::Workflow resource type is expecting the following request > body on resource signal reque

[openstack-dev] [mistral] [heat] Mistral Workflow resource type - resource signal handling

Hi, I would like to propose a change in the behavior of the OS::Mistral::Workflow resource signal. CURRENT: The OS::Mistral::Workflow resource type is expecting the following request body on resource signal request: { "input": { ... }, "params": { ... } } The input section is

[openstack-dev] [mistral] Team meeting - 10/05/2015

Hi, This is a reminder that we’ll hold a team meeting today at #openstack-meeting at 16.00 UTC. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) UI progress Official Liberty Release health Bugfixing progress Documentation progress Open discussion Feel fre

[openstack-dev] [mistral] stable/liberty branch is created

Team, We created stable/liberty branch for all Mistral subprojects based on RC1 release (and 1.1.0 version of client). All critically important fixes for official liberty release must be backported into this branch. Master is now open for developing new features. Renat Akhmerov @ Mirantis Inc.

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

Hi, guys, We will have a 7 days holiday in China, which is National Day, from Oct. 1 to Oct. 7. So, I'll miss the next team meeting :( On Mon, Sep 28, 2015 at 4:46 PM, Nikolay Makhotkin wrote: > Mistral Team, > > We’re cancelling today’s team meeting because a number of key members won’t > be ab

[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 Maili

[openstack-dev] [mistral] Mistral Liberty RC1 available

Hi, Mistral Liberty RC1 release is available. The exact version name is 1.0.0.0rc1. Look at the release page in order to see a list of bugs fixed during RC1 cycle: https://launchpad.net/mistral/liberty/liberty-rc1 Thanks! Renat Akhmerov @ Mi

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 > > Y

[openstack-dev] [mistral] Etherpad for Tokyo design summit topics

Hi, I created an etherpad where you can suggest summit topics for Mistral: https://etherpad.openstack.org/p/mistral-tokyo-summit-2015 Renat Akhmerov @ Mirantis Inc. _

[openstack-dev] [mistral] Cancelling team meeting - 09/21/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 28 Sep. Renat Akhmerov @ Mirantis Inc. __ OpenStack Development Mailing List (no

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

> On 18 Sep 2015, at 18:47, HADDLETON, Robert W (Bob) > wrote: > > Hi Renat: > > [TL;DR] - maybe use multiple words in the state name to avoid confusion > > I agree that there is a lot of overlap - WAITING and DELAYED and POSTPONED > are all very similar. The context is important when tryin

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

Hi Renat: [TL;DR] - maybe use multiple words in the state name to avoid confusion I agree that there is a lot of overlap - WAITING and DELAYED and POSTPONED are all very similar. The context is important when trying to decipher what the words means. I would normally interpret WAITING as hav

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

Hello, We have a bug [1] that addresses the small semantical issue in names of the states for workflow and task executions: WAITING and DELAYED. I’m really interested in your opinion about this. Especially native english speakers’ opinion because, IMO, they would be able to challenge better what

Re: [openstack-dev] [mistral][requirements] lockfile not in global requirements

On 09/18/2015 12:54 PM, Renat Akhmerov wrote: Thanks Andreas and Lingxian, Andreas, the corresponding patch has landed: https://review.openstack.org/#/c/225073/ Great, then syncing of requirements should be green again. thanks, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Id

Re: [openstack-dev] [mistral][requirements] lockfile not in global requirements

Thanks Andreas and Lingxian, Andreas, the corresponding patch has landed: https://review.openstack.org/#/c/225073/ Renat Akhmerov @ Mirantis Inc. > On 18 Sep 2015, at 12:08, Lingxian Kong wrote: > > Hi, Andreas, > > Sorry for the late response fr

Re: [openstack-dev] [mistral][requirements] lockfile not in global requirements

Hi, Andreas, Sorry for the late response from Mistral. Anyway, I'm coming :-) I'll take a look and solve it if needed, thanks for letting us know that. On Fri, Sep 18, 2015 at 2:22 AM, Andreas Jaeger wrote: > The syncing of requirements fails from the requirements repository to > mistral-extra

[openstack-dev] [mistral][requirements] lockfile not in global requirements

The syncing of requirements fails from the requirements repository to mistral-extra with 'lockfile' is not in global-requirements.txt Mistral team, could you either propose to add lockfile to the global requirements file - or remove it from your project, please? for details see: https://jenki

[openstack-dev] [Mistral] Mistral PTL Candidacy

Hi, My name is Renat Akhmerov. I decided to run for Mistral PTL for Mitaka release cycle. This is the first time when I’m doing it officially after Mistral was accepted into Big Tent. In fact, I’ve been driving the project for just a little less than 2 years by now and I've put a lot of my ene

[openstack-dev] [mistral] Team meeting minutes/log

Thanks for joining us for the meeting today. Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-09-14-16.00.html Meeting log: http://eavesdrop.openstack.org/meetings/mistral/201

[openstack-dev] [mistral] Team meeting - 09/14/2015

Hi Mistral team (and not only), This is a reminder that we’ll have a team meeting today at #openstack-meeting at 16.00 UTC. The agenda is: * Review action items * Current status (progress, issues, roadblocks, further plans) * Scoping RC releases * Open discussion Add your own items by editing

[openstack-dev] [Mistral] Mistral PTL Candidacy

Greetings, After contributing consistently to Mistral since the Kilo dev cycle, I'd like to run for the Mistral PTL position for the Mikata release cycle. In case you don't immediately recognize me, I'm 'xylan_kong' on IRC, where you can always find me. Although I know that I have served as Mistr

[openstack-dev] [mistral] Mistral Liberty-3 milestone has been released

Hi, Mistral Liberty 3 milestone has been released! We’ve also released Mistral Client 1.0.2 that has some adjustments needed to use the new Mistral server. Below are corresponding release pages where you can find downloadable artefacts and more detailed information about what has changed: https

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

questions) Subject: Re: [openstack-dev] [mistral][yaql] Addressing task result using YAQL function > On 07 Sep 2015, at 19:18, Stan Lagun wrote: > > I believe this is a good change. $.task_name requires you that $ be > pointing to a tasks dictionary. But in the middle of the query li

[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: *http://eavesdrop.openstack.org/meetings/mistral/2015/mistr

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

> On 07 Sep 2015, at 19:18, Stan Lagun wrote: > > I believe this is a good change. $.task_name requires you that $ be pointing > to a tasks dictionary. But in the middle of the query like [1.2.3].select($ + > 1) "$" will change its value. With a function approach > you can write [1, 2, 3].sel

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

I believe this is a good change. $.task_name requires you that $ be pointing to a tasks dictionary. But in the middle of the query like [1.2.3].select($ + 1) "$" will change its value. With a function approach you can write [1, 2, 3].select($ + task(taskName)). However the name "task" looks confus

[openstack-dev] [mistral] Team meeting - 09/07/2015

Hi, This is a reminder that we’ll have a team meeting today at #openstack-meeting IRC channel at 16.00 UTC. Agenda: * Review action items * Current status (progress, issues, roadblocks, further plans) * Wrapping up Liberty-3 * Open discussion Feel free to add your topics to https://wiki.openst

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

Yes meant to ask for consistency of referencing to task results. So it’s task(task_name) regardless of where. One use case in favor of this is tooling: I refactor workflow with an automated tool which wants to automatically rename the task name EVERYWHERE. You guys know well by now that renami

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

> On 02 Sep 2015, at 21:01, Dmitri Zimine wrote: > > Agree, > > with one detail: make it explicit - task(task_name). So do you suggest we just replace res() with task() and it looks like task() - get task result when we are in “publish” task(task_name) - get task result from anywhere ? I

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

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 ro

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

t; > *From: *Renat Akhmerov > *Subject: **[openstack-dev][mistral][yaql] Addressing task result using > YAQL function* > *Date: *2 Sep 2015 17:16:27 GMT+6 > *To: *"OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> >

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

Hi, I’d like to propose a few changes after transition to yaql 1.0: We already moved from using “$.__execution” in DSL to "execution()” and from “$.__env” to “env()” where “execution()” and “env()" are registered yaql functions. We had to do it because double underscored are prohibited in the n

Re: [openstack-dev] [mistral] Displaying wf hierarchy in CLI

> On 02 Sep 2015, at 14:56, Lingxian Kong wrote: > > I want to make it clear. Then, what you want to see is dependencies between > workflow executions? or task executions in one workflow? We know that we > could use a separate task or a workflow as a 'task'. Dependencies between workflow exec

Re: [openstack-dev] [mistral] Displaying wf hierarchy in CLI

Hi, Renat, I want to make it clear. Then, what you want to see is dependencies between workflow executions? or task executions in one workflow? We know that we could use a separate task or a workflow as a 'task'. On Wed, Sep 2, 2015 at 3:33 PM, Renat Akhmerov wrote: > > On 01 Sep 2015, at 22:21

Re: [openstack-dev] [mistral] Displaying wf hierarchy in CLI

> On 01 Sep 2015, at 22:21, Lingxian Kong wrote: > > To achieve that, we should record the execution/task-execution relationship > during an execution is running, because we have no such info currently. Well, in DB model we, in fact, have a field pointing to parent task execution id (and henc

Re: [openstack-dev] [mistral] Displaying wf hierarchy in CLI

> On 31 Aug 2015, at 23:47, Joshua Harlow wrote: > > Would u guys have any use for the following being split out into its own > library? > > https://github.com/openstack/taskflow/blob/master/taskflow/types/tree.py Do you mean we could move this, for instance, into oslo somewhere? Taskflow it

Re: [openstack-dev] [mistral] Displaying wf hierarchy in CLI

Hi, Renat, Actually, I have the same idea months ago, but what I thought is to provide task dependencies information in a workflow definition, since as a workflow designer, I have no idea about how my workflow 'looks like', unless I create an execution with that, especially when there are a lot of

Re: [openstack-dev] [mistral] Displaying wf hierarchy in CLI

Would u guys have any use for the following being split out into its own library? https://github.com/openstack/taskflow/blob/master/taskflow/types/tree.py It already has a pformat method that could be used to do your drawing of the 'tree'... http://docs.openstack.org/developer/taskflow/types

<    1   2   3   4   5   6   7   8   9   10   >