[
https://issues.apache.org/jira/browse/KNOX-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170742#comment-16170742
]
Phil Zampino commented on KNOX-1014:
------------------------------------
[~lmccay]
1. This had crossed my mind, and I even implemented something along these lines
in the POC, but I wanted to give that some more thought. I agree that a
follow-up jira to address this would be appropriate.
2. Are you suggesting something like... knoxcli.sh create-alias
ambari-discovery-credentials --value 'admin:admin' , and then have a
discovery-credentials-alias in the descriptor referencing that alias, rather
than discovery-user?
3. The topology will not be generated if we can't determine a url for a
declared service.
4. This is effectively the same as #3, at least in terms of the resulting
behavior.
> Service Discovery and Topology Generation Framework
> ---------------------------------------------------
>
> Key: KNOX-1014
> URL: https://issues.apache.org/jira/browse/KNOX-1014
> Project: Apache Knox
> Issue Type: Sub-task
> Components: Server
> Reporter: Phil Zampino
> Assignee: Phil Zampino
> Labels: kip-8
> Fix For: 0.14.0
>
> Attachments: KNOX-1014.patch
>
>
> Implement the foundation for Service Discovery and Topology Generation.
> * Define simple descriptor format (YAML, JSON, etc...)
> * Local simple descriptor and shared provider configuration discovery
> ** Monitor conf/shared-providers, conf/descriptors similar to the way
> conf/topologies is currently monitored.
> * Ambari service discovery (REST API interactions and model construction)
> ** Configuration
> *** How to plug-in discovery implementations
> *** How to configure authentication (credentials/trust) with the service
> registries
> * Topology assembly from simple descriptor and discovery details
> * Topology deployment
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
