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
://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
and make corrections if needed.
Renat Akhmerov
@ Mirantis Inc.
On 22 Aug 2014, at 11:12, Dmitri Zimine wrote:
> Hi Stackers,
>
> we are discussing the API, v2.
>
> The core team captured the initial thoughts
>
> here (most recent):
> https://etherpad.openst
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
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
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
.
Inviting everyone to discussion.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 28 Aug 2014, at 06:17, W Chan 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, ru
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
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
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
so 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/open
://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
-16.01.log.html
The next meeting is scheduled for Sep 22.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
as “action” 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, Dmi
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
Hi,
I’ll be on vacation till Dec 17th. I’ll be replying emails but with delays.
Thanks
Renat Akhmerov
@Nokia
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ
://wiki.openstack.org/wiki/Mistral#Etherpads
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.
Feel free to join us and discuss all the Mistral activities!
Thanks.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cg
!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
about them and tell us what you need from Mistral
to be able to use it in other projects.
Thanks!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
to participate and contribute!
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.
Join us to build Mistral in the way you need!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/lis
.2013-12-02-16.00.log.html
Feel free to join us next time!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi,
We’re inviting everyone to participate our community meeting at
#openstack-meeting today at 16.00 UTC.
Here’s the link to meeting agenda:
https://wiki.openstack.org/wiki/Meetings/MistralAgenda
Thanks!
Renat Akhmerov
@ Mirantis Inc
Join us next time to discuss Mistral PoC and Mistral Engine architecture.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Hi!
This is a reminder that we will have another community meeting today in IRC
(#openstack-meeting) at 16.00 UTC.
Here’s the agenda: https://wiki.openstack.org/wiki/Meetings/MistralAgenda
As usually, you’re welcome to join!
Renat Akhmerov
@ Mirantis Inc
time.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
ll evaluate to:
{
"street": "25 Broadway Avenue",
"city": "Woodstock"
}
And corresponding HTTP request will be:
http POST http://localhost:8988/my_service/action1
{
"street": "25 Broadway Avenue",
&quo
“straightforward” flow definition is preferred.
Regardless of the option described here a user would start new workflow
execution with specifying a particular task in a graph.
As always, we would like to get your feedback on this.
Thanks!
Renat Akhmerov
@ Mirantis Inc.
___
Hi,
Due to NY celebrations and upcoming holidays I would suggest we cancel the next
two Mistral community meetings: today on Dec 30 and on Jan 6. I tend to think
they’re not going to be super productive.
However, if someone still would like to have them please let us know.
Thanks.
Renat
yourself since TaskFlow does
not support it now, at least I didn’t find anything like that (Joshua can
provide more details on that).
Thanks.
Renat Akhmerov
@Mirantis Inc.___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
Sorry for being a little bit verbose :) …
Renat
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
efinition similar to
provided above.
So my main point here that I was trying to make is that EventScheduler is just
a special case of Mistral capabilities. We can just provide a convenience for
scheduling webhook calls on the API (a couple of hours to implement).
Thanks! Happy New Year to everyo
/Meetings/MistralAgenda
as well as logs and minutes for 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
.log.html
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
the entire coding
culture is built of.
Renat Akhmerov
@ Mirantis Inc.
On 14 Jan 2014, at 06:00, Jay Pipes wrote:
> On Tue, 2014-01-14 at 08:01 -0500, Doug Hellmann wrote:
>> Ned Batchelder had an interesting post a few days ago about why code
>> comments should be written as com
that.
Renat Akhmerov
@ Mirantis Inc.
On 02 Jan 2014, at 09:52, Greg Hill wrote:
> Renat,
>
> Thanks for the additional information. I've been trying to put the pieces of
> history together and it seems I missed some of it. I think I now understand
> the evolution of t
Great idea, fully support it. We’re interested in that too. One specific thing
that was mentioned is the ability to mock auth service seems to be very useful
for some test scenarios, we came across that recently.
Renat Akhmerov
@ Mirantis Inc.
On 15 Jan 2014, at 14:07, Sylvain Bauza wrote
fully functional REST client
automatically based on an API specification (WADL could be used for that)? Not
sure how convenient it would be, it really depends on a particular
implementation, but as an idea it could be at least thought of. Sounds a little
bit crazy though, I recognize it :).
Renat
On 16 Jan 2014, at 12:36, Dean Troyer wrote:
> I've already written a POC for solum and some other things to demonstrate how
> to add additional projects simply by installing the python-*client package.
> https://github.com/dtroyer/python-oscplugin is a trivial example.
Thanks, this link is
On 16 Jan 2014, at 13:06, Jesse Noller wrote:
>> Since it’s pretty easy to get lost among all the opinions I’d like to
>> clarify/ask a couple of things:
>>
>> Keeping all the clients physically separate/combining them in to a single
>> library. Two things here:
>> In case of combining them, w
projects? So
if yes, it’s just going to be one more incubation/integration requirement,
right?
Renat
On 16 Jan 2014, at 18:09, Donald Stufft wrote:
>
> On Jan 16, 2014, at 8:42 PM, Jesse Noller wrote:
>
>>
>>
>> On Jan 16, 2014, at 4:59 PM, "Renat Akhmerov&quo
On 17 Jan 2014, at 10:04, Jonathan LaCour
wrote:
> "pip install openstack"
That would be awesome :)
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cg
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 17 Jan 2014, at 22:00, Jamie Lennox wrote:
> (I don't buy the problem with large amounts of dependencies, if you have a
> meta-package you just have one line in requirements and pip will figure the
> rest out.)
+1
Renat Akhmerov
On 17 Jan 2014, at 22:06, Robert Collins wrote:
> On 17 January 2014 09:22, Renat Akhmerov wrote:
>> Since it’s pretty easy to get lost among all the opinions I’d like to
>> clarify/ask a couple of things:
>>
>> Keeping all the clients physically separate/co
ing
about building a complex object from small pieces. We haven’t made a decision
though. We’ll be discussing it with the community.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack
On 21 Jan 2014, at 09:07, Jesse Noller wrote:
> Do you use any other platform than Linux? Even donald - one of the python
> packaging leads and PyPI leads said this is a bad end-user experience for
> consumers of openstack clouds.
That fact that someone (even very smart experience) said somet
On 21 Jan 2014, at 09:40, Sean Dague wrote:
> On 01/21/2014 11:54 AM, Renat Akhmerov wrote:
>>
>> On 17 Jan 2014, at 22:00, Jamie Lennox > <mailto:jamielen...@redhat.com>> wrote:
>>
>>> (I don't buy the problem with large amounts of dependencie
+1 for opening new threads regarding specific questions.
On 21 Jan 2014, at 11:54, Renat Akhmerov wrote:
>
> On 21 Jan 2014, at 09:40, Sean Dague wrote:
>
>> On 01/21/2014 11:54 AM, Renat Akhmerov wrote:
>>>
>>> On 17 Jan 2014, at 22:00, Jamie Lennox
On 21 Jan 2014, at 11:55, Alexander Tivelkov wrote:
>
> murano - main services, common, agents docs, deployments scripts
> python-muranoclient - python bindings and CLI
> murano-dashboard - OS Dashboard plugin
> murano-apps - new repo for metadata, including core library and example apps.
> mur
ld be written as the
> author may not be a native english speaker.
Yes, sure. That’s how we (non-native speakers) learn. )
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 23 Jan 2014, at 08:41, Joshua Harlow wrote:
> So to me memoizing is typically a premature optimization in a lot of cases.
> And doing it incorrectly leads to overfilling the python processes memory
> (your global dict will have objects in it that can't be garbage collected,
> and with enou
Hi folks,
I would suggest we cancel our next community meeting on Monday 01/27/2014 since
several active participants (including myself) won’t be available. So the next
meeting is scheduled on 02/03/2013.
Renat Akhmerov
@ Mirantis Inc
Ok, I see. Thanks, good to know.
Renat Akhmerov
@ Mirantis Inc.
On 23 Jan 2014, at 14:33, Doug Hellmann wrote:
> The fact that it is already in the requirements list makes it a top contender
> in my mind, unless we find some major issue with it.
>
> Doug
>
>
> On Thu,
Joining to providing our backgrounds.. I’d be happy to help here too since I
have pretty solid background in using and developing caching solutions, however
mostly in Java world (expertise in GemFire and Coherence, developing GridGain
distributed cache).
Renat Akhmerov
@ Mirantis Inc.
On
feature
sets.
Renat Akhmerov
@ Mirantis Inc.
On 27 Jan 2014, at 13:21, Joshua Harlow wrote:
> Hi all,
>
> In order to encourage further discussion off IRC and more in public I'd like
> to share a etherpad that was worked on during a 'meetup' with some of the
> mi
contributors)
Discuss DSL example (https://etherpad.openstack.org/p/mistral-poc)
Discuss current PoC status
Review Blueprints (at least part)
Open discussion (roadblocks, suggestions, etc.)
As usually, everyone is welcome to join!
[0] https://wiki.openstack.org/wiki/Meetings/MistralAgenda
Renat Akhmerov
Hi,
Thanks for joining us today!
Here are the links to minutes and log:
Minutes:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-02-03-16.00.html
Log:
http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-02-03-16.00.log.html
Renat Akhmerov
@ Mirantis Inc
Dmitri,
Sure, no problem. Good considerations. I’m now in the process of reviewing your
notes..
Renat Akhmerov
@ Mirantis Inc.
On 04 Feb 2014, at 09:05, Dmitri Zimine wrote:
> Following up from yesterday's community meeting
>
> I am still catching up with the project, still
I guess it should be but just in case…
Renat Akhmerov
@ Mirantis Inc.
On 06 Feb 2014, at 07:58, Doug Hellmann wrote:
>
>
>
> On Thu, Feb 6, 2014 at 10:11 AM, Sylvain Bauza
> wrote:
> Thanks Doug,
>
>
>
>
> 2014-02
Doug, is it backwards compatible with 0.5b6?
Renat Akhmerov
@ Mirantis Inc.
On 06 Feb 2014, at 07:58, Doug Hellmann wrote:
>
>
>
> On Thu, Feb 6, 2014 at 10:11 AM, Sylvain Bauza
> wrote:
> Thanks Doug,
>
>
>
>
> 2014-02
Hi guys,
I would suggest we skip today’s community meeting since some folks from the
team (including myself) won’t be able to participate. My apologies for the late
notice..
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack
itself”. Does that make sense?
Renat Akhmerov
@ Mirantis Inc.
On 11 Feb 2014, at 16:23, Dmitri Zimine wrote:
> Do we have (or think about) a shorthand to calling REST_API action, without
> defining a service?
>
> FULL DSL:
>
> Services:
> TimeService:
&
On 14 Feb 2014, at 15:02, Dmitri Zimine wrote:
> Current DSL snippet:
> actions:
>my-action
> parameters:
> foo: bar
> response: # just agreed to change to 'results’
Just a note: “response” indentation here is not correct, it’s not a parameter
called “response”
“output” looks nice!
Renat Akhmerov
@ Mirantis Inc.
On 14 Feb 2014, at 20:26, Nikolay Makhotkin wrote:
> Current DSL snippet:
> actions:
>my-action
> parameters:
> foo: bar
> response: # just agreed to change to 'results'
>
On 15 Feb 2014, at 04:01, Nikolay Makhotkin wrote:
> Dmitri, in our concerns under word 'input' we assume a block contains the
> info about how the input data will be taken for corresponding task from
> initial context. So, it will be a kind of expression (e.g. YAQL).
>
> Renat, am I right?
another etherpad for further
long-term discussions.
Renat Akhmerov
@ Mirantis Inc.
On 15 Feb 2014, at 06:26, Dmitri Zimine wrote:
> Ok, I see.
>
> Do we have a spec that describes this?
> Lets spell it out and describe the whole picture of input, output,
> parameters, and r
both languages look similar or at least
the possibility to use them seamlessly, if needed (call Mistral workflows from
Murano DSL or vice versa).
Renat Akhmerov
@ Mirantis Inc.
On 16 Feb 2014, at 05:48, Clint Byrum wrote:
> Excerpts from Alexander Tivelkov's message of 2014-02-14 18:17:10
. Thanks!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
!
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
links to the previous meeting minutes and
logs at https://wiki.openstack.org/wiki/Meetings/MistralAgenda.
Please follow up on this email if you have additional items to discuss.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack
meeting will be held on March 3. Looking forward to chat with you again.
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
sks over task executors via asynchronous HA
transport (scalable). Later on we decided to leave them both since scalable is
needed by the requirements and local might be useful for demonstration purposes
and testing since it doesn’t require RabbitMQ to be installed. So we decided to
refactor both
On 25 Feb 2014, at 07:12, W Chan wrote:
> As I understand, the local engine runs the task immediately whereas the
> scalable engine sends it over the message queue to one or more executors.
Correct.
> In what circumstances would we see a Mistral user using a local engine (other
> than test
team and assign this
task to someone else.
We already have a BP
(https://blueprints.launchpad.net/mistral/+spec/mistral-pluggable-task-actions)
but it doesn’t describe how this plugin architecture should be implemented.
Renat Akhmerov
@ Mirantis Inc.
On 25 Feb 2014, at 08:43, W Chan wrote
“In process” is fine to me.
Winson, please register a blueprint for this change and put the link in here so
that everyone can see what it all means exactly. My feeling is that we can
approve and get it done pretty soon.
Renat Akhmerov
@ Mirantis Inc.
On 25 Feb 2014, at 12:40, Dmitri Zimine
that I’m
currently working on the first Data Flow implementation and I feel that not
everything is good with our understanding of what parameters are, at least with
my understanding ). But I think it makes sense to start a new thread to discuss
this in details.
Thanks
Renat Akhmerov
@ Miranti
Yes, right. Thanks Winson.
Renat Akhmerov
@ Mirantis Inc.
On 26 Feb 2014, at 01:39, W Chan wrote:
> Sure. Let me give this some thoughts and work with you separately. Before
> we speak up, we should have a proposal for discussion.
>
>
> On Mon, Feb 24, 2014 at 9:53 PM
heir additional properties
influencing their nature (like method for HTTP actions).
Please let me know your thoughts. We can make required adjustments right now.
[1] https://etherpad.openstack.org/p/mistral-poc
Renat Akhmerov
@ Mirantis Inc.
___
OpenSt
:
parameters:
url: /servers/{$.vm_id}
method: POST
There’s no information about “REST” or “API” here. It’s just a spec how to form
an HTTP request.
Thoughts?
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack
, and modify the API layer to consume the engine client.
> https://blueprints.launchpad.net/mistral/+spec/mistral-engine-standalone-process.
>
> Winson
>
>
> On Mon, Feb 24, 2014 at 8:07 PM, Renat Akhmerov
> wrote:
>
> On 25 Feb 2014, at 02:21, W Chan wrote:
>
Hm.. I see your point. Generally, I like short names but expressive enough to
understand what it is. VERB_NOUN would be good but nothing decent comes to my
mind regarding HTTP :)
If you guys have any suggestions you’re welcome.
Renat Akhmerov
@ Mirantis Inc.
On 26 Feb 2014, at 16:33, Dmitri
On 26 Feb 2014, at 15:18, Timur Nurlygayanov wrote:
> for me just unclear the following syntacsis:
> $.image_id
> what is $ in this case? It will be more clear if we can replace $ to
> something - any instance with readable name, like global.image_id or
> context.image_id.
> looks like $ can b
.
Renat Akhmerov
@ Mirantis Inc.
On 26 Feb 2014, at 17:58, Jay Pipes wrote:
> On Wed, 2014-02-26 at 14:38 +0700, Renat Akhmerov wrote:
>> Folks,
>>
>> I’m proposing to rename these two action types REST_API and
>> MISTRAL_REST_API to HTTP and MISTRAL_HTTP. Words “RE
Ooh, I was wrong. Sorry. We use dash naming. We have “on-success”, “on-error”
and so forth.
Please let us know if you see other inconsistencies.
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 26 Feb 2014, at 21:00, Renat Akhmerov wrote:
> Thanks Jay.
>
> Regarding underscore namin
I don’t see any issues with term DSL (Domain Specific Language). This is really
a language which 'workbook definitions’ are written in.
Dmitri, could you please provide more details on why you question it?
Thanks
Renat Akhmerov
@ Mirantis Inc.
On 26 Feb 2014, at 20:12, Nikolay Makh
ng
events about over HTTP or AMQP about changes in workflows' and tasks’ state).
I would also suggest we move events out of “Workflow” section since it’s not
actually a part of workflow.
Thoughts?
If you agree I’ll create a blueprint for this.
Renat Akhmerov
On 26 Feb 2014, at 22:54, Dmitri Zimine wrote:
> Based on the terminology from [1], it's not part of the model, but the
> language that describes the model in the file.
Sorry, I’m having a hard time trying to understand this phrase :) What do you
mean by “model” here? And why should DSL be a
quot;service" actions now look symmetric on input/output.
Yes, makes sense. As you said “we don’t refer the context variables” and that’s
why I’m against of having “store-as” in action declaration, it indirectly
refers to the context (the output of action will be stored under this name in
the context).
Renat Akhmerov
@ Mirantis Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
th all parameters
required by this action and its implementation logic. ActionData is what we
declare in DSL.
Renat Akhmerov
@Mistral Inc___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
goal of Mistral is to provide a workflow
engine and easy way to integrate Mistral with other systems so that we can
trigger workflow execution upon external events like Ceilometer alarms, timer
or anything else.
Feel free to ask any questions, thanks!
Renat Akhmerov
@ Mirantis Inc.
On 27 Feb
significantly.
Team, please research carefully this etherpad and leave your comments. It’s a
pretty tricky thing and we need to figure out the best strategy how to approach
this kind of things. We’re going to have more problems similar to this one.
Renat Akhmerov
@ Mirantis Inc.
On 25 Feb 2014, at 10
You’re welcome! Please let us know if you need more info.
Renat Akhmerov
@ Mirantis Inc.
On 28 Feb 2014, at 09:48, Liuji (Jeremy) wrote:
> Hi,
>
> Yes. I mean the feature like VMware Distributed Resource Scheduler.
> Now I am totally clear about the question. Thanks for your
Ok, thanks guys!
https://blueprints.launchpad.net/mistral/+spec/mistral-rename-event-to-trigger
Renat Akhmerov
@ Mirantis Inc.
On 28 Feb 2014, at 07:41, Dmitri Zimine wrote:
> Agree on both.
>
>
> On Feb 26, 2014, at 8:51 PM, Renat Akhmerov wrote:
>
>> Hi tea
Haah :) Honestly, I don’t like it. “invoke” doesn’t seem to be carrying any
useful information here. And “invoke_mistral” looks completely confusing since
it’s not clear it’s related with HTTP.
Renat Akhmerov
@ Mirantis Inc.
On 27 Feb 2014, at 23:42, Manas Kelshikar wrote:
> How ab
this model (could
be other language, for example). Our initial intention actually was different
but anyway what you’re saying is valid. Looks like Nikolay agrees with me too
and he’s now reworking this commit. Coming up soon.
Renat Akhmerov
@ Mirantis Inc.
On 27 Feb 2014, at 23:36, Manas
1 - 100 of 683 matches
Mail list logo
