airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mawathage Sanjaya Priyadarshana Medonsa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-342) [GSoC] Integrate Airavata Workflow Interpreter with OODT to improvise provenance aware workflow execution
Date Sat, 24 Aug 2013 04:07:51 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749293#comment-13749293
] 

Mawathage Sanjaya Priyadarshana Medonsa commented on AIRAVATA-342:
------------------------------------------------------------------

Primary ingredient to successful provenance aware workflow execution is the rich set of Metadata
captured in OODT Metadata catalog. I'd like to know the set of Metadata that should be captured
as part of the output ingestion of the Airavata-OODT integration. These Metadata should able
to provenance aware capabilities in Apache Airavata.
I am planning to store following Metadata together with output file staged at the OODT File
manager repository.
   1. FileName
   2. Execution time
   3. Experiment ID
   4. Wokflow Instance ID
   5. Node ID

I guess input value/type should also be required. Please let me other Metadata that should
be captured to improve provenance aware workflow processing.

                
> [GSoC] Integrate Airavata Workflow Interpreter with OODT to improvise provenance aware
workflow execution
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-342
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-342
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Workflow Interpreter
>            Reporter: Suresh Marru
>              Labels: gsoc2012, gsoc2013, mentor
>             Fix For: WISHLIST
>
>
> Airavata workflow interpreter provides features of provenance aware workflow execution.
In a over simplified case If a workflow has 10 components, and if 5th component output is
already in there in the registry, then workflow dynamically adapts the graphs and jumps to
executes from 6th component. This feature needs the output matching to be semantically correct.
Rich metdata expression about outputs and an efficient data cataloging and querying will enhance
this capability significantly. 
> The proposed new feature is to utilize OODT to register, query and adapt the workflow
execution based on the enhanced metadata extraction and cataloging. Airavata & OODT developer
communities will be able guide in implementing this task.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message