ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Zang <>
Subject Re: Can "Delete" button on Ambari UI be disabled ?
Date Tue, 07 Feb 2017 00:50:18 GMT
Hi Di,

From an end user perspective, you can also use the RBAC features in admin view to assign “Cluster
Operator” or lower role to the users you don’t want add/delete service available.


On 2/6/17, 2:12 PM, "Jaimin Jetly" <> wrote:

    Hi Di,
    Existence of "Delete" button for a service is not stack driven.
    Although on clicking delete action, UI asks end-user to first stop and delete any service
that depends on "being deleted" service.
    This logic is stack driven.
    So when user tries to delete a zookeeper service, ambari-web will ask user to first delete
other "many" services like HDFS, YARN, etc first since they are marked to require zookeeper
service in their service definition.
    Again these restrictions are stack driven but these are made by ambari-web client and
so user can always use API to delete a service directly. In this case all "Delete Service"
API checks is that no host component of service should be in running state.
    -- Thanks
    From: Di Li <>
    Sent: Monday, February 06, 2017 1:43 PM
    Subject: Can "Delete" button on Ambari UI be disabled ?
    Hello folks,
    Can "Delete" button on Ambari UI be disabled (via some stack service
    configuration ) ?  For example, disable the Delete button for Zookeeper as
    many services depend on it ?

View raw message