airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <>
Subject [jira] [Resolved] (AIRAVATA-161) Reorganize Application Schema to make it extendable.
Date Mon, 22 Oct 2012 03:44:15 GMT


Suresh Marru resolved AIRAVATA-161.

    Resolution: Fixed

The schema changes have been incorporated.
> Reorganize Application Schema to make it extendable. 
> -----------------------------------------------------
>                 Key: AIRAVATA-161
>                 URL:
>             Project: Airavata
>          Issue Type: Improvement
>          Components: GFac, XBaya
>            Reporter: Suresh Marru
>            Assignee: Suresh Marru
>             Fix For: 0.1-INCUBATING
> The improvements to the gfac schemas (external xml version and internal pojo representation)
are very good so far. I want to improve this further to take the following into account. 
> * Any application irrespective of computational resource type and application program
paradigm will have the following artifacts: executable location, environment variables, optional
input and output directories, standard input, standard outputs and standard errors, input/output
and temporary scratch work directories. I do not see the need for a shell application description,
everything in shell description is minimalistic to all applications, so I recommend removing
> * Above the basic application, there are batch scheduling applications, with queues and
parallelization parameters. Technically, job type does not always associate with batch systems,
but without one, its very complex to execute MPI, openmp style applications. Map reduce jobs
or any job manager executed jobs can fall into this category. 
> * Cloud based virtual image executed applications can wrap basic application.
> * Grid applications wrap around batch applications. Each grid implementation like globus
and unicore use these extensions. 

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:

View raw message