[
https://issues.apache.org/jira/browse/AMBARI-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804345#comment-14804345
]
Hadoop QA commented on AMBARI-7469:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12757109/AMBARI-7469.v3.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 5 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The test build failed in ambari-server
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/3803//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3803//console
This message is automatically generated.
> 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
> Assignee: Sebastian Toader
> Labels: installation, service, ui, visibility
> Attachments: AMBARI-7469.patch, AMBARI-7469.v1.patch,
> AMBARI-7469.v2.patch, AMBARI-7469.v3.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 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)
