Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 18 Sep 2015 16:05:05 +0000 (UTC)
From: "Sebastian Toader (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12743796.1411572791000.13106.1442592305423@Atlassian.JIRA>
In-Reply-To: <JIRA.12743796.1411572791000@Atlassian.JIRA>
References: <JIRA.12743796.1411572791000@Atlassian.JIRA>
 <JIRA.12743796.1411572791380@arcas>
Subject: [jira] [Updated] (AMBARI-7469) Add Visibility Attributes to
 Services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/AMBARI-7469?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebastian Toader updated AMBARI-7469:
-------------------------------------
    Attachment:     (was: AMBARI-7469.v2.patch)

> 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: AmbariServiceVisibility.pdf
>
>
> *Problem*
> In a stack there may be one or more services that should not be installab=
le, configurable, or managed via the Ambari web-based interface.  Such a se=
rvice may need to be installed via some Ambari API call or manually. There =
is no way to specify these =E2=80=9Cvisibility=E2=80=9D attributes within a=
 service=E2=80=99s definition; thus to =E2=80=9Chide=E2=80=9D a service, on=
e-off code needs to be added to the different Ambari facilities.
> *Solution*
> Add visibility attributes to service definitions to describe how Ambari s=
hould expose services via front-end facilities.   The following Boolean att=
ributes should be settable by services:
> * installable
> ** indicates if Ambari can install the service - if not installable, the =
service should be hidden from =E2=80=9Cadd service=E2=80=9D features of Amb=
ari
> * managed
> ** indicates if Ambari can start and stop the service - if not managed, t=
he 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)