[
https://issues.apache.org/jira/browse/KNOX-2530?focusedWorklogId=539826&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-539826
]
ASF GitHub Bot logged work on KNOX-2530:
----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Jan/21 06:22
Start Date: 22/Jan/21 06:22
Worklog Time Spent: 10m
Work Description: pzampino opened a new pull request #398:
URL: https://github.com/apache/knox/pull/398
## What changes were proposed in this pull request?
In the case of some services, or specific deployments of those services,
there exists the need to direct the discovery process for topology generation.
One example is HA HDFS deployments, where a particular nameservice can be
desired to be proxied. Another example is multiple Solr instances within the
same cluster, where one should be proxied but not the other(s).
This change introduces for Cloudera Manager discovery the concept of
discovery-time-only service parameters in simple descriptors. This is already
supported by Amabari service discovery for the aforementioned HDFS HA scenario,
and the same pattern is being applied and extended for Cloudera Manager.
Service parameters beginning with "discovery-" can be declared for supported
services in simple descriptors. The actual names of the parameters are
service-specific.
This is an example for the HDFS nameservice selection:
`"services": [
{
"name": "WEBHDFS",
"params": {
"discovery-nameservice": "ns2"
}
},`
## How was this patch tested?
Manual testing, augmented/modified unit tests for the affected
ServiceModelGenerator implementations.
----------------------------------------------------------------
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: 539826)
Time Spent: 1h 10m (was: 1h)
> 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: 1h 10m
> 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)
