You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2013/03/23 16:55:15 UTC

[jira] [Updated] (AIRAVATA-342) [GSoC] Integrate Airavata Workflow Interpreter with OODT to improvise provenance aware workflow execution

     [ https://issues.apache.org/jira/browse/AIRAVATA-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated AIRAVATA-342:
---------------------------------------

    Labels: gsoc2012 gsoc2013 mentor  (was: gsoc2012 mentor)
    
> [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