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

Tom Barber commented on OODT-945:
---------------------------------

Hi [~imesha]

Thanks for asking!

Yeah one of the core plans for OODT 2.0 is to add an option for developers to 
deploy OODT with ZK as the backing config store. This will allow us to scale 
the platform whilst keeping the config manageable and dynamic as components 
come and go in deployments.

In order of the questions asked:

Yes, pretty much, there are lots of OODT components so storing in 
namspace/componentName makes sense
Again, yes, currently the configs for most OODT components are based on Spring 
configs and property files, so it would be a question of reworking these. We'd 
likely start with the File Manager as the first component as its the most 
critical for scale and a good reference implementation
And finally, yes Apache Curator would be fine, simplifying the complexity is 
always good :)

Tom

> 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)

Reply via email to