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
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
