Philip Zampino created KNOX-2530:
------------------------------------
Summary: 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
Fix For: 1.6.0
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)
