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

Suresh Marru commented on AIRAVATA-991:
---------------------------------------

To keep the API manageable, we can continue to build upon the current 
functional grouping with minor enhancements. A draft suggestion is to include 
the following api blocks:

Airavata Configuration Management: Provides access to client queriable Airavata 
configuration data.

Airavata Application and Workflow Catalog: API functions register and manage 
application interfaces, deployment descriptions and workflow definitions.  

Execution Management: API functions to create, configure, launch and terminate 
experiments. 

Monitoring and Messaging: Provide ability to Monitor execution progress in near 
real-time using pub-sub and poll based approaches. 

Data Management: API functions to retrieve experiment generated metadata, 
provenance information and actual data of the experiments.

Please comment to help refine these. We can create subtasks to has these 
individual blocks and craft the data models. 

> Craft the Airavata 1.0 API
> --------------------------
>
>                 Key: AIRAVATA-991
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-991
>             Project: Airavata
>          Issue Type: New Feature
>          Components: Airavata API
>    Affects Versions: 0.11
>            Reporter: Suresh Marru
>            Assignee: Suresh Marru
>             Fix For: 1.0
>
>
> An important goal for Airavata 1.0 release is to draft a public facing API 
> which  includes subset of functionality exposed by the internal SPI and 
> higher level functions which can be realized by one of more internal 
> components. 
> Airavata clients have to be abstracted from internal component level details 
> and would like to interact through API through higher order method. Some of 
> the capabilities include abilities to Register gateways, computational 
> credentials, register and manage applications, create, configure and launch 
> experiments (binding them to applications/workflows), monitor real-time and 
> poll based progress, query for generated data and analyze results. 
> These capabilities can be realized by one or more internal Airavata 
> components and the API layers abstracts these out and maps appropriately. 



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to