a decision to follow all the release procedures adopted for
official OpenStack projects to simplify future incubation and integration and
from now on all terms, principles and versioning will be corresponding.
Renat Akhmerov
@ Mirantis Inc
Yeah,
We had a very productive discussion with Winson today and he’s going to prepare
more formal specification on what he’s suggesting. I’d like to say in advance
though that I really really like it in terms of what it will allow to do.
Renat Akhmerov
@ Mirantis Inc.
On 19 Dec 2014, at 17
Ok, Doug, we’ll look into it.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 18 Dec 2014, at 22:59, Doug Hellmann d...@doughellmann.com wrote:
On Dec 18, 2014, at 2:53 AM, Renat Akhmerov rakhme...@mirantis.com
mailto:rakhme...@mirantis.com wrote:
Doug,
Sorry for trying to resurrect
(and not only to me). Please share
the details.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 17 Dec 2014, at 13:22, W Chan m4d.co...@gmail.com wrote:
Renat,
We want to introduce the concept of an ActionProvider to Mistral. We are
thinking that with an ActionProvider, a third party system can
Dmitri,
Yes, it would be really cool if you could with the documentation. Btw, while
doing it you could also think recommendations for others tests that should be
added to make sure they provide enough coverage for needed case.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 17 Dec 2014, at 15
Doug,
Sorry for trying to resurrect this thread again. It seems to be pretty
important for us. Do you have some comments on that? Or if you need more
context please also let us know.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 27 Nov 2014, at 17:43, Renat Akhmerov rakhme...@mirantis.com
://review.openstack.org/#/c/142452/. Took fairly reasonable amount of
time for Nikolay to fix it.
Option 1 introduce a new syntax; although familiar to CLI users, I think it’s
a bit out of place in YAML definition.
Yes, agree.
Option 4 is no go :)
Out of discussion.
Renat Akhmerov
@ Mirantis Inc
.
Thanks
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
https://wiki.openstack.org/wiki/Meetings/MistralAgenda
https://wiki.openstack.org/wiki/Meetings/MistralAgenda to the same agenda and
the meeting archive).
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
/mistral.2014-12-15-16.01.log.html
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-12-15-16.01.log.html
The next meeting is on Dec 22 at the same time.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev
after all iterations and be able to access an array of iteration results
as $. But technically, it may be a problem to implement such behavior, need to
think about it more.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev
Maybe put all these different context under a kwarg called context?
For example,
ctx = {
env: {...},
global: {...},
runtime: {
execution_id: ...,
task_id: ...,
...
}
}
action = SomeMistralAction(context=ctx)
IMO, that is a nice idea. I
.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 10 Dec 2014, at 00:17, Nikolay Makhotkin nmakhot...@mirantis.com wrote:
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
/mistral/+spec/mistral-default-input-values
https://blueprints.launchpad.net/mistral/+spec/mistral-default-input-values
Renat Akhmerov
@ Mirantis Inc.
On 10 Dec 2014, at 13:12, W Chan m4d.co...@gmail.com wrote:
Nikolay,
Regarding whether the execution environment BP is the same
to be able to alter behavior.
One more thing: Now only will Heat be able to call Mistral somewhere underneath
the surface. Mistral has already integration with Heat to be able to call it if
needed and there’s a plan to make it even more useful and usable.
Thanks
Renat Akhmerov
@ Mirantis Inc
No problem, let us know if you have any other questions.
Renat Akhmerov
@ Mirantis Inc.
On 09 Dec 2014, at 11:57, Sushma Korati sushma_kor...@persistent.com wrote:
Hi,
Thank you guys.
Yes I am able to do this with heat, but I faced issues while trying the same
with mistral
Ok, got it.
So my general suggestion here is: let's keep it as simple as possible for now,
create something that works and then let’s see how to improve it. And yes,
consumers may be and mostly will be 3rd parties.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 09 Dec 2014, at 08:25, W Chan
Hi Winson,
I think it makes perfect sense. The reason I think is mostly historical and
this can be reviewed now. Can you pls file a BP and describe your suggested
design on that? I mean how we need to alter interface Action etc.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 09 Dec 2014, at 13
Hundred percent agree with all said by Zane.
Renat Akhmerov
@ Mirantis Inc.
On 10 Dec 2014, at 02:20, Zane Bitter zbit...@redhat.com wrote:
On 09/12/14 03:48, Renat Akhmerov wrote:
Hey,
I think it’s a question of what the final goal is. For just creating
security groups as a resource
] https://wiki.openstack.org/wiki/Meetings/MistralAgenda
https://wiki.openstack.org/wiki/Meetings/MistralAgenda
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
/mistral.2014-12-01-16.00.log.html
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-12-01-16.00.log.html
The next meeting is scheduled for Dec 8 at the same time.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack
should use same executors to process these
notifications or introduce a new type of entity for that?
Thanks
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
Doug, thanks for your answer!
My explanations below..
On 26 Nov 2014, at 21:18, Doug Hellmann d...@doughellmann.com wrote:
On Nov 26, 2014, at 3:49 AM, Renat Akhmerov rakhme...@mirantis.com
mailto:rakhme...@mirantis.com wrote:
Hi,
I traced the WSME code and found a place [0
or
if we can just fix it.
If you need help with contribution let us know pls.
Thanks
[0] https://github.com/stackforge/wsme/blob/master/wsme/rest/args.py#L215
https://github.com/stackforge/wsme/blob/master/wsme/rest/args.py#L215
Renat Akhmerov
@ Mirantis Inc.
On 25 Nov 2014, at 23:06
hesitate
reaching us out in IRC (#openstack-mistral) or email.
Thanks!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
https://wiki.openstack.org/wiki/Meetings/MistralAgenda as well as the meeting
archive)
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-11-17-16.00.log.html
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-11-17-16.00.log.html
The next meeting will be next Monday Nov 24 at 16.00 UTC.
Renat Akhmerov
@ Mirantis Inc
’ that don’t have to be distributed across executors. The
reason is the same: distribution overhead is much higher than just running them
right in the engine process. So I would like to know what you think here.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 12 Nov 2014, at 22:21, W Chan m4d.co
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-mistral
https://etherpad.openstack.org/p/paris-2014-design-summit-mistral
Thanks!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/wiki/Mistral/DSLv2
https://wiki.openstack.org/wiki/Mistral/DSLv2
Would be nice to talk to you personally if you’re going to the summit or using
any other channel and discuss the details )
Renat Akhmerov
@ Mirantis Inc.
On 31 Oct 2014, at 02:22, Raanan Jossefi (RJ) Benikar rbeni...@gmail.com
Folks, we are canceling today's team meeting since several key members won't be
able to join.
Sent from Renat's iPad
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-mistralclient/juno/0.1.1
Thanks!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
http://www.youtube.com/watch?v=9kaac_AfNow
MIstral 0.1, part 2: http://www.youtube.com/watch?v=u6ki_DIpsg0
http://www.youtube.com/watch?v=u6ki_DIpsg0
More screencasts coming soon...
Thanks
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
/2014/mistral.2014-10-20-16.02.log.html
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-10-20-16.02.log.html
The next meeting will be on Oct 27 at the same time.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack
Yes, I already reviewed your commits. Thanks.
Renat Akhmerov
@ Mirantis Inc.
On 07 Oct 2014, at 15:06, Dmitri Zimine dzim...@stackstorm.com wrote:
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/README.md
Ok, Timur, thanks. Will check it out by the end of this week.
Renat Akhmerov
@ Mirantis Inc.
On 06 Oct 2014, at 20:16, Timur Sufiev tsuf...@mirantis.com wrote:
Renat,
I've addressed a number of Mistral Workbook builder's issues, including:
* separating workflow-based Tasks from action
Yes,
Currently available resources seem to allow this )
Renat Akhmerov
@ Mirantis Inc.
On 03 Oct 2014, at 12:30, Dmitri Zimine dzim...@stackstorm.com wrote:
Thanks Renat for running and capturing.
One addition - allocate time for bug fixes, we’ll have quite a few :)
DZ.
On Oct 2
Please join the discussion if you have something to add/comment or if you’d
like to contribute to Mistral 0.2.
Thanks
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
Yes, Dmitri, thank you for your comments. We basically came to the same
conclusion. For now DB is not going to be involved and it will be possible to
fill ‘targets’ from workflow input using YAQL expressions to be able to assign
tasks to executors dynamically.
Renat Akhmerov
@ Mirantis Inc
Timur,
For us, undoubtedly, it’s a great news. Visualization of any kind is really
important for Mistral for a number of reasons. You can count on any
help(including code contribution) from our side.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 26 Sep 2014, at 04:04, Steve Baker sba
.
* Blueprints: https://blueprints.launchpad.net/mistral
* Roadmap: https://wiki.openstack.org/wiki/Mistral/Roadmap
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman
Well, event types are supposed to be different depending on what we want.. I
just like the idea of using actions because corresponds to spirit of Mistral :)
Btw, zaqar can be easily supported in a form of action (again, to be consistent
with what we do in the system).
Renat Akhmerov
@ Mirantis
” but not sure if we
need to get that far for now.
Thoughts?
[0] https://blueprints.launchpad.net/mistral/+spec/mistral-event-listeners-amqp
[1] https://blueprints.launchpad.net/mistral/+spec/mistral-event-listeners-http
Renat Akhmerov
@ Mirantis Inc.
On 17 Sep 2014, at 10:36, Dmitri Zimine
://wiki.openstack.org/wiki/Meetings/MistralAgenda
The next meeting will be at the same time/place on Sep 15.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
at https://wiki.openstack.org/wiki/Meetings/MistralAgenda#Agenda as
well as meeting archive)
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
as well
as the meeting archive)
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/MistralAgenda
The next meeting will be on Sep 8th.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Yes, it’s just a regular task that sends a request. Something like:
notify_about_completion:
action: std.http
parameters:
url: whatever_we_need.org
method: GET
You can also take a look at webhooks examples in mistral-extra.
Renat Akhmerov
@ Mirantis Inc.
On 29 Aug 2014, at 01:22
to it.
Inviting everyone to discussion.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 28 Aug 2014, at 06:17, W Chan m4d.co...@gmail.com wrote:
Renat,
It will be helpful to perform a callback on completion of the async workflow.
Can we add on-finish to the workflow spec and when workflow completes
Right now, you can just include a special task into a workflow that, for
example, sends an HTTP request to whatever you need to notify about workflow
completion. Although, I see it rather as a hack (not so horrible though).
Renat Akhmerov
@ Mirantis Inc.
On 28 Aug 2014, at 12:01, Renat
Team,
Please take a look at the new BP
https://blueprints.launchpad.net/mistral/+spec/mistral-access-filtering.
Interested in your feedback and shared experience. Although it’s a purely
internal design thing I find pretty important to be accurate about things like
that.
Thanks
Renat
discussion (storing actions in DB etc.)
* Open discussion
(See http://wiki.openstack.org/wiki/Meetings/MistralAgenda for meeting archive)
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org
at the same time.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
and make corrections if needed.
Renat Akhmerov
@ Mirantis Inc.
On 22 Aug 2014, at 11:12, Dmitri Zimine dzim...@stackstorm.com wrote:
Hi Stackers,
we are discussing the API, v2.
The core team captured the initial thoughts
here (most recent):
https://etherpad.openstack.org/p/mistral
://wiki.openstack.org/wiki/Meetings/MistralAgenda if
you need to find meeting archive.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
://wiki.openstack.org/wiki/Meetings/MistralAgenda
Next Monday on Aug 25 we’ll meet again.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks,
Dmitri, I left my comments in the document you shared. Please take a loot at
them. We also need to define a reasonable date for 0.1 release which is now set
to Sept 11 according to my very raw estimates. We may want to move it a little
bit.
Renat Akhmerov
@ Mirantis Inc.
On 14 Aug
to the previous meetings).
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/MistralAgenda
The next meeting will be held on Aug 11.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
to the previous meetings.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks for joining the meeting today!
Meeting minutes:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-07-21-16.00.html
Log:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-07-21-16.00.log.html
The next meeting will be held on July 28th.
Renat Akhmerov
as the links to the previous meetings.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks for joining us today!
As usually,
Minutes:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-07-14-16.00.html
Full Log:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-07-14-16.00.log.html
The next meeting will be held on July 21st.
Renat Akhmerov
discussion
You can also find this agenda at
https://wiki.openstack.org/wiki/Meetings/MistralAgenda as well as the links to
the previous meetings.
Looking forward to see you there!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack
meeting is scheduled for July 14th.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Engine (which
is one of the most important parts of Mistral now). It’s somewhat confusing to
me, especially when I navigate through the project structure. It’s not a
critical urgent thing, of course, but would be nice if you share your opinion.
What do you guys think?
Renat Akhmerov
@ Mirantis Inc
-mistralclient:
...
etc.
Renat Akhmerov
@ Mirantis Inc.
On 24 Jun 2014, at 14:39, Anastasia Kuznetsova akuznets...@mirantis.com wrote:
(reposting due to lack of subject)
Hello, everyone!
I am happy to announce that Mistral team started working on test
infrastructure. Due to this fact I
://blueprints.launchpad.net/mistral/+spec/mistral-engine-executor-protocol,
we just need to clarify the intent
That was an initial design (that didn’t take lots of things into account). I
agree this is all bad. Particularly, we can’t fail the whole execution at once.
Renat Akhmerov
@ Mirantis Inc
process and
had to be abandoned.)
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Folks,
We’re cancelling today’s community meeting for a number of reasons
(intermediate release activities, not all important members will be available).
Let’s meet next Monday on 06/30/2014.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev
In case you have urgent questions please ping me personally.
Renat Akhmerov
@ Mirantis Inc.
On 23 Jun 2014, at 18:17, Renat Akhmerov rakhme...@mirantis.com wrote:
Folks,
We’re cancelling today’s community meeting for a number of reasons
(intermediate release activities, not all
into the refactoring. It will be easy to do, but takes
the longest.
I personally would prefer this latest option since I don’t see any rush with
refactoring the current API/impl to have two separate workflow types right now.
Renat Akhmerov
@ Mirantis Inc.
On 20 Jun 2014, at 12:33, Dmitri Zimine dzim
it over though...
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Thanks Timur, that’s a good doc.
Anastasia and Sergey were supposed to start working on a proposal devoted to
our approaches to integration testing. I hope we’ll see them soon.
Renat Akhmerov
@ Mirantis Inc.
On 11 Jun 2014, at 13:55, Timur Nurlygayanov tnurlygaya...@mirantis.com wrote:
Hi
Dmitri, this is a true statement. Mistral is fully abstracted out from a
concrete transport.
Renat Akhmerov
@ Mirantis Inc.
On 17 Jun 2014, at 00:52, Dmitry Borodaenko dborodae...@mirantis.com wrote:
Mistral doesn't have to be married to RabbitMQ, there's a ZeroMQ
driver in oslo.messaging
Ooh, alright :) It passed by me why I was off.
Renat Akhmerov
@ Mirantis Inc.
On 18 Jun 2014, at 01:20, W Chan m4d.co...@gmail.com wrote:
I figured. I implemented it in https://review.openstack.org/#/c/97684/.
On Mon, Jun 16, 2014 at 9:35 PM, Renat Akhmerov rakhme...@mirantis.com
be better aware. Dmitri? As far
as engine-executor interaction we now have an issue with it that we need to
fix but it’s not related with parallelism. The protocol itself is not 100%
complete in terms of reliability.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 06 Jun 2014, at 23:12, W Chan m4d.co
/MistralAgenda
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
I don’t think we have them. You can write them I think as a part of what you’re
doing.
Renat Akhmerov
@ Mirantis Inc.
On 31 May 2014, at 04:26, W Chan m4d.co...@gmail.com wrote:
Is there an existing unit test for testing enabling keystone middleware in
pecan (setting
of blueprints currently accepted for Juno:
https://blueprints.launchpad.net/mistral/juno
Thanks!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
On 28 May 2014, at 13:51, Angus Salkeld angus.salk...@rackspace.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17/05/14 02:48, W Chan wrote:
Regarding config opts for keystone, the keystoneclient middleware already
registers the opts at
as well as links to the previous meeting minutes and logs.
Looking forward to see you all there!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
Hi,
As usually, meeting minutes and full log:
Minutes:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-05-26-16.00.html
Full log:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-05-26-16.00.html
Thanks
Renat Akhmerov
@ Mirantis Inc
configuration option
definitions (types, descriptions etc.) but with this refactoring it seems to be
a tricky task.
Thoughts? What benefits of doing that?
Renat Akhmerov
@ Mirantis Inc.
On 16 May 2014, at 21:32, Dmitri Zimine d...@stackstorm.com wrote:
+1 for breaking down the configuration
and hence provide
tremendous usability benefits for the community.
Totally support bi-weekly meetings, let me take this part and figure out the
schedule that would work for everyone of us.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 15 May 2014, at 22:30, Joshua Harlow harlo...@yahoo-inc.com wrote
to see you there!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
to see you there!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
://wiki.openstack.org/wiki/Mistral
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
://wiki.openstack.org/wiki/EventScheduler
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/MistralAgenda
as well as the links to the previous meeting minutes and logs.
Thanks!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
activities
and have the next meeting on May 26th. Thoughts?
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
/stackforge/python-mistralclient
Thanks!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
://wiki.openstack.org/wiki/Meetings/MistralAgenda
as well as the links the previous meeting minutes and logs.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
Thanks for joining today’s community meeting.
Minutes:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-04-28-16.00.html
Full log:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-04-28-16.00.log.html
The next meeting is scheduled for May 5.
Renat Akhmerov
be
much easier to talk about opportunities for integration because everyone will
be able to find out what exactly Mistral is.
Thanks
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
I appreciate that Zane! I’ll set up at least ten alarm clocks to wake up on
time :)
Renat Akhmerov
@ Mirantis Inc.
On 18 Apr 2014, at 06:44, Zane Bitter zbit...@redhat.com wrote:
On 17/04/14 00:34, Renat Akhmerov wrote:
Ooh, I confused the day of meeting :(. My apologies, I’m in a completely
Ok, no problem :)
Renat Akhmerov
@ Mirantis Inc.
On 16 Apr 2014, at 12:43, Joshua Harlow harlo...@yahoo-inc.com wrote:
I have stricken the word micro and language from my vocabulary. Begone
evil demons!! Haha :)
Sent from my really tiny device...
On Apr 15, 2014, at 10:35 PM, Renat
Hi,
Can we include action item “Heat/Mistral collaboration” into the agenda of
tomorrow’s Heat community meeting? I’d like to take a few minutes and discuss
this a little bit. If you think it’s not a suitable time/way to discuss it
please let me know your preferences.
Thanks
Renat Akhmerov
Ok. The reason I asked about it is because I recognize you guys may be very
busy now for pre-summit activities going on. :)
Thanks!
Renat Akhmerov
@ Mirantis Inc.
On 16 Apr 2014, at 22:18, Zane Bitter zbit...@redhat.com wrote:
On 16/04/14 10:29, Renat Akhmerov wrote:
Can we include action
401 - 500 of 652 matches
Mail list logo
