[
https://issues.apache.org/jira/browse/AIRAVATA-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398781#comment-13398781
]
Saminda Wijeratne commented on AIRAVATA-484:
--------------------------------------------
Current Impl plan...
AiravataClient will be reintroduced through an Interface called AiravataAPI
AiravataAPI will have the following managers,
: AiravataManager - functions to retrieve Airavata related metadata
information such as the gfac url, msgbox url etc.
: ApplicationManager - functions to manage application/service/host
descriptors
: WorkflowManager - functions to manage workflows (retrieve/save/launch)
: ProvenanceManager - functions to manage workflow execution data
: UserManager - functions to manage users in airavata system (not yet
planned fully)
Right now we wont expose the Registry API through the AiravataAPI since there
is no requirement for the user to interact with the registry which is not
covered by the above managers.
> Airavata API improvements
> -------------------------
>
> Key: AIRAVATA-484
> URL: https://issues.apache.org/jira/browse/AIRAVATA-484
> Project: Airavata
> Issue Type: Improvement
> Components: Airavata Client
> Affects Versions: 0.2-INCUBATING
> Environment: Current Airavata API eventhough has the capability
> perform all Airavata operations the API functions are not properly organized.
> They should be organized in a intuitive and less hassle for gateway
> developers.
> Reporter: Saminda Wijeratne
> Assignee: Saminda Wijeratne
> Fix For: 0.4-INCUBATING
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
