[
https://issues.apache.org/jira/browse/KNOX-2530?focusedWorklogId=539132&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-539132
]
ASF GitHub Bot logged work on KNOX-2530:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Jan/21 15:25
Start Date: 21/Jan/21 15:25
Worklog Time Spent: 10m
Work Description: pzampino commented on a change in pull request #398:
URL: https://github.com/apache/knox/pull/398#discussion_r561968345
##########
File path:
gateway-discovery-cm/src/main/java/org/apache/knox/gateway/topology/discovery/cm/ServiceModel.java
##########
@@ -37,6 +37,9 @@
private final String roleType;
private final String serviceUrl;
+ // Metadata for the model object, which is not directly from the service or
role configuration
+ private final Map<String, String> modelProperties = new
ConcurrentHashMap<>();
Review comment:
New PS in progress...
----------------------------------------------------------------
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: 539132)
Time Spent: 50m (was: 40m)
> Support qualifying service params for CM discovery control
> ----------------------------------------------------------
>
> Key: KNOX-2530
> URL: https://issues.apache.org/jira/browse/KNOX-2530
> Project: Apache Knox
> Issue Type: Improvement
> Components: cm-discovery
> Affects Versions: 1.5.0
> Reporter: Philip Zampino
> Assignee: Philip Zampino
> Priority: Major
> Fix For: 1.6.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Add support for discovery-only service params in descriptor service
> declarations, such that the ClouderaManager discovery process can be
> controlled for HA and other deployments where there are multiple sources of
> endpoint information that should not be combined for a given topology.
> One example is HDFS HA, where a nameservice can be specified. (Similar
> support for this exists for Ambari discovery)
> {noformat}
> {
> "discovery-type":"ClouderaManager",
> "discovery-address":"https://cm-host:7183";,
> "discovery-user":"admin",
> "discovery-pwd-alias":"cm.discovery.pwd",
> "provider-config-ref":"pam",
> "cluster":"Cluster 1",
> "services":[
> {
> "name":"WEBHDFS",
> "params": {
> "discovery-nameservice":"ns2"
> }
> }
> ]
> }{noformat}
> Another example is a cluster with multiple SOLR instances.
> {noformat}
> {
> "discovery-type":"ClouderaManager",
> "discovery-address":"https://cm-host:7183";,
> "discovery-user":"admin",
> "discovery-pwd-alias":"cm.discovery.pwd",
> "provider-config-ref":"pam",
> "cluster":"Cluster 1",
> "services":[
> {
> "name":"SOLR",
> "params": {
> "discovery-service-display-name":"SOLR-1"
> }
> }
> ]
> }{noformat}
> These discovery-only service parameters are prefixed with *discovery-*, and
> must not manifest in the generated topologies.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
