Open Stack

Renat,

We want to introduce the concept of an ActionProvider to Mistral.  We are
thinking that with an ActionProvider, a third party system can extend
Mistral with it's own action catalog and set of dedicated and specialized
action executors.  The ActionProvider will return it's own list of actions
via an abstract interface.  This minimizes the complexity and latency in
managing and sync'ing the Action table.  In the DSL, we can define provider
specific context/configuration separately and apply to all provider
specific actions without explicitly passing as inputs.  WDYT?

Winson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141216/adc87883/attachment.html>