Hi Hasitha,

On Jun 5, 2012, at 8:14 AM, Hasitha Aravinda wrote:

> Hi ,
> 
> Thank Suresh,
> 
> Does it mean that, an event xml without an attribute 'workflowID' indicates
> the event of an experiment. If an workflowID present in the xml (inside
> notificationSource tag) it is corresponding to a workflow event. Is this
> correct?

Did you check the workflow tracking schema [1]? it has a decent description of 
the schema. Ideally speaking, every execution event should at the minimum have 
a experiment id, workflow id. Also, please read the following papers which will 
explain you the schema for events in a detailed way [2] , [3].
> 
> Also Can we have sample notification messages for a experiment which has
> multiple workflows ?

I do not think Airavata has hierarchal workflow samples. One way to obtain that 
is to change your question and ask the dev's nicely :) a questions can be 
something like ...I will create an experiment with hierarchal workflows (a meta 
workflow with sub workflows) Can any one help me do that? ..a answer will be 
something like ..please goahead and do it, if you run into issues, raise a JIRA 
and we will help you fix it and submit a patch :) 

Cheers,
Suresh

[1] - 
https://svn.apache.org/repos/asf/incubator/airavata/trunk/modules/commons/workflow-tracking/src/main/resources/schemas/workflow_tracking_types.xsd
[2] - http://gridtestbed.org/sites/default/files/SimmhanICWS06.pdf
[3] - http://www.ptl.iu.edu/sites/default/files/Simmhan-JWSR-07.pdf


> 
> Thank You,
> Hasitha.
> 
> On Tue, Jun 5, 2012 at 10:41 AM, Suresh Marru <[email protected]> wrote:
> 
>> Hi Hasitha,
>> 
>> All three of these are for different purposes.
>> 
>> An experiment corresponds to an "experiment" or "investigation" done by a
>> scientist/user and might require multiple workflows (in a hierarchal
>> fashion) to accomplish it. A single workflow most of the times has many
>> services in it. So the hierarchy is experiment id -> (one or more workflow
>> ids) -> one or more service id's.
>> 
>> Suresh
>> On Jun 5, 2012, at 12:59 AM, Hasitha Aravinda wrote:
>> 
>>> Hi Devs,
>>> 
>>> Now, We are working on metadata extracting component of Metadata catalog.
>>> We went though the workflow tracking schema [1], and found that
>> workflowID
>>> is an optional field. I would like to know about relationship between
>>> experimentID, workflowID and serviceID for an experiment / workflow
>>> execution.
>>> 
>>> We want to know mainly following details,
>>> 
>>> 1. Are always experimentID and workflowID  equals?
>>> 2. consider following part of a workflowInvoked message,
>>> 
>>> <wor:workflowInvoked infoModelVersion="2.6" xmlns:wor="
>>> http://airavata.apache.org/schemas/workflow_tracking_types";>
>>> 
>>> <wor:notificationSource wor:serviceID="*
>>> _691c768f_9f9d_41ae_b90b_bfad37f2aba9*" wor:experimentID="*
>>> 691c768f-9f9d-41ae-b90b-bfad37f2aba9*" />
>>> 
>>> <wor:timestamp>2012-06-05T10:20:25.101+05:30</wor:timestamp>
>>> 
>>> <wor:description>param1=15, param2=16, param1=18, param2=21, param1=25,
>>> param2=30, param1=36, param2=43</wor:description>
>>> 
>>> <wor:annotation />
>>> 
>>> <wor:initiator wor:serviceID="_691c768f_9f9d_41ae_b90b_bfad37f2aba9" />
>>> 
>>> </wor:workflowInvoked>
>>> 
>>> 
>>> why the serviceID has an underscore followed by experimentID ? and can
>> they
>>> be considered as equal in all usecases?
>>> 
>>> 
>>> Thank you,
>>> Hasitha.
>>> 
>>> 
>>> [1] -
>>> 
>> http://svn.apache.org/repos/asf/incubator/airavata/trunk/modules/commons/workflow-tracking/src/main/resources/schemas/workflow_tracking_types.xsd
>> 
>> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to