airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raminderjeet Singh <>
Subject Re: Workflow Notification Report
Date Thu, 06 Sep 2012 16:03:44 GMT

On Sep 6, 2012, at 10:24 AM, Suresh Marru wrote:

> +1 on the requirement and making it part of the release 0.6 or later.
> As for solution, I think we really need to formalize workflow monitoring and decouple
it from workflow interpreter. It should be aware of the state of workflows in interaction
with enactment engine but loosely coupled with it.
Yes it can be away from workflow interpreter. Other other place which have the workflow state
and resolve the relationship of notification is provenance manager. We can call that as monitoring
and provenance as we don't want to listen same notification twice to judge start/termination
of workflow.  Reports can be generated from saved data based on some filters. 

> Like this example, we can foresee users asking, please tweet me once done, or push a
Mac notification, or update my Facebook wall that the workflow I ran is finished :) 
These are all good requirement and can be developed as we go. We can have the framework extendable.

> It will be nice to have volunteers implement a first class workflow monitoring support.
There is a code in sandbox [1] for reference, I don't mean to stick to its implementation,
but to get an idea and develop a pluggable monitoring framework harnessing the workflow tracking
schema and ws messenger capabilities. 
> Suresh
> [1] -
> On Sep 6, 2012, at 10:12 AM, Raminderjeet Singh <> wrote:
>> Hash: SHA1
>> Hi Dev,
>> I came across a requirement of Email notification for workflow run incase of success
and failure for 2 different Gateways (DES (Dark energy survey) and ODI  (one degree imager)).
I feel its a useful feature and users can be notified on completion/termination of workflow.
This can to be a optional feature and should be configured by user. My idea is to have notification
code part of Workflow interpreter code as it controls the state of the workflow. Challenging
part in this requirement is configuration of the sender of email. Any comments about the requirement
and solution for the email sender configuration steps.  
>> Thanks
>> Raminder
>> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
>> wK06Dg5eogF+VoLNLkPuMgaax/a2lCtNFXZSImREYawF9aWnUBhYrWcqRb5H+vAD
>> bvDO7XhtTPPzHnCNTof01iDmFJxrXog1p+FHi4HB/Z0LJH0nKv5vCYGZY2eAq3ww
>> 8e3sooMvS+Kdzt4Tt8vaNZGY9PUmDymEGlWqM6Y7Viw9C3vPrZAs+xTNmINmSLCl
>> aVa7aaznEmZvsdU0aBnf8GW3gFOZvv3CLMzMiJ0DXwpX0u7wIQXdh+vc4tsjBWMT
>> XQbdCE/EkzQ21H2nhWQ9EeXmW6qpW0SnKHSaJPQBYkrKa1QhlABFOYcO3ihqjQvZ
>> D4g+JsGBDtdmGh+59q0NvB8O61ZB/lDAVZucmSIrS6RWpXMfDuRTLtFjXS+rtC5e
>> FfwgNwGyAmSqf732PrKVSaf2WRhtCypXid5sJju5+jqK81CUAKS6l2AO2a64J42c
>> VR2i6g9LlTybx/fscJtvalpIqpYs4+deiBuoqETmDtlLwP5ZHRpjW7rH1UVjQhXJ
>> m+fRY0xAfqFM8Sj+sHfaKZAvade0AN8hFa8wz0KbcVesSQrBFzz4cFGTEat0X9Pd
>> jDZIFHZxaotHxgiqGm6zkbYinNs3C5nT1GAG5LXGfJSQM42Fi6+PuYK568nHO29N
>> XiDrEZPfsJHEb0X6tVVy
>> =JG5I
>> -----END PGP SIGNATURE-----

View raw message