You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Nipun Udara (JIRA)" <ji...@apache.org> on 2014/01/30 14:24:08 UTC
[jira] [Comment Edited] (AIRAVATA-341) [GSOC] NoSQL implementation
for Airavata Registry
[ https://issues.apache.org/jira/browse/AIRAVATA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885811#comment-13885811 ]
Nipun Udara edited comment on AIRAVATA-341 at 1/30/14 1:23 PM:
---------------------------------------------------------------
I am interested about this project and According to What i understood so far, Airavata registry is a common component used by Xbaya , GFac , Orchestrator to store and retrieve data such as service information, workflow metadata and workflow consumed input and generated outputs. The Airavata specific registry API is build over the generic JCR API layer which is used to store/retrieve data from the content repository.
The goal of this project is to replace the sql implementation with NoSql implementation such as Cassandra which can provide linear, scalable , large profile database which can handle high volume of simultaneous read/write requests without running into table locking while preserving the currently supporting feathers of the Airavata registry.
I would be grateful if you can clarify more about the requirements of this project.
was (Author: udara):
I am interested about this project and According to What i understood so far, Airavata registry is a common component used by Xbaya , GFac , Orchestrator to store and retrieve data such as service information, workflow metadata and workflow consumed input and generated outputs. The Airavata specific registry API is build over the generic JCR API layer which is used to store/retrieve data from the Jackrabbit content repository.
The goal of this project is to replace the jackrabbit implementation with NoSql implementation such as Cassandra which can provide linear, scalable , large profile database which can handle high volume of simultaneous read/write requests without running into table locking while preserving the currently supporting feathers of the Airavata registry.
I would be grateful if you can clarify more about the requirements of this project.
> [GSOC] NoSQL implementation for Airavata Registry
> -------------------------------------------------
>
> Key: AIRAVATA-341
> URL: https://issues.apache.org/jira/browse/AIRAVATA-341
> 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
(v6.1.5#6160)