[
https://issues.apache.org/jira/browse/AIRAVATA-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13930558#comment-13930558
]
ASF subversion and git services commented on AIRAVATA-1006:
-----------------------------------------------------------
Commit 44ec4d31566fb2bab2f0b8c03bfa4af7e75f8287 in airavata's branch
refs/heads/master from chathuri
[ https://git-wip-us.apache.org/repos/asf?p=airavata.git;h=44ec4d3 ]
adding project data to cpi - AIRAVATA-991, AIRAVATA-1006
> Craft the Registry 1.0 CPI
> --------------------------
>
> Key: AIRAVATA-1006
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1006
> Project: Airavata
> Issue Type: Sub-task
> Reporter: Suresh Marru
> Fix For: 0.12
>
>
> As the Airavata API is evolving towards 1.0 version, we need to refine the
> currently Registry API (and the current Airavata Client->Registry API) into a
> unified and well defined Registry CPI.
> This registry CPI is targeted to be invoked by the Airavata API functions and
> use of Registry by all internal Airavata internal components like
> Orchestrator, Workflow Interpreter and GFac.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
