Major Description
With KNOX-2160, Knos is capable of processing a Hadoop XML configuration file and turn its content into Knox providers.
It'd be beneficial to add support for the following use cases that are also Cloudera Manager integration specific:
1.) Cloudera Manager reports if auto-discovery is enabled for each known services. That is, a list of boolean properties can be generated by CM indicating if SERVICE_X is enabled or not in the following form: gateway.auto.discovery.enabled.SERVICE_NAME=[true|false]
The new Hadoop XML configuration parser should take this information into account, and add a certain service into the generated Knox descriptor only if that service is explicitly enabled or there is no boolean flag within the CM generated properties with that service name (indicating an unknown - custom - service).
Additionally, a set of known (expected) topologies can be listed by CM. These topologies (Knox descriptors) should be populated with an enabled service(only with its name) even if that particular service was not listed in the new style Hadoop XML configuration file within the descriptor that matches any of the expected topology names.
2.) There are some services - mainly UI services - that are not working without some more required services in place (mainly their API counterpart). For instance: RANGERUI won't work properly if RANGER is not available.
The new Hadoop XML configuration parser should be modified to not to add any service into the generated Knox descriptor unless
- all required services are available (if any)
- all required services are enabled (see the previous point)
Attachments
Issue Links
- relates to
-
KNOX-2187 Add metadata to service definitions
-
- Resolved
-
- links to
