Open Stack

Agreed on both event -> trigger & moving triggers out of workflow. Lets get
the blueprint started.

/manas


On Wed, Feb 26, 2014 at 8:51 PM, Renat Akhmerov <rakhmerov at mirantis.com>wrote:

> Hi team,
>
> When I tell peopleI about Mistral I always have a hard time explaining why
> we use term "event" for declaring ways to start workflows. For example,
> take a look at the following snippet:
>
> Workflow:
>    ...
>    events:
>      execute_backup:
>         type: periodic
>         tasks: execute_backup
>         parameters:
>             cron-pattern: "*/1 * * * *"
>
> Here we just tell Mistral "we should run backup workflow every minute".
>
> My suggestion is to rename "events" to "triggers" because actually events
> are going to be sent by Mistral when we implement notification mechanism
> (sending 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
> @ Mirantis Inc.
>
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140227/e76007d3/attachment.html>