[
https://issues.apache.org/jira/browse/OODT-945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081487#comment-16081487
]
ASF GitHub Bot commented on OODT-945:
-------------------------------------
Github user IMS94 commented on a diff in the pull request:
https://github.com/apache/oodt/pull/44#discussion_r126577697
--- Diff: README.md ---
@@ -53,8 +50,7 @@ To contribute a patch, follow these instructions (note
that installing
```
-License (see also LICENSE.txt)
-==============================
+## License (see also LICENSE.txt)
--- End diff --
@chrismattmann Sure. But I think you have applied these changes to the
Readme.md with the commit [update
README.md](https://github.com/apache/oodt/commit/1b42cacacfc96e96b69f0c28d7eefcb89ae85856).
Therefore, I will rollback this change
> 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)
