[jira] [Updated] (AMBARI-5401) Service Pluggability for Ambari Web

["Yusaku Sako (JIRA)" <ji...@apache.org>]

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

Yusaku Sako updated AMBARI-5401:
--------------------------------

    Description: 
Ambari Web UI needs work to support service pluggability.

* UI should reflect the stack definition and should not have knowledge about specific services in its core.  This includes which services are available in which stacks, which components belong to which services, which components are masters/slaves/clients, stack/service version-dependent behavior, service/component dependencies, service configs, etc.

* Wherever service-specific UI/UX is needed, these should be defined and loaded as "plugins".  For example, such service-specific UI elements should be defined in the "plugins" directory, which is dynamically loaded at runtime.
We need to separate out the "core" from service-specific "plugins".

Resolution of this JIRA requires the following:
* Services added to a stack or removed from a stack should automatically be reflected in services available to install in Install Wizard and Add Service Wizard.
* All services installed on a cluster should automatically be reflected in the Dashboard, Services, and other Cluster Management and Monitoring pages.
* Service components defined for a service should automatically be reflected in Install/Add Service Wizards.  This includes Assign Master page in Install Wizard and Add Service Wizard.


> Service Pluggability for Ambari Web
> -----------------------------------
>
>                 Key: AMBARI-5401
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5401
>             Project: Ambari
>          Issue Type: Bug
>          Components: client, controller
>    Affects Versions: 1.6.0
>            Reporter: Yusaku Sako
>            Assignee: Yusaku Sako
>             Fix For: 1.6.0
>
>
> Ambari Web UI needs work to support service pluggability.
> * UI should reflect the stack definition and should not have knowledge about specific services in its core.  This includes which services are available in which stacks, which components belong to which services, which components are masters/slaves/clients, stack/service version-dependent behavior, service/component dependencies, service configs, etc.
> * Wherever service-specific UI/UX is needed, these should be defined and loaded as "plugins".  For example, such service-specific UI elements should be defined in the "plugins" directory, which is dynamically loaded at runtime.
> We need to separate out the "core" from service-specific "plugins".
> Resolution of this JIRA requires the following:
> * Services added to a stack or removed from a stack should automatically be reflected in services available to install in Install Wizard and Add Service Wizard.
> * All services installed on a cluster should automatically be reflected in the Dashboard, Services, and other Cluster Management and Monitoring pages.
> * Service components defined for a service should automatically be reflected in Install/Add Service Wizards.  This includes Assign Master page in Install Wizard and Add Service Wizard.



--
This message was sent by Atlassian JIRA
(v6.2#6252)