[jira] [Updated] (KNOX-1107) Remote Configuration Registry Client Service
[ https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Risden updated KNOX-1107: --- Affects Version/s: (was: 0.15.0) 0.14.0 > 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.14.0 >Reporter: Phil Zampino >Assignee: Phil Zampino >Priority: Major > 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 (v7.6.3#76005)
[jira] [Updated] (KNOX-1107) Remote Configuration Registry Client Service
[ https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay updated KNOX-1107: -- Resolution: Fixed Status: Resolved (was: Patch Available) > 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)
[jira] [Updated] (KNOX-1107) Remote Configuration Registry Client Service
[ https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay updated KNOX-1107: -- Fix Version/s: (was: 0.15.0) 0.14.0 > 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)
[jira] [Updated] (KNOX-1107) Remote Configuration Registry Client Service
[ https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino updated KNOX-1107: --- Attachment: KNOX-1107.001.patch Removed lingering znode notification listeners, and added the RemoteConfigurationRegistryClientService to the CLI GatewayServices. > 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.15.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)
[jira] [Updated] (KNOX-1107) Remote Configuration Registry Client Service
[ https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino updated KNOX-1107: --- Attachment: zkupload.sh > 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.15.0 > > Attachments: 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)
[jira] [Updated] (KNOX-1107) Remote Configuration Registry Client Service
[ https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino updated KNOX-1107: --- Status: Patch Available (was: In Progress) > 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.15.0 > > Attachments: KNOX-1107.patch, testing-remote-zk-config-monitoring.txt > > > 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)
[jira] [Updated] (KNOX-1107) Remote Configuration Registry Client Service
[ https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino updated KNOX-1107: --- Attachment: KNOX-1107.patch testing-remote-zk-config-monitoring.txt The attached patch includes the remote registry client service and the default remote configuration monitor (i.e., KNOX-1010). The default monitor is included in this patch because it is not really a ZooKeeper-specific monitor any longer since it uses this new client service. The configuration of the client is what makes it ZooKeeper-specific. As such, I'm including it in this patch, and the tests include configuration that exercises the interactions with ZooKeeper. I've attached some instructions for testing both unsecured and secured clients. > 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.15.0 > > Attachments: KNOX-1107.patch, testing-remote-zk-config-monitoring.txt > > > 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)
[jira] [Updated] (KNOX-1107) Remote Configuration Registry Client Service
[ https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay updated KNOX-1107: -- Fix Version/s: 0.15.0 > 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.15.0 > > > 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)
[jira] [Updated] (KNOX-1107) Remote Configuration Registry Client Service
[ https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino updated KNOX-1107: --- Description: 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. was: 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 untrusted configuration. > 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 > > 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)
[jira] [Updated] (KNOX-1107) Remote Configuration Registry Client Service
[ https://issues.apache.org/jira/browse/KNOX-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Zampino updated KNOX-1107: --- Description: 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 untrusted configuration. was: There are currently multiple ZooKeeper clients in Knox, in the form of HA provider URL managers. These clients has 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 untrusted configuration. > 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 > > 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 untrusted > configuration. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
