You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Imesha Sudasingha (JIRA)" <ji...@apache.org> on 2017/03/11 15:37:04 UTC

[jira] [Comment Edited] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management

    [ https://issues.apache.org/jira/browse/OODT-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15906204#comment-15906204 ] 

Imesha Sudasingha edited comment on OODT-945 at 3/11/17 3:36 PM:
-----------------------------------------------------------------

I am a final year student of University of Moratuwa, Sri Lanka. Since I have a strong background in Apache Zookeeper, I think I will be able to complete this task for GSoC 2017. In order to do that, I want to know few things about this project.

* The task is to store configuration of each component under a Zookeeper namespace in a unique ZNode (say {{/{$namespace}/{$componentName}}})?
* A suitable architecture for this configuration management has to be introduced?
* Can we use Apache Curator as the client?

Thanks in advance!


was (Author: imesha):
I am a final year student of University of Moratuwa, Sri Lanka. I want to know few things about this project.

* The task is to store configuration of each component under a Zookeeper namespace in a unique ZNode (say {{/{$namespace}/{$componentName}}})?
* A suitable architecture for this configuration management has to be introduced?
* Can we use Apache Curator as the client?

Thanks in advance!

> Rework OODT configuration to make use of  Zookeeper for distributed configuration management
> --------------------------------------------------------------------------------------------
>
>                 Key: OODT-945
>                 URL: https://issues.apache.org/jira/browse/OODT-945
>             Project: OODT
>          Issue Type: Bug
>            Reporter: Tom Barber
>            Assignee: Tom Barber
>              Labels: gsoc2017, mentor
>
> OODT is made up of a number of different components, each of which have their own set of configuration files and locations. This is complex to manage and causes additional problems when the platform requires distribution across servers or geographically.
> To combat this we are proposing that we migrate the OODT configuration to an opional Zookeeper module that would allow users to commission a zookeeper cluster and register the various OODT components against it, which will allow the zookeeper cluster to maintain the state of the various OODT components regardless of scale.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)