airavata-dev mailing list archives

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

    [ https://issues.apache.org/jira/browse/AIRAVATA-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14051843#comment-14051843
] 

Suresh Marru commented on AIRAVATA-1304:
----------------------------------------

* monitoring mechanism in compute resource description is currently a string. It needs to
encompass the push/pull and appropriate details associated with these mechanisms. 

> App Catalog Improvements beyond phase 1
> ---------------------------------------
>
>                 Key: AIRAVATA-1304
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1304
>             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
(v6.2#6252)

Mime
View raw message