Mailing-List: contact airavata-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: airavata-dev@incubator.apache.org
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1486\))
Subject: Re: Workflow Notification Report
From: Suresh Marru <smarru@apache.org>
In-Reply-To: <273B14FE-FB09-413F-934E-128762FA8470@gmail.com>
Date: Thu, 6 Sep 2012 10:24:00 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <B88DA326-DFE7-47FB-91D2-F498CDEC0FA7@apache.org>
References: <273B14FE-FB09-413F-934E-128762FA8470@gmail.com>
To: airavata-dev@incubator.apache.org

+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.

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 :)=20

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.=20

Suresh

[1] - =
https://svn.apache.org/repos/asf/incubator/airavata/sandbox/workflow-monit=
oring-util/

On Sep 6, 2012, at 10:12 AM, Raminderjeet Singh =
<raminderjsingh@gmail.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Hi Dev,
>=20
> 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. =20
>=20
> Thanks
> Raminder
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
>=20
> iQIcBAEBAgAGBQJQSK9MAAoJEA+Bv4sb5yE4yMEP/iVB8CUA3Ty6S2EGQS8K9XeV
> 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
> =3DJG5I
> -----END PGP SIGNATURE-----