[ 
https://issues.apache.org/jira/browse/KNOX-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Phil Zampino updated KNOX-1911:
-------------------------------
    Description: 
The Discovery Details part of the descriptor authoring / editing facilities in 
the Admin UI assume Ambari-based discovery. As such, there is currently no way 
to specify the discovery type.

The Discovery Details UI should include a drop-down based on the available 
supported discovery implementations. Ideally, this will be dynamically 
populated (via the service loader facility, or an API that depends on it?), 
rather than a static list.

It also should be possible to exclude any discovery configuration from the 
associated descriptor.
 A _no discovery_ option should be included in the drop-down list of discovery 
types.

 

  was:
The Discovery Details part of the descriptor authoring / editing facilities in 
the Admin UI assume Ambari-based discovery. As such, there is currently no way 
to specify the discovery type.

The Discovery Details UI should include a drop-down based on the available 
supported discovery implementations.

It also should be possible to exclude any discovery configuration from the 
associated descriptor.
A _no discovery_ option should be included in the drop-down list of discovery 
types.

 


> Support ClouderManager Service Discovery in Admin UI
> ----------------------------------------------------
>
>                 Key: KNOX-1911
>                 URL: https://issues.apache.org/jira/browse/KNOX-1911
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: AdminUI
>    Affects Versions: 1.3.0
>            Reporter: Phil Zampino
>            Priority: Major
>
> The Discovery Details part of the descriptor authoring / editing facilities 
> in the Admin UI assume Ambari-based discovery. As such, there is currently no 
> way to specify the discovery type.
> The Discovery Details UI should include a drop-down based on the available 
> supported discovery implementations. Ideally, this will be dynamically 
> populated (via the service loader facility, or an API that depends on it?), 
> rather than a static list.
> It also should be possible to exclude any discovery configuration from the 
> associated descriptor.
>  A _no discovery_ option should be included in the drop-down list of 
> discovery types.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to