[KNOX-2530] Support qualifying service params for CM discovery control

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.6.0
• Component/s: cm-discovery
• Assignee: Philip Zampino
• Reporter: Philip Zampino
• Created: 15/Jan/21 20:27
• Updated: 22/Jan/21 06:40
• Resolved: 21/Jan/21 18:44

Description

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)

{
  "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"
      }
    }
  ]
}

Another example is a cluster with multiple SOLR instances.

{
  "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"
      }
    }
  ]
}

These discovery-only service parameters are prefixed with discovery-, and must not manifest in the generated topologies.

 

Issue Links

• links to: GitHub Pull Request #398