airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-1304) App Catalog Improvements beyond phase 1
Date Thu, 03 Jul 2014 18:39:34 GMT


Suresh Marru commented on AIRAVATA-1304:

* One other improvement suggested by [~samindaw]: Some of the fields in app catalog structures
can be improved by adding a Map of a Key associated value. Example, gateway profile resources
preferences could be improved. Current good example will be compute resource file systems.

> App Catalog Improvements beyond phase 1
> ---------------------------------------
>                 Key: AIRAVATA-1304
>                 URL:
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: Application Catalog
>            Reporter: Suresh Marru
> Current description of Airavata APP Catalog is a start. Following are the usecases to
consider for future revision:
> * Inferred Inputs: Some inputs may be needed by the application but not directly obtained
from users but provided by Airavata. EX (Ultrascan): Number of process passed to application
post scheduling. 
> * Optional Inputs: Application will be able to run without these parameters. If present
will be used, if not can be ignored. Example: Paramchem,  LEAD Data Assimilation can run with
varied of inputs increasing the quality. 

This message was sent by Atlassian JIRA

View raw message