You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Sandor Molnar (Jira)" <ji...@apache.org> on 2020/01/21 16:42:00 UTC
[jira] [Created] (KNOX-2190) Cloudera Manager integration - advance
service discovery handling on topology level
Sandor Molnar created KNOX-2190:
-----------------------------------
Summary: Cloudera Manager integration - advance service discovery handling on topology level
Key: KNOX-2190
URL: https://issues.apache.org/jira/browse/KNOX-2190
Project: Apache Knox
Issue Type: New Feature
Components: Server
Affects Versions: 1.4.0
Reporter: Sandor Molnar
Assignee: Sandor Molnar
Fix For: 1.4.0
With KNOX-2186, Knox is capable of processing a properties file ({{auto-discovery-advanced-configuration.properties}}) which CM generates with a list of boolean flags of enabled services. These boolean flags are valid to all descriptors (topologies) within all topologies listed in {{gateway.auto.discovery.expected.topology.names}}.
It'd be beneficial to refine this behavior the following way:
- the monitor would handle different properties file with {{auto-discovery-advanced-configuration}} file name prefix (it's also recommended that whoever generates these files the file name suffix would be the topology name. For instance: {{auto-discovery-advanced-configuration-topology1.properties}}).
- a new property should be introduced in each property file: {{gateway.auto.discovery.topology.name}} to indicate the topology name (to not to rely on the file name suffix)
- keep the existing list of boolean flags of service enablement
- the existing {{gateway.auto.discovery.expected.topology.names}} property should be removed (it's no longer useful)
The monitor then builds a map of properties where the key is the topology name and the value is a list of boolean flags (if service X is enabled or not) and notifies all \{{AdvancedServiceDiscoveryConfigChangeListener}}s when a change is detected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)