Robert Levas created AMBARI-7469:
------------------------------------
Summary: Add Visibility Attributes to Services
Key: AMBARI-7469
URL: https://issues.apache.org/jira/browse/AMBARI-7469
Project: Ambari
Issue Type: Epic
Components: ambari-web, stacks
Affects Versions: 1.7.0
Reporter: Robert Levas
Fix For: 2.0.0
*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 services:
* 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
(v6.3.4#6332)