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).
Renat Akhmerov @ Mirantis Inc. On 28 Aug 2014, at 12:01, Renat Akhmerov <rakhme...@mirantis.com> wrote: > There are two blueprints that I supposed to use for this purpose: > https://blueprints.launchpad.net/mistral/+spec/mistral-event-listeners-http > https://blueprints.launchpad.net/mistral/+spec/mistral-event-listeners-amqp > > So my opinion: > This functionality should be orthogonal to what we configure in DSL. > The mechanism of listeners would is more generic and would your requirement > as a special case. > 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. > > Inviting everyone to discussion. > > Thanks > > Renat Akhmerov > @ Mirantis Inc. > > > > On 28 Aug 2014, at 06:17, W Chan <m4d.co...@gmail.com> wrote: > >> Renat, >> >> It will be helpful to perform a callback on completion of the async >> workflow. Can we add 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. >> >> Here's the bp link. >> https://blueprints.launchpad.net/mistral/+spec/mistral-workflow-on-finish >> >> 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
