airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marlon Pierce (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-341) [GSOC] NoSQL implementation for Airavata Registry
Date Thu, 30 Jan 2014 14:48:08 GMT


Marlon Pierce commented on AIRAVATA-341:

Hi Nipun--

Thanks for your interest.  The registry has changed a lot since this GSOC ticket was originally
posted in 2012.  We replaced the JCR system with a relational database approach and OpenJPA.
 Please only trust what you read in the code itself.

The registry is a critical piece of code in our work to get to Airavata API 1.0 (see the Jira
entry Airavata-1000), since it will host the data objects we are defining in Thrift.  This
will still be based on OpenJPA+Relational DB for the time being, but it is also probably a
great match for NoSQL DBs that act as object stores.  

If you are interested in this GSOC, I recommend following the Airavata API 1.0 discussion
closely and watch also for changes in the current registry.  Feel free to contact the dev
list, too, if you have questions or comments. 

> [GSOC] NoSQL implementation for Airavata Registry
> -------------------------------------------------
>                 Key: AIRAVATA-341
>                 URL:
>             Project: Airavata
>          Issue Type: New Feature
>            Reporter: Marlon Pierce
>            Assignee: Marlon Pierce
>            Priority: Minor
>              Labels: gsoc, gsoc2012, gsoc2014, mentor
> Airavata's Registry is used to store and retrieve services and workflows. The Registry
is currently very lightweight with an implementation based on Apache Jackrabbit. This task
is to develop a more powerful registry capable of handling a wider variety of use cases and
science gateway metadata.  Issues include development of JSON metadata models for different
use cases, development and evaluation of metadata search capabilities (both expressiveness
and performance), and development and evaluation of access policies for the metadata.  The
latter may involve integration with Apache Rave as an OpenSocial engine for defining groups
and filtering requests.  
> Evaluating the capabilities of multiple NoSQL databases will be an important component
of this task. Candidate technologies from Apache include Cassandra and CouchDB, but appropriately
licensed non-Apache projects such as MongoDB will also be evaluated. 
> Sample use case scenarios will include computational chemistry, material science, astronomy,
and earth science.

This message was sent by Atlassian JIRA

View raw message