[
https://issues.apache.org/jira/browse/KNOX-2190?focusedWorklogId=375532&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-375532
]
ASF GitHub Bot logged work on KNOX-2190:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Jan/20 11:19
Start Date: 22/Jan/20 11:19
Worklog Time Spent: 10m
Work Description: smolnar82 commented on pull request #242: KNOX-2190 -
Processing advanced service discovery configuration on topology level
URL: https://github.com/apache/knox/pull/242
## What changes were proposed in this pull request?
TODO: change description
## How was this patch tested?
JUnit:
```
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 19:24 min (Wall Clock)
[INFO] Finished at: 2020-01-22T11:48:12+01:00
[INFO] Final Memory: 421M/2351M
[INFO]
------------------------------------------------------------------------
```
TODO: Manual testing description
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 375532)
Remaining Estimate: 0h
Time Spent: 10m
> 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
> Priority: Major
> Fix For: 1.4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 files 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}}
> instances when a change is detected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
