<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">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.<div><br></div><div>We already have a BP (<a href="https://blueprints.launchpad.net/mistral/+spec/mistral-pluggable-task-actions">https://blueprints.launchpad.net/mistral/+spec/mistral-pluggable-task-actions</a>) but it doesn’t describe how this plugin architecture should be implemented.<br><div><br><div>
<div>Renat Akhmerov</div><div>@ Mirantis Inc.</div><div><br></div><br class="Apple-interchange-newline">
</div>
<br><div><div>On 25 Feb 2014, at 08:43, W Chan <<a href="mailto:m4d.coder@gmail.com">m4d.coder@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">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?<div><br></div><div>Thanks.<br>
<div>Winson</div><div><br></div></div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></div></div></body></html>