[
https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267126#comment-16267126
]
ASF subversion and git services commented on KNOX-1107:
-------------------------------------------------------
Commit b5caf182387e05d36c96cd375956c5be6c979a4d in knox's branch
refs/heads/v0.14.0 from [~lmccay]
[ https://git-wip-us.apache.org/repos/asf?p=knox.git;h=b5caf18 ]
KNOX-1107 - Remote Configuration Registry Client Service (Phil Zampino via
lmccay)
> Remote Configuration Registry Client Service
> --------------------------------------------
>
> Key: KNOX-1107
> URL: https://issues.apache.org/jira/browse/KNOX-1107
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Affects Versions: 0.15.0
> Reporter: Phil Zampino
> Assignee: Phil Zampino
> Labels: kip-8
> Fix For: 0.14.0
>
> Attachments: KNOX-1107.001.patch, KNOX-1107.patch,
> testing-remote-zk-config-monitoring.txt, zkupload.sh
>
>
> There are currently multiple ZooKeeper clients in Knox, in the form of HA
> provider URL managers.
> These clients have been added to Knox independently, each without concern for
> the other. KNOX-1010 introduces yet another such client.
> In order to manage the configuration of these clients, it would be good to
> have a Client Service, from which these features can retrieve a ZooKeeper
> client.
> Furthermore, in the future, Knox may support additional configuration
> registries (e.g., consul, etcd), which these features may wish to employ. If
> this service is abstracted sufficiently, the underlying registry type can be
> a simple configuration change.
> In addition to managing security configuration for these clients, the service
> may also be able to enforce some ACL constraints on referenced znodes (or
> other registry entries) to mitigate the consumption of potentially untrusted
> configuration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
