ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <>
Subject [jira] [Updated] (AMBARI-7469) Add Visibility Attributes to Services
Date Mon, 24 Aug 2015 22:35:46 GMT


Yusaku Sako updated AMBARI-7469:
    Assignee: Sebastian Toader

> Add Visibility Attributes to Services
> -------------------------------------
>                 Key: AMBARI-7469
>                 URL:
>             Project: Ambari
>          Issue Type: Epic
>          Components: ambari-web, stacks
>    Affects Versions: 1.7.0
>            Reporter: Robert Levas
>            Assignee: Sebastian Toader
>              Labels: installation, service, ui, visibility
>         Attachments: AMBARI-7469.patch, AmbariServiceVisibility.pdf
> *Problem*
> In a stack there may be one or more services that should not be installable, configurable,
or managed via the Ambari web-based interface.  Such a service may need to be installed via
some Ambari API call or manually. There is no way to specify these “visibility” attributes
within a service’s definition; thus to “hide” a service, one-off code needs to be added
to the different Ambari facilities.
> *Solution*
> Add visibility attributes to service definitions to describe how Ambari should expose
services via front-end facilities.   The following Boolean attributes should be settable by
> * installable
> ** indicates if Ambari can install the service - if not installable, the service should
be hidden from “add service” features of Ambari
> * managed
> ** indicates if Ambari can start and stop the service - if not managed, the service should
be hidden from all views where management operations can occur
> * monitored
> ** indicates if Ambari can monitor the service - if not monitored, status information
should not be displayed

This message was sent by Atlassian JIRA

View raw message