You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2015/04/09 20:37:12 UTC

[jira] [Assigned] (AIRAVATA-1637) Multiplex Airavata API based on functional categories

     [ https://issues.apache.org/jira/browse/AIRAVATA-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suresh Marru reassigned AIRAVATA-1637:
--------------------------------------

    Assignee: Suresh Marru

> Multiplex Airavata API based on functional categories 
> ------------------------------------------------------
>
>                 Key: AIRAVATA-1637
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-1637
>             Project: Airavata
>          Issue Type: Epic
>            Reporter: Suresh Marru
>            Assignee: Suresh Marru
>             Fix For: 0.16
>
>
> Airavata API has become monolithic. More over, different category of API's have different usage rate and targeted for different roles. 
> Since we do not have good way to demarcate the API, please post suggestions. To help the discussion, here is a first draft:
> gateway-management
> credential-management
> appcatalog
> application-execution
> workflow-execution
> data-management 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)