Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Sat, 9 Nov 2013 00:24:17 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <JIRA.12678356.1383956582712.45429.1383956657765@arcas>
In-Reply-To: <JIRA.12678356.1383956582712@arcas>
References: <JIRA.12678356.1383956582712@arcas>
Subject: [jira] [Updated] (AMBARI-3731) Add support for custom action
 execution
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


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

Sumit Mohanty updated AMBARI-3731:
----------------------------------

    Issue Type: Sub-task  (was: Bug)
        Parent: AMBARI-1426

> Add support for custom action execution
> ---------------------------------------
>
>                 Key: AMBARI-3731
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3731
>             Project: Ambari
>          Issue Type: Sub-task
>          Components: controller
>    Affects Versions: 1.4.2
>            Reporter: Sumit Mohanty
>            Assignee: Sumit Mohanty
>             Fix For: 1.4.2
>
>
> An action is executed on demand.  Actions can also be executed as a part =
of some other operation being executed by Ambari. For example, =E2=80=98Ver=
ify Kerberos Setting=E2=80=99 can be executed while setting up the secured =
cluster or at a later point when the admin has a need to verify the setting=
 while debugging some issue.
> Once an action is requested by posting the request to the cluster specifi=
c actions collection, the executor can monitor the status to know when the =
action has finished execution. The links specific to the hosts can be monit=
ored for progress on specific hosts.
> Ambari Server may execute the action on all hosts in parallel.=20
> A custom action execution request consists of:
> * ActionName: This is a reference to the action being executed
> * Inputs: The inputs provided by the action executor to the action
> * TargetHosts: The set of hosts where the action should be executed
> *API support for Custom Action Execution*
> An action is scheduled by posting a request resource.
> {code}
> curl -u admin:admin -X POST -d'{"RequestInfo":{"context":"Execute an acti=
on", "action" : "a1", "service_name" : "HDFS", "component_name":"DATANODE",=
 "hosts":"h1"}}' http://localhost:8080/api/v1/clusters/c1/requests
> {code}
> Sub-tasks:
> * API support to post action execution
> * API support to read executed actions
> * DB changes to hold action execution requests


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