oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OODT-945) Rework OODT configuration to make use of Zookeeper for distributed configuration management
Date Fri, 14 Jul 2017 14:23:00 GMT

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

ASF GitHub Bot commented on OODT-945:
-------------------------------------

Github user chrismattmann commented on the issue:

    https://github.com/apache/oodt/pull/44
  
    hi @IMS94 do I need to set those env vars? This will screw up tests since they should
not have environment variable requirements, or if so, should be mock'ed in the tests themselves.


> 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.4.14#64029)

Mime
View raw message