[jira] [Resolved] (AIRAVATA-152) Support application level scheduling and outputs in execution context

["Suresh Marru (Resolved) (JIRA)" <ji...@apache.org>]

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

Suresh Marru resolved AIRAVATA-152.
-----------------------------------

    Resolution: Fixed

The schema has now wrapped complex types to specify application specific scheduling and output handling
                
> Support application level scheduling and outputs in execution context
> ---------------------------------------------------------------------
>
>                 Key: AIRAVATA-152
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-152
>             Project: Airavata
>          Issue Type: Improvement
>          Components: Workflow Interpreter, XBaya
>            Reporter: Suresh Marru
>            Assignee: Suresh Marru
>             Fix For: 0.1-INCUBATING
>
>
> Individual application services within a workflow may have different requirements for scheduling, and output data handling. The workflow execution context must be able to specify these individually. Most of the time, all applications will be scheduled on one resource and all outputs are handled in a identical way. But the schema should provision advanced cases where intermediate outputs are handled differently, final outputs may need to be published and so on. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira