Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0DCCB17CAB for ; Fri, 7 Nov 2014 05:06:34 +0000 (UTC) Received: (qmail 23041 invoked by uid 500); 7 Nov 2014 05:06:33 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 22998 invoked by uid 500); 7 Nov 2014 05:06:33 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 22986 invoked by uid 99); 7 Nov 2014 05:06:33 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Nov 2014 05:06:33 +0000 Date: Fri, 7 Nov 2014 05:06:33 +0000 (UTC) From: "Jonathan Hurley (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-7985) Allow for server-side commands MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-7985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201609#comment-14201609 ] Jonathan Hurley commented on AMBARI-7985: ----------------------------------------- [~rlevas] - It looks like your patch increased the test time from 35 minutes to over 47 minutes causing the builds to timeout. How many tests did you add? Are they spinning up a database - that's usually what adds time to the test suite. I've actually never seen a patch increase the test time this much. > Allow for server-side commands > ------------------------------ > > Key: AMBARI-7985 > URL: https://issues.apache.org/jira/browse/AMBARI-7985 > Project: Ambari > Issue Type: New Feature > Components: ambari-server > Affects Versions: 2.0.0 > Reporter: Robert Levas > Assignee: Robert Levas > Labels: ambari-server, commands, server, server-side, tasks > Fix For: 2.0.0 > > Attachments: AMBARI-7985_01.patch, AMBARI-7985_01.patch > > > Ambari currently handles _client-/agent-side_ commands; however there is no ability to handle _server-side_ commands. Server-side commands should be specified as a task in a stage and managed along with the stage. > *Use Case:* Generate principals and keytabs on the Ambari server before sending the keytabs to their relevant hosts. > *Implementation:* To add the concept of a server-side task: > * update {{org.apache.ambari.server.serveraction.ServerAction}} to be an _abstract class_ > ** _server-side_ tasks must implement this class > * reuse existing _host_role_command_ and _execution_command_ data > ** _server-side_ tasks are to have a role of {{AMBARI_SERVER_ACTION}} > ** _server-side_ execution command data should be encapsulated as JSON and specify the ServerAction implementation class and any needed payload data > * {{org.apache.ambari.server.actionmanager.ActionScheduler}} and {{org.apache.ambari.server.serveraction.ServerActionManagerImpl}} need to be updated to handle the execution of server-side tasks > ** each _server-side_ task should be executed in its own thread. > *** _server_side_ tasks should be executed in (staged) order, serially - not in parallel > *** _server_side_ tasks should ensure not to mess up _stage_ ordering -- This message was sent by Atlassian JIRA (v6.3.4#6332)