Yes, it’s one of the important things that we would like to implement. It’s not the highest priority right now but we definitely need to do that. Dmitri Zimine and I talked about it and at some point Dmitri wanted to start working on it. However, we can decide to rearrange our plans within the 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 <m4d.co...@gmail.com> wrote: > Will Mistral be supporting custom actions developed by users? If so, should > the Actions module be refactored to individual plugins with a dynamic process > for action type mapping/lookup? > > Thanks. > Winson > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
