[AMBARI-7469] Add Visibility Attributes to Services

• Type: Epic
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.0
• Fix Version/s: 2.3.0
• Component/s: ambari-web, stacks
• Labels: installation service ui visibility
• Epic Name: Ambari Service Visibility
• Assignee: Sebastian Toader
• Reporter: Robert Levas
• Created: 24/Sep/14 15:33
• Updated: 02/Oct/15 01:00
• Resolved: 01/Oct/15 22:01

Description

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

Issue Links

• links to: ReviewBoard