Return-Path: X-Original-To: apmail-ambari-user-archive@www.apache.org Delivered-To: apmail-ambari-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 28D22C6B5 for ; Thu, 5 Jun 2014 14:10:26 +0000 (UTC) Received: (qmail 33752 invoked by uid 500); 5 Jun 2014 14:10:26 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 33721 invoked by uid 500); 5 Jun 2014 14:10:26 -0000 Mailing-List: contact user-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ambari.apache.org Delivered-To: mailing list user@ambari.apache.org Received: (qmail 33713 invoked by uid 99); 5 Jun 2014 14:10:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2014 14:10:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of smohanty@hortonworks.com designates 209.85.160.177 as permitted sender) Received: from [209.85.160.177] (HELO mail-yk0-f177.google.com) (209.85.160.177) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jun 2014 14:10:21 +0000 Received: by mail-yk0-f177.google.com with SMTP id 10so244251ykt.22 for ; Thu, 05 Jun 2014 07:10:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Sgvzrz7rrIdlqZk58dEleMkGBhcWE11MfdI/acYIVmY=; b=F64fLZh0qB3/O/rNQIrxuxtrpq3yrVaPNfy5NYbmt/e2bBsaVqn2/emWgrn0j1Dyrq KShDBN5Ymb+TXHyCS8cJLXPTeY3xDuVlK2tegmpyPCrYgf7nwlgjbPk9KwgDd4oTiv1C cBsGp7TJ0dyhPe9rvnFKSMo/YNqEWx0m8i9z98LsjK4+Apw5X+ZeRicIStny/WT+8b/4 9nI983ZdwETcQwOpavQndvyTLCvtaKrg3okN6sXBzPd6+fr+s22+59Czz4UNLhlhzZur tE2zb4OxYh3FdOHdYoZqpnJL4fTTVN3eLpzOjSpIz5XtdbFSRdxJvTRZkx34iVpe/1zs DHYQ== X-Gm-Message-State: ALoCoQlefrsU7uLunKIc0r5hh6iogNk+z0NbuEqzWjLdDURREvy4wZfSboi+QKm99UTfF0BzMF4fHelv95m+upEplmul4x+Xz8MtrZZ+TaEIJ8ohlObKCCI= MIME-Version: 1.0 X-Received: by 10.236.194.169 with SMTP id m29mr36189649yhn.121.1401977401182; Thu, 05 Jun 2014 07:10:01 -0700 (PDT) Received: by 10.170.113.203 with HTTP; Thu, 5 Jun 2014 07:10:01 -0700 (PDT) In-Reply-To: References: Date: Thu, 5 Jun 2014 07:10:01 -0700 Message-ID: Subject: Re: Running smoke test From: Sumit Mohanty To: "user@ambari.apache.org" Content-Type: multipart/alternative; boundary=bcaec50dc668fb1f5b04fb174c56 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec50dc668fb1f5b04fb174c56 Content-Type: text/plain; charset=UTF-8 Can you provide some details on what type of check you want to do? You can use custom actions support for that. You will need to define a custom action first. There is API only support for issuing custom action on all hosts and then the action can perform the test and then report back results. What version of Ambari are you using? I need to check if custom action is supported. -Sumit On Wed, Jun 4, 2014 at 10:23 AM, Anisha Agarwal wrote: > Thanks for the explanation Sumit. > I have some tests which I want to run on all hosts on the cluster each > time. > How can I make that happen? > > Thanks, > Anisha > > From: Sumit Mohanty > Reply-To: "user@ambari.apache.org" > Date: Tuesday, June 3, 2014 at 9:45 PM > To: "user@ambari.apache.org" > Subject: Re: Running smoke test > > The implementation of smoke test depends on what will happen when you > run smoke tests. Smoke tests shipped with the stacks test the services for > basic capabilities - e.g. hbase smoke test will create a table. From the > perspective of creating a table it does not make much sense to test it on > all hosts. > > A client instance is randomly chosen and the test is ran only from one > client host. As its random, you may notice that different host got used on > different runs of the same test. > > -Sumit > > > On Tue, Jun 3, 2014 at 3:41 PM, Anisha Agarwal > wrote: > >> Hi, >> >> I have a couple of questions about running smoke tests. >> >> 1. Both during installation, and post installation (using >> maintenance->run smoke test), I see that the smoke test run on a single >> host. How is this host decided when running smoke tests? It is different >> for me during installation, and post-installation. >> >> 2. Is it possible to run smoke tests on all hosts in the cluster? >> >> Thanks, >> Anisha >> > > > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity > to which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. > -- CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are hereby notified that any printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and delete it from your system. Thank You. --bcaec50dc668fb1f5b04fb174c56 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Can you provide some details on what type of check you wan= t to do?

You can use custom actions support for that. Yo= u will need to define a custom action first. There is API only support for = issuing custom action on all hosts and then the action can perform the test= and then report back results.=C2=A0

What version of Ambari are you using? I need to ch= eck if custom action is supported.

-Sumit



On Wed, Jun 4, 2014 at 10:23 AM, Anisha Agarwal <aagarwal@hexiscyber= .com> wrote:
Thanks for the explanation Sumit.
I have some tests which I want to run on all hosts on the cluster each= time.
How can I make that happen?

Thanks,
Anisha

From: Sumit Mohanty <smohanty@hortonworks.com= >
Reply-To: "user@ambari.apache.org" &= lt;user@ambari.= apache.org>
Date: Tuesday, June 3, 2014 at 9:45= PM
To: "user@ambari.apache.org" <user@ambari.apache= .org>
Subject: Re: Running smoke test

The implementation of smoke test depends on what will happ= en when you run smoke tests. Smoke tests shipped with the stacks test the s= ervices for basic capabilities - e.g. hbase smoke test will create a table.= From the perspective of creating a table it does not make much sense to test it on all hosts.=C2=A0

A client instance is randomly chosen and the test is ran only from one= client host. As its random, you may notice that different host got used on= different runs of the same test.

-Sumit


On Tue, Jun 3, 2014 at 3:41 PM, Anisha Agarwal <= span dir=3D"ltr"> <aagarwal@h= exiscyber.com> wrote:
Hi,

I have a couple of questions about running smoke tests.=C2=A0

1. Both during installation, and post installation (using maintenance-= >run smoke test), I see that the smoke test run on a single host. How is= this host decided when running smoke tests? It is different for me during = installation, and post-installation.=C2=A0

2. Is it possible to run smoke tests on all hosts in the cluster?

Thanks,
Anisha


CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or e= ntity to which it is addressed and may contain information that is confiden= tial, privileged and exempt from disclosure under applicable law. If the reader of this message is not= the intended recipient, you are hereby notified that any printing, copying= , dissemination, distribution, disclosure or forwarding of this communicati= on is strictly prohibited. If you have received this communication in error, please contact the sender immed= iately and delete it from your system. Thank You.


CONFIDENTIALITY NOTICE
NOTICE: This message is = intended for the use of the individual or entity to which it is addressed a= nd may contain information that is confidential, privileged and exempt from= disclosure under applicable law. If the reader of this message is not the = intended recipient, you are hereby notified that any printing, copying, dis= semination, distribution, disclosure or forwarding of this communication is= strictly prohibited. If you have received this communication in error, ple= ase contact the sender immediately and delete it from your system. Thank Yo= u. --bcaec50dc668fb1f5b04fb174c56--