[
https://issues.apache.org/jira/browse/KNOX-1014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163630#comment-16163630
]
Larry McCay commented on KNOX-1014:
-----------------------------------
[~pzampino] - this is looking really good!
bq. If you delete a shared provider configuration, any referencing descriptors
(and associated topology files) will also be deleted, and the topologies will
be undeployed.
This should probably be changed such that you cannot delete a provider config
through the admin API that is actively referenced by topologies.
If someone deletes it at the OS level from the filesystem let's leave the
referencing topologies and let them fail to deploy. Let's make sure that the
logged deployment or topology generation failures have meaningful messages.
> 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)
