ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7469) Add Visibility Attributes to Services
Date Tue, 25 Aug 2015 02:08:46 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-7469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14710442#comment-14710442
] 

Hadoop QA commented on AMBARI-7469:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12752011/AMBARI-7469.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:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/3634//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/3634//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, 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)

Mime
View raw message