airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-1551) Handling Application Outputs
Date Fri, 16 Jan 2015 20:00:35 GMT


ASF subversion and git services commented on AIRAVATA-1551:

Commit ab59a1574f7e760345443fe600a0137fe833c093 in airavata's branch refs/heads/master from
[;h=ab59a15 ]

To fix output and stdout/error paths in job context.AIRAVATA-1551

> Handling Application Outputs
> ----------------------------
>                 Key: AIRAVATA-1551
>                 URL:
>             Project: Airavata
>          Issue Type: Story
>          Components: Airavata API, Application Catalog, GFac
>    Affects Versions: 0.15 
>            Reporter: Raminderjeet Singh
>            Assignee: Raminderjeet Singh
> Scientific applications consume inputs and produce outputs. Currently, we handle application
outputs either by scanning STDOUT or looking into output data directory. We had to add wrapper
scripts for different application to handle outputs in the way Airavata understands. Output
handler code is overloaded with those details and difficult to extend/improve. To improve
output handler code and to support application without wrapper scripts, we need to rewrite
these handlers. 
> Requirements for new code are:
> 1. New handler code should work based on experiment object or a internal gfac context.

> 2. Stop scanning STDOUT file for outputs and use gateway defined output names/locations
to map outputs.
> 3. STDOUT and STDERR will be output for every application and we will not treat them
as special outputs.
> 4. Primitive type data types(STRING, INT) will not be supported for batch job. They always
produce stdout and stderr and these will be output for simple jobs like ECHO. So output for
echo like jobs can be found in stdout file.

This message was sent by Atlassian JIRA

View raw message