[
https://issues.apache.org/jira/browse/KNOX-1013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152017#comment-16152017
]
Larry McCay commented on KNOX-1013:
-----------------------------------
[~risdenk] - Your concern is well founded. This however is a scenario related
to KIP-8 where Ambari is the source for service discovery rather than the
management platform that is pushing out all the config details. By allowing
Knox to pull the relevant URLs and HA metadata from a service registry
abstraction, we can have much simpler topology descriptors. Admins would only
need to indicate which services they want in a topology and the rest will be
pulled from the service registry. In this case, the Ambari REST APIs are used
as the registry. Another source may be ZooKeeper.
So this is in a way simplifying what the Ambari UI needs to do - instead of all
that XML we can have a simple page of services with checkboxes as well as
allowing for the metadata to be pull from other sources if desired.
Give KIP-8 a read and see whether it makes sense to you.
Thank you for raising a concern here!
> Monitor Ambari for Topology changes
> -----------------------------------
>
> Key: KNOX-1013
> URL: https://issues.apache.org/jira/browse/KNOX-1013
> Project: Apache Knox
> Issue Type: Sub-task
> Components: Server
> Reporter: Phil Zampino
> Labels: kip-8
>
> Knox should provide the option to monitor an Ambari cluster for which it has
> deployed a topology, in order to notice configuration changes that affect the
> service URLs for that topology. Upon noticing such a change, Knox should
> respond by updating the deployed topology appropriately.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
