Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Mon, 28 Oct 2013 21:12:32 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12632127.1360717957815.13585.1382994752850@arcas>
In-Reply-To: <JIRA.12632127.1360717957815@arcas>
References: <JIRA.12632127.1360717957815@arcas>
Subject: [jira] [Updated] (AMBARI-1426) Create cluster level Custom Action
 support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Sumit Mohanty updated AMBARI-1426:
----------------------------------

    Attachment: Custom_Action_Support_Using_Ambari-Design.docx

Attaching the design document.

> Create cluster level Custom Action support
> ------------------------------------------
>
>                 Key: AMBARI-1426
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1426
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.5.0
>
>         Attachments: Custom_Action_Support_Using_Ambari-Design.docx
>
>
> While managing an HDP cluster, the admin may need to execute custom scrip=
ts etc. to perform house-keeping operations. Ambari support for smoke test =
can be viewed as one such operation, which has a first class support in Amb=
ari. It is conceivable that in future releases several such operations need=
 to be supported by Ambari. Some such requirements are:
> * Validate Kerberos settings
> * Perform metadata check/backup (e.g. fsck) prior to upgrade
> * Dump the list of datanodes
> Rather than designing each of these capabilities in a one-off fashion, it=
 is useful to develop an infrastructure to execute such operations and then=
 define new operations based on the infrastructure.=20
> h3. Custom Action Definition
> A custom action is a python (_can be extended to other scripting language=
 including puppet_) script that can be executed to perform any management a=
ctivity on a cluster. The relevant aspects of a custom action are:
> *Alias*: A friendly name of a custom action. E.g. =E2=80=9CValidate_Kerbe=
ros_Setting=E2=80=9D
> *Definition*: The definition of the custom action. This is essentially a =
script that will get executed.
> *Input*: A set of name-value pairs that are the input to the script. E.g.=
 =E2=80=9Cprincipal=3Dabc@abc.com=E2=80=9D.
> *Context*: The default context that is available to all custom actions. T=
he context will include.
> * Cluster name
> * Host name
> * Service name
> * Component name
> *Target*: The target node(s)/host(s), where the custom action will be exe=
cuted. Optionally, an action may explicitly specify the component on which =
it can be executed =E2=80=93 e.g. NAMENODE, in which case a host that has t=
he component mapped will be randomly selected.=20
> *MaxExecutionTime*: The maximum execution time allowed for these class of=
 custom actions. Ambari will enforce an absolution maximum time limit for a=
ll custom actions


--
This message was sent by Atlassian JIRA
(v6.1#6144)