Re: [openstack-dev] [Mistral] Workflow on-finish

2014-08-28 Thread W Chan
Is there an example somewhere that I can reference on how to define this
special task?  Thanks!


On Wed, Aug 27, 2014 at 10:02 PM, Renat Akhmerov rakhme...@mirantis.com
wrote:

 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


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Re: [openstack-dev] [Mistral] Workflow on-finish

2014-08-28 Thread Renat Akhmerov
Yes, it’s just a regular task that sends a request. Something like:

notify_about_completion:
  action: std.http
  parameters:
url: whatever_we_need.org
method: GET

You can also take a look at webhooks examples in mistral-extra.

Renat Akhmerov
@ Mirantis Inc.



On 29 Aug 2014, at 01:22, W Chan m4d.co...@gmail.com wrote:

 Is there an example somewhere that I can reference on how to define this 
 special task?  Thanks!
 
 
 On Wed, Aug 27, 2014 at 10:02 PM, Renat Akhmerov rakhme...@mirantis.com 
 wrote:
 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
 
 
 ___
 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


Re: [openstack-dev] [Mistral] Workflow on-finish

2014-08-27 Thread Renat Akhmerov
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


Re: [openstack-dev] [Mistral] Workflow on-finish

2014-08-27 Thread Renat Akhmerov
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