airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marlon Pierce <marpi...@iu.edu>
Subject Re: Summary Re: Hangout: Orchestrator, Registry, GFAC, and API recap and plans
Date Tue, 04 Feb 2014 13:55:12 GMT
Please see the Thrift definitions in modules/thrift-interfaces.


Marlon

On 2/3/14 11:14 PM, Nipun Udara wrote:
> Hi Suresh,
>
> Can you let me know what are the new data model Objects defined in API that
> mentioned above. Thank you
>
> Regards
>
>
> On Tue, Feb 4, 2014 at 1:32 AM, Suresh Marru <smarru@apache.org> wrote:
>
>> Thanks Marlon for a comprehensive yet concise summary.
>>
>> For the API Server, how about Airavata API Facade - drawing from
>> http://en.wikipedia.org/wiki/Facade_pattern
>>
>> This does not make a good acronym either. So better suggestions will be
>> great.
>>
>> Suresh
>>
>> On Feb 3, 2014, at 2:54 PM, Marlon Pierce <marpierc@iu.edu> wrote:
>>
>>> The following will be associated with specific Jira tasks. Here is the
>>> summary:
>>>
>>> * Suresh is done with the Thrift API for now, ready from critical
>> feedback.
>>> * Registry needs to implement the data model objects defined in Suresh's
>>> API and map these to database schema and OpenJPA.
>>>
>>> * Registry needs to define its Component Programming Interface (CPI).
>>> Ideally, this will be just "get" and "set" methods associated with
>>> Thrift-defined data model objects.
>>>
>>> * Orchestrator and GFAC components both also need CPIs. CPIs are Java
>>> interfaces with ".cpi." in the name space.  This is refactoring current
>>> code for the most part.
>>>
>>> * While waiting on the Registry changes, we need to evaluate the Thrift
>>> data models from the point of view of the Orchestrator and GFAC.
>>>
>>> * We also need to evaluate the Thrift API from the point of view of
>>> external gateways.
>>>
>>> * We will need to implement and test the Airavata API Server (or AAS, to
>>> give it a name and abbreviation). This is the Thrift server that maps
>>> API methods to CPI calls.  External gateways call the API.  The AAS maps
>>> these calls to the internal CPI invocations (to the Registry or
>>> Orchestrator).
>>>
>>> We also will need to do steps for the Workflow Interpreter but this will
>>> be discussed more later.
>>>
>>>
>>> Marlon
>>>
>>>
>>> On 2/3/14 1:04 PM, Marlon Pierce wrote:
>>>> Hangout URL is
>>>> https://plus.google.com/hangouts/_/72cpjvt6sl94fnn4hs10bibi6g?hl=en
>>>>
>>>>
>>>> Marlon
>>>>
>>>> On 2/3/14 9:14 AM, Marlon Pierce wrote:
>>>>> Hi all--
>>>>>
>>>>> We'll have a hangout at 1:00 pm US EST to discuss the subject.  Hangout
>>>>> URL will be forthcoming.
>>>>>
>>>>>
>>>>> Marlon
>>>>>
>>


Mime
View raw message