<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Right now, you can just include a special task into a workflow that, for example, sends an HTTP request to whatever you need to notify about workflow completion. Although, I see it rather as a hack (not so horrible though).<div><br><div>
<div>Renat Akhmerov</div><div>@ Mirantis Inc.</div><div><br></div><br class="Apple-interchange-newline">
</div>
<br><div><div>On 28 Aug 2014, at 12:01, Renat Akhmerov <<a href="mailto:rakhmerov@mirantis.com">rakhmerov@mirantis.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">There are two blueprints that I supposed to use for this purpose:<div><a href="https://blueprints.launchpad.net/mistral/+spec/mistral-event-listeners-http">https://blueprints.launchpad.net/mistral/+spec/mistral-event-listeners-http</a></div><div><a href="https://blueprints.launchpad.net/mistral/+spec/mistral-event-listeners-amqp">https://blueprints.launchpad.net/mistral/+spec/mistral-event-listeners-amqp</a></div><div><br></div><div>So my opinion:</div><div><ul class="MailOutline"><li>This functionality should be orthogonal to what we configure in DSL.</li><li>The mechanism of listeners would is more generic and would your requirement as a special case.</li><li>At this point, I see that we may want to implement a generic transport-agnostic listener mechanism internally (not that hard task) and then implement required transport specific plugins to it.</li></ul><div><br></div></div><div>Inviting everyone to discussion.</div><div><br></div><div>Thanks</div><div><br><div>
<div>Renat Akhmerov</div><div>@ Mirantis Inc.</div><div><br></div><br class="Apple-interchange-newline">
</div>
<br><div><div>On 28 Aug 2014, at 06:17, 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">Renat,<div><br></div><div>It will be helpful to perform a callback on completion of the async workflow. Can we add <span style="color:rgb(51,51,51);font-family:sans-serif;font-size:12px;line-height:18px">on-finish to the workflow spec and when workflow completes, runs task(s) defined in the on-finish section of the spec? This will allow the workflow author to define how the callback is to be done.</span></div>
<div><br></div><div>Here's the bp link. <a href="https://blueprints.launchpad.net/mistral/+spec/mistral-workflow-on-finish">https://blueprints.launchpad.net/mistral/+spec/mistral-workflow-on-finish</a><br></div><div><br>
</div><div>Thanks.</div><div>Winson</div><div><br></div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></blockquote></div><br></div></div></blockquote></div><br></div></body></html>