[
https://issues.apache.org/jira/browse/AIRAVATA-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13892545#comment-13892545
]
Marlon Pierce commented on AIRAVATA-1006:
-----------------------------------------
I think it is a good starting point. We can provide more specialized, less
abstract methods after we get more integration experience with the
Orchestrator, Interpreter, and GFAC. Probably these methods would just be
wrappers around the general methods above.
I'm assuming a CPI can evolve a lot between releases, unlike the API, and this
is won't have the same data model incompatibilities we need to worry about with
the API.
> 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.1.5#6160)
