believe it should have warranted a major version bump.
Agree with that. But thanks for letting us know. We’ll have to deal with that.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage
Ok, thanks. We’ll fix it in Mistral accordingly.
Renat Akhmerov
@ Mirantis Inc.
On 26 Aug 2015, at 15:12, Dmitry Tantsur dtant...@redhat.com wrote:
On 08/26/2015 11:05 AM, Lucas Alvares Gomes wrote:
On Wed, Aug 26, 2015 at 9:27 AM, Chris Dent chd...@redhat.com wrote:
On Wed, 26 Aug 2015
On 24 Aug 2015, at 20:17, Doug Hellmann d...@doughellmann.com wrote:
My point is the following: we’re not getting rid of oslo.messaging for
several reasons (community standard,
its developers have better vision and expertise at messaging etc.). In any
case we’ll have oslo.messaging as one
://wiki.openstack.org/wiki/Meetings/MistralAgenda
https://wiki.openstack.org/wiki/Meetings/MistralAgenda or replying to this
email.
Thanks
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions
(Resending the email that I sent last week but it doesn’t seem to have been
sent out actually…)
On 19 Aug 2015, at 21:44, Doug Hellmann d...@doughellmann.com
mailto:d...@doughellmann.com wrote:
Excerpts from Nikolay Makhotkin's message of 2015-08-19 17:16:14 +0300:
Hi, Davanum!
Have
Yes, I fully support this. Let’s do this.
Renat Akhmerov
@ Mirantis Inc.
On 13 Aug 2015, at 17:44, ELISHA, Moshe (Moshe)
moshe.eli...@alcatel-lucent.com wrote:
Hey,
Following our discussion in the IRC, when pushing UI changes please upload a
screenshot of the result and add a link
or by modifying
https://wiki.openstack.org/wiki/Meetings/MistralAgenda
https://wiki.openstack.org/wiki/Meetings/MistralAgenda.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions
/mistral.2015-08-17-16.02.log.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-08-17-16.02.log.html
The next meeting will be on Aug 24 at the same time. See you soon.
Renat Akhmerov
@ Mirantis Inc
users it will be very
handy tool. I am actually for improving it further.
Thanks a lot! Looking forward to switch to yaql 1.0!
Renat Akhmerov
@ Mirantis Inc.
On 05 Aug 2015, at 04:09, Stan Lagun sla...@mirantis.com wrote:
Dmitry,
yaql 1.0 has both str() and len() and much much more so
Hi,
Mistral Liberty-2 development milestone has been released.
Look at release page [1] to find detailed info about implemented blueprints and
fixed bugs.
[1] https://launchpad.net/mistral/liberty/liberty-2
https://launchpad.net/mistral/liberty/liberty-2
Thanks!
Renat Akhmerov
@ Mirantis
Hi,
Mistral Client (Python API and CLI) version 1.0.1 has been released. It
contains changes needed for Python 3.4 compatibility and a number of bug fixes.
[1] https://launchpad.net/python-mistralclient/liberty/1.0.1
https://launchpad.net/python-mistralclient/liberty/1.0.1
Thanks
Renat
Hi,
I’m ok with this time.
Renat Akhmerov
@ Mirantis Inc.
On 11 Aug 2015, at 16:27, Anastasia Kuznetsova akuznets...@mirantis.com
wrote:
Hello all,
Happy to announce that Mistral team is planning to provide L-3 roadmap
discussion meeting on Wednesday ( Aug 12 ).
Meeting
Limor,
No objections from my side. Just follow regular OpenStack procedures to do it.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 15 Jul 2015, at 14:19, BORTMAN, Limor (Limor)
limor.bort...@alcatel-lucent.com wrote:
Hi all,
I have puppet for mistral and i would like to contribute
be
related though but who knows..
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
be transformed.
Renat Akhmerov
@ Mirantis Inc.
On 14 Jul 2015, at 23:42, ELISHA, Moshe (Moshe)
moshe.eli...@alcatel-lucent.com wrote:
Hey,
I have created a new BP “Support large datasets being passed” [1].
You comments / suggestion / approval are most welcome.
[1] - https
or modifying
https://wiki.openstack.org/wiki/Meetings/MistralAgenda
https://wiki.openstack.org/wiki/Meetings/MistralAgenda.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions
/Meetings/MistralAgenda
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
to get input from someone else working in Horizon team.
Zhenguo, thanks for bringing this up.
Renat Akhmerov
@ Mirantis Inc.
On 07 Jul 2015, at 13:16, niuzhenguo niuzhen...@huawei.com wrote:
Hi folks,
As Horizon is moving towards an Angular application, I think it’s high time
that we
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo
://www.rabbitmq.com/tutorials/tutorial-two-python.html
Renat Akhmerov
@ Mirantis Inc.
On 07 Jul 2015, at 15:58, Nikolay Makhotkin nmakhot...@mirantis.com wrote:
Hi,
I am using RabbitMQ as the backend and searched oslo.messaging for message
acknowledgement feature but I found only [1] what is wrong
or modifying
https://wiki.openstack.org/wiki/Meetings/MistralAgenda
https://wiki.openstack.org/wiki/Meetings/MistralAgenda.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions
[2] https://etherpad.openstack.org/p/mistral-explicit-task-parameters
https://etherpad.openstack.org/p/mistral-explicit-task-parameters
Please take a look at leave your comments/questions.
Thanks
Renat Akhmerov
@ Mirantis Inc
/MistralAgenda.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
modules and classes and then we
may want to have a script to launch it separately if needed. Or it can start
automatically say within an engine instance.
Anyway, let’s not run ahead of train and gather what we need to do first.
Renat Akhmerov
@ Mirantis Inc
Renat Akhmerov
@ Mirantis Inc.
On 02 Jul 2015, at 13:37, ELISHA, Moshe (Moshe)
moshe.eli...@alcatel-lucent.com wrote:
Hey,
We are planning to use Mistral in production in the next few months.
We noticed that having even a simple workflow with a cron-trigger (For
example monitor
.
Renat Akhmerov
@ Mirantis Inc.
On 26 Jun 2015, at 17:25, Renat Akhmerov rakhme...@mirantis.com wrote:
Hi all,
Liberty 1 milestone for Mistral server and Mistral client 0.3.0 have been
released!
Visit corresponding release pages to see information on fixed bugs and
implemented
topics (either by replying to this email or
modifying https://wiki.openstack.org/wiki/Meetings/MistralAgenda
https://wiki.openstack.org/wiki/Meetings/MistralAgenda).
Thanks
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack
://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-06-29-16.00.log.html
The next meeting will be on July 7 at the same time.
Looking forward to see you all again.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development
://launchpad.net/python-mistralclient
https://launchpad.net/python-mistralclient
Thanks to Mistral team!
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev
Yes, 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 dzim...@stackstorm.com wrote:
Folks,
it’s been some time,what’s the news:
* Is Murano moving YAQL
Can you please confirm that the issue has been fixed?
The thing is AFAIK Solum was using the old version of Mistral API that is no
longer supported (was announced a couple of months ago) so I just want to make
sure you’re using the new API.
Renat Akhmerov
@ Mirantis Inc.
On 18 Jun 2015
Alright, I see no objections. Then my congratulations Lingxian!
Done.
Renat Akhmerov
@ Mirantis Inc.
On 23 Jun 2015, at 11:51, BORTMAN, Limor (Limor)
limor.bort...@alcatel-lucent.com wrote:
+1
From: W Chan [mailto:m4d.co...@gmail.com]
Sent: Tuesday, June 23, 2015 12:07 AM
energy is
desire to be active is really hard to ignore :)
I’d like to ask you to support me in this proposal.
Thanks
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions
/Meetings/MistralAgenda.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
to this
email.
Thanks
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman
Thanks Doug, got it.
Limor, can you please explain why exactly do you need this library?
Renat Akhmerov
@ Mirantis Inc.
On 02 Jun 2015, at 18:45, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Renat Akhmerov's message of 2015-06-02 18:26:40 +0600:
Any comments from TC
Any comments from TC on that? What is the typical procedure of accepting new
libs into global requirements?
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 02 Jun 2015, at 18:11, BORTMAN, Limor (Limor)
limor.bort...@alcatel-lucent.com wrote:
Hi all,
As part as a BP in mistral (Add seconds
/Meetings/MistralAgenda#Agenda.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi
for Liberty with a wider audience.
Thanks
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http
.
Renat Akhmerov
@ Mirantis Inc.
On 13 May 2015, at 23:17, Nikolay Makhotkin nmakhot...@mirantis.com wrote:
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
with the weird accent ;)
With the great pleasure.
(P.S. your accent is cool!)
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
-mistral
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo
all companies for their active and
insightful participation!
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
implementation
detail?
More precisely: implementation detail of Mistral action which may not be even
hardcoded part of Mistral, we can rather plug them in (using stevedore
underneath).
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack
Team,
We decided to cancel today’s meeting because a number of key members won’t be
able to attend.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
correctly now:
https://github.com/stackforge/mistral/blob/master/mistral/engine/policies.py#L295-L296
https://github.com/stackforge/mistral/blob/master/mistral/engine/policies.py#L295-L296
Yes, you’re right. It seems like it works now as I described.
Renat Akhmerov
@ Mirantis Inc
for this is to “stop waiting for something if we
see that fundamental requirements for that are not met”.
Thoughts?
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
Lingxian, yes, that’s basically what I suggest too.
Renat Akhmerov
@ Mirantis Inc.
On 22 Apr 2015, at 16:03, Lingxian Kong anlin.k...@gmail.com wrote:
Hi all,
In my understanding, the meaning of the 'break-on' in 'retry' policy
is just give an oppotunity to end the task execution
Client: https://launchpad.net/python-mistralclient/kilo/kilo-rc1
https://launchpad.net/python-mistralclient/kilo/kilo-rc1
Thanks
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions
/Meetings/MistralAgenda
https://wiki.openstack.org/wiki/Meetings/MistralAgenda
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
-16.22.log.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-04-20-16.22.log.html
The next meeting is scheduled for Apr 27 (same place and time).
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack
Ok, the main problem is that we won’t be able to use Kilo releases of Murano
and Mistral in the same environment which doesn’t make me happy. Hm… Ok. So
looks like we’ll have to switch back to old YAQL till Liberty (which is very
soon).
Renat Akhmerov
@ Mirantis Inc.
On 14 Apr 2015
/2015/mistral.2015-04-13-16.20.log.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-04-13-16.20.log.html
The next meeting will be held on Apr 20, same place and time.
Renat Akhmerov
@ Mirantis Inc
Hi,
This is a reminder about our team meeting today at 16.20 UTC at
#openstack-meeting.
Agenda:
Review AIs
Current Status
RC1 progress
Open Discussion
Thanks
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development
Congratulations Winson! You’re now a core member of Mistral. Welcome )
Cheers
Renat Akhmerov
@ Mirantis Inc.
On 07 Apr 2015, at 19:28, Anastasia Kuznetsova akuznets...@mirantis.com
wrote:
Hello all,
As a QA Engineer of Mistral, I also appreciate Winson's contribution to the
project
Well, we’ve been ready to switch to YAQL-1.0 for a couple of months. We
researched it, figured out how our integration would change etc. It’s pretty
easy to do from our side. So let’s wait for the official YAQL-1.0.X release on
pypi.
Renat Akhmerov
@ Mirantis Inc.
On 07 Apr 2015, at 00:56
!
Renat Akhmerov
@ Mirantis Inc.
On 07 Apr 2015, at 03:04, Dmitri Zimine dzim...@stackstorm.com wrote:
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
Ok, sounds good! So if there aren’t any objections we can start doing it asap.
Renat Akhmerov
@ Mirantis Inc.
On 07 Apr 2015, at 16:00, Serg Melikyan smelik...@mirantis.com wrote:
Hi Renat Dmitry
Today we released YAQL 1.0.0b2 and release is available on PyPI, I
think it's better
Hi,
This is a reminder that we’ll hold our weekly team meeting today at 16.20 UTC
at #openstack-meeting.
Agenda:
* Review AIs
* Current status
* Discussing RC1 progress
* Open discussion
Thanks
Renat Akhmerov
@ Mirantis Inc
://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-04-06-16.20.log.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-04-06-16.20.log.html
Thanks again and join us in one week on April 13 at the same time.
Renat Akhmerov
@ Mirantis Inc
be implemented.
This is just my preference to see something like this but at the same time I
personally don’t want you to spend much time on that but if it’s possible to
prepare it within a reasonable amount of time that would be helpful
Thanks
Renat Akhmerov
@ Mirantis Inc
/mistral.2015-03-30-16.23.log.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-03-30-16.23.log.html
The next meeting is scheduled for April 6 at 16.20 UTC (temporarily new time)
Renat Akhmerov
@ Mirantis Inc
you’ve done!
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin
We’re cancelling today’s meeting since some key members won’t present.
Thanks
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
Hi,
This is a reminder about weekly team meeting that we’ll have today. Please note
that today (and possibly next several times) we’ll start at 16.20 UTC instead
of 16.00 UTC due to schedule issues within the team.
Agenda:
Kilo-3 progress
Engine refactoring
Next plans
Renat Akhmerov
Thank you so much! I’m excited and looking forward to play with it )
How about moving (or copying) this code into one of our official repos?
“mistral-extra” seems to be the right place since from the very beginning it
was intended to be used for various tools and examples.
Renat Akhmerov
for “success-on” may be, for example,
checking a completion of another parallel task and if it’s completed then we
can treat our task successful meaning that we already got what’s required. I
know it sounds a little bit generic but still pointful for me.
Renat Akhmerov
@ Mirantis Inc.
On 03 Mar
Oooh, ok! Yeah, additional tests for that would help us clearly see that solved.
Thanks!
Renat Akhmerov
@ Mirantis Inc.
On 03 Mar 2015, at 18:03, Peter Razumovsky prazumov...@mirantis.com wrote:
Hi Renat,
We solved problem with referencing. I'll add more tests for understanding,
how
references accounting for stack name etc.. Or we need to provide
some facility in Mistral itself.
Other than that it looks to be ready to start gathering Heat folks’ feedback.
Renat Akhmerov
@ Mirantis Inc.
On 26 Feb 2015, at 17:49, Peter Razumovsky prazumov...@mirantis.com wrote
/mistral.2015-03-02-16.00.log.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-03-02-16.00.log.html
We may change our team meeting time so we’ll notify about that separately.
Renat Akhmerov
@ Mirantis Inc
Sorry for the late notice. We’re cancelling our team meeting today. Several
team members are on official holidays.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions
://wiki.openstack.org/wiki/Keystone/Trusts
https://wiki.openstack.org/wiki/Keystone/Trusts but it would be nice if
something more tutorial-like existed.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage
] https://etherpad.openstack.org/p/mistral-YAQL-delimiters
https://etherpad.openstack.org/p/mistral-YAQL-delimiters
Renat Akhmerov
@ Mirantis Inc.
On 18 Feb 2015, at 07:37, Patrick Hoolboom patr...@stackstorm.com wrote:
My main concern with the {} delimiters in YAQL is that the curly brace
using their fully
qualified names. To do that you can use regular well known python procedures
(setuptools etc.)
Hope this helps
Renat Akhmerov
@ Mirantis Inc.
On 18 Feb 2015, at 14:55, Filip Blaha filip.bl...@hp.com wrote:
Thanks for answer!
A custom action inherits from base.Action
? If yes then how exactly they must be understood?
Thanks!
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
ready to be beaten by stones! Fire away :)
Renat Akhmerov
@ Mirantis Inc.
On 19 Feb 2015, at 11:25, James Fryman ja...@stackstorm.com wrote:
On Feb 18, 2015, at 3:07 PM, Dmitri Zimine dzim...@stackstorm.com
mailto:dzim...@stackstorm.com wrote:
Syntax options that we’d like to discuss
Renat Akhmerov
@ Mirantis Inc.
On 17 Feb 2015, at 13:37, Renat Akhmerov rakhme...@mirantis.com wrote:
Along with % % syntax here are some other alternatives that I checked for
YAML friendliness with my short comments:
p1: ${1 + $.var} # Here it’s bad that $ sign is used for two
Steve, I saw a couple of things in what you wrote that we might be doing wrong.
We’ll check them when we wake up and let you know what we discovered.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 16 Feb 2015, at 21:47, Steven Hardy sha...@redhat.com wrote:
On Mon, Feb 16, 2015 at 09:02:01PM
and
easy mechanism to plug in other expression languages, “yaql” here is a used
dialect for the following expression
p8: y{1 + $.var}# “y” here is just shortened “yaql
Any ideas and thoughts would be really appreciated!
Renat Akhmerov
@ Mirantis Inc.
On 17 Feb 2015, at 12:53, Renat
friendly.
I would be good if we could here more feedback on this, especially from people
who started using Mistral.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 17 Feb 2015, at 03:06, Dmitri Zimine dzim...@stackstorm.com wrote:
SUMMARY:
We are changing the syntax for inlining
the correct usage?)
Trust mechanism itself is in development and can’t be used at this point.
OpenStack clients need to be changed in some way to somehow bypass this
keystone limitation?
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 16 Feb 2015, at 19:10, Nikolay Makhotkin nmakhot...@mirantis.com wrote
of the previously saved environment, but
environments are not officially announced yet).
* $.openstack which contains whatever is listed in the doc (project_id etc.)
This part is slightly changing now and there isn’t still a final doc on that.
It will be created by the end of kilo-3.
Thanks
Renat Akhmerov
/2015/mistral.2015-02-09-16.00.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-02-09-16.00.html
The next one will be on Feb 16.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List
Hi,
It’s pretty simple and described in
http://mistral.readthedocs.org/en/master/developer/writing_a_plugin_action.html
http://mistral.readthedocs.org/en/master/developer/writing_a_plugin_action.html.
Renat Akhmerov
@ Mirantis Inc.
On 09 Feb 2015, at 21:43, Filip Blaha filip.bl...@hp.com
There you can find a list of implemented blueprints and fixed bugs as well as
the links to downloadable files.
Thanks
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe
/mistral.2015-02-02-16.00.log.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-02-02-16.00.log.html
The next meeting is scheduled on Feb 09
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development
.2015-01-19-16.00.log.html
http://eavesdrop.openstack.org/meetings/mistral/2015/mistral.2015-01-19-16.00.log.html
The next meeting is scheduled on Jan 26.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing
Hi,
We decided to cancel today’s team meeting because some key members of the team
won’t be present.
The next on will be held on Jan 19.
Renat Akhmerov
@ Mirantis Inc.
__
OpenStack Development Mailing List
Hi,
Let’s cancel the meeting today and on the next week. I think they won’t gather
enough people because of the New Year holidays.
Thanks
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
.
Agree. How about using double underscore for env as well (i.e. $.__env.var1,
$.__env.var2)?
Yes.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
”.
3) Can user has a few environments?
Yes. That’s one of the goals of introducing a concept of environment. So that
same workflows could be running in different environments (e.g with different
email settings, any kinds of passports etc.).
Renat Akhmerov
@ Mirantis Inc
)
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.
The nested dict for __actions (and all other keys with double underscore)
is special system purpose, in this case declaring defaults for action inputs.
Similar to __execution where it's for containing runtime data for the WF
execution.
Yes, that’s clear
Renat Akhmerov
@ Mirantis Inc
Thanks Boris!
Renat Akhmerov
@ Mirantis Inc.
On 24 Dec 2014, at 23:54, Boris Pavlovic bpavlo...@mirantis.com wrote:
Guys,
I added patch to infra:
https://review.openstack.org/#/c/143879/
https://review.openstack.org/#/c/143879/
That allows to run Rally against Mistral in gates
Thanks Clint,
I actually didn’t see this before (like I said just rumors) so need to read it
carefully.
Renat Akhmerov
@ Mirantis Inc.
On 25 Dec 2014, at 00:18, Clint Byrum cl...@fewbar.com wrote:
Excerpts from Renat Akhmerov's message of 2014-12-24 03:40:22 -0800:
Hi
Ok, I'm quite
, all additional comments and questions are more than welcomed!
Renat Akhmerov
@ Mirantis Inc.
On 24 Dec 2014, at 04:32, W Chan m4d.co...@gmail.com wrote:
After some online discussions with Renat, the following is a revision of the
proposal to address the following related blueprints
/wiki/Meetings/MistralAgenda
https://wiki.openstack.org/wiki/Meetings/MistralAgenda to find the agenda and
the meeting archive)
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi
at least one major version of DSL. If we gather enough
feedback that some of the things need to be changed in a non-backwards
compatible way then we will probably create v3. Otherwise, why do we need
versioning at all?
Renat Akhmerov
@ Mirantis Inc
to a great
extent.
Thanks
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
301 - 400 of 652 matches
Mail list logo
