[
https://issues.apache.org/jira/browse/AIRAVATA-991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915027#comment-13915027
]
Chathuri Wimalasena commented on AIRAVATA-991:
----------------------------------------------
Hi Suresh,
Currently we have data models inside airavata-api-stubs and
airavata-data-models which leads to redundancy and confusion. From airavata
components, we use data models inside airavata-data-models project. Instead of
having two places, can we have all the generated data models in
airavata-data-models ?
> Craft the Airavata 1.0 API
> --------------------------
>
> Key: AIRAVATA-991
> URL: https://issues.apache.org/jira/browse/AIRAVATA-991
> Project: Airavata
> Issue Type: Story
> 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)
