You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Marlon Pierce (Created) (JIRA)" <ji...@apache.org> on 2012/03/12 15:44:42 UTC
[jira] [Created] (AIRAVATA-341) NoSQL implementation for Airavata
Registry
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
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AIRAVATA-341) [GSOC] NoSQL implementation for
Airavata Registry
Posted by "Marlon Pierce (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marlon Pierce updated AIRAVATA-341:
-----------------------------------
Summary: [GSOC] NoSQL implementation for Airavata Registry (was: NoSQL implementation for Airavata Registry)
> [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, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AIRAVATA-341) [GSOC] NoSQL implementation for
Airavata Registry
Posted by "Suresh Marru (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248245#comment-13248245 ]
Suresh Marru commented on AIRAVATA-341:
---------------------------------------
Suresh April 6, 2012, 4:38 a.m.
Hi Sumedha,
Very well written proposals. Few comments
I think a good value add will be also to consider a web component to your proposed API, so you can provide registry browsing/searching capabilities. It may be outside the scope of the proposed project but a thought.
Since you need to validate all the currently supported features wil be preserved in the NoSQL implementation, you should engage with the airavata dev community providing good sampels and test cases so you can validate it with your enhancements.
Good luck with the project,
Suresh
Sumedha Kodithuwakku April 6, 2012, 6:51 a.m.
Hi Suresh,
Thanks for the feed back.
Actually I was hoping to implement a simple GUI which can provide the functionalities you have mentioned. Also to improve it with the ability to modify the data in the registry, for example to modify formulas in a computational chemistry use case. Also features of the proposed registry such as searching capabilities and imposing access policies can be done though the GUI easily.
But I was not sure about including it in this proposal becasue as I feel It has to be done after completing the initial project which is to implement the registry completely. My plan was to implemet the registry as the GSoC project and then implement the GUI. So I will be able to concentrate more on implementing the core functionalities of the registgry during the GSoC period and then after that complete the GUI focusing only on it so that it can be made more powerful. Also while doing this I will be able to polish the registry more.
So please let me know whether I should add it as a task in the proposal or do it as I said earlier.
Also I was hoping to pay more attention to documentation because as I feel current registry implementation side is lacking documentation (I searched a lot about the current registry implemetation of Airavata but I couldn't find enough documentation regarding it. So I had to look in to the code which is bit tough for a new commer as I feel. Please point me, if there are documentations related toregistry other that those which are available in the Airavata site). So I thought of writing a comprehensive documentation related to the proposed registry. Please let me know your opinoins on this.
Thanks.
Suresh April 6, 2012, 11:37 a.m.
Hi Sumedha,
All of what you say sounds good. You are the right track. These GUI and search interface is outside the scope of the project and its encouraging to hear you are not only planning on the project itself, but how and what to contribute beyond the project. You have enough development tasks within the scope of the project itself, so you are good for now. A big + 1 for your thinking on not just docuemnting your nosql additions but entire registry. Airavata community will be pleased and also be will help you understand the details and possibly assist you with this additional task.
Suresh
> [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, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AIRAVATA-341) [GSOC] NoSQL implementation for
Airavata Registry
Posted by "Suresh Marru (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Marru updated AIRAVATA-341:
----------------------------------
Labels: gsoc gsoc2012 mentor (was: gsoc mentor)
> [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, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AIRAVATA-341) [GSOC] NoSQL implementation for
Airavata Registry
Posted by "Sumedha Kodithuwakku (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243064#comment-13243064 ]
Sumedha Kodithuwakku commented on AIRAVATA-341:
-----------------------------------------------
I did some background studies on Airavata and also went through the registry API and the AiravataClient roughly as suggested by Marlon in dev-list. So I have few things to clarify about implementation of this new feature.
As I understood Apache Jackrabbit is used as the content repository and it is accessed via the JCR API. As per the discussion with Marlon, the main goal of this project is to replace the storing mechanism with a NoSQL solution. I'm not clear whether the project is to replace the whole Jackrabbit implementation with a NoSQL based implementation which can be accessed through the JCR API or to implement a NoSQL storage mechanism replacing the current storage mechanism inside Jackrabbit. Please can someone clarify on this.
Also It would be appreciated if I can know some more details on what will be expected from the project and the initial requirements.
> [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, 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira