Reorganize Application Schema to make it extendable.
-----------------------------------------------------
Key: AIRAVATA-161
URL: https://issues.apache.org/jira/browse/AIRAVATA-161
Project: Airavata
Issue Type: Improvement
Components: GFac, XBaya
Reporter: 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 it.
* 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
