Return-Path: 
 <user-return-2072-apmail-ambari-user-archive=ambari.apache.org@ambari.apache.org>
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 3444F17AEB
	for <apmail-ambari-user-archive@www.apache.org>;
 Fri,  3 Apr 2015 00:41:50 +0000 (UTC)
Received: (qmail 78526 invoked by uid 500); 3 Apr 2015 00:41:45 -0000
Delivered-To: apmail-ambari-user-archive@ambari.apache.org
Received: (qmail 78492 invoked by uid 500); 3 Apr 2015 00:41:45 -0000
Mailing-List: contact user-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@ambari.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@ambari.apache.org>
List-Post: <mailto:user@ambari.apache.org>
List-Id: <user.ambari.apache.org>
Reply-To: user@ambari.apache.org
Delivered-To: mailing list user@ambari.apache.org
Received: (qmail 78482 invoked by uid 99); 3 Apr 2015 00:41:44 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2015 00:41:44 +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 truthisoutwhere@gmail.com
 designates 209.85.213.171 as permitted sender)
Received: from [209.85.213.171] (HELO mail-ig0-f171.google.com)
 (209.85.213.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2015 00:41:39 +0000
Received: by ignm3 with SMTP id m3so57799402ign.0
        for <user@ambari.apache.org>; Thu, 02 Apr 2015 17:39:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=ukk0sz3hHjhWb8hkyKM9e56A69QJSpmIAU4RBUHtJNo=;
        b=PZ25/rfo7VmolhFOEv7XvXhRQtj6Kkql8pNvBY6ANOgNetapfLrdZA/PecExeYubFa
         fuBUW/qtb56c6SYhRNyIUB7J4on7xwoClxCsULYFmg2KCSnmKsaunPyoQJUhfbtSCiqo
         +zJnH+zSFFIl/RzIkyMx8h89CfBiGszJMelAL7+I2tX3eiZei0Hv6X5lkbZkGc2hVWIf
         +tJh++lrErl5V0uJvHhCk7Yk23At6OY2Pdop97EBJyCCACb/PtD7s4h31GK3A3VFamfa
         JheiZ3KTMilC8/kg439Tpn602qLnk4VM3hnBNpOqb4i65pr7k8qYtvD+6bvrQFQWdChF
         PJHg==
MIME-Version: 1.0
X-Received: by 10.107.37.132 with SMTP id l126mr59586347iol.42.1428021544142;
 Thu, 02 Apr 2015 17:39:04 -0700 (PDT)
Received: by 10.36.152.130 with HTTP; Thu, 2 Apr 2015 17:39:04 -0700 (PDT)
Date: Thu, 2 Apr 2015 17:39:04 -0700
Message-ID: 
 <CAN-ywPBZnFA6TSnGR1X_w9dgPGNWO-q3QGGfoM5dychAZcY8Ww@mail.gmail.com>
Subject: Locating services using Ambari APIs
From: Um ar <truthisoutwhere@gmail.com>
To: user@ambari.apache.org
Content-Type: multipart/alternative; boundary=001a1140ecbadecf120512c72c30
X-Virus-Checked: Checked by ClamAV on apache.org

--001a1140ecbadecf120512c72c30
Content-Type: text/plain; charset=UTF-8

Hi,

I am looking for a way to find out which service is running where on my
cluster programmatically using Ambari APIs. For example, how to locate
where 'Slider Client' is installed so that any slider commands can be
redirected to that node.

Thanks,
-Umar

--001a1140ecbadecf120512c72c30
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-size:12.8000001907349px">Hi,</span><di=
v style=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-size:=
12.8000001907349px">I am looking for a way to find out which service is run=
ning where on my cluster programmatically using Ambari APIs. For example, h=
ow to locate where &#39;Slider Client&#39; is installed so that any slider =
commands can be redirected to that node.</div><div style=3D"font-size:12.80=
00001907349px"><br></div><div style=3D"font-size:12.8000001907349px">Thanks=
,</div><div style=3D"font-size:12.8000001907349px">-Umar</div></div>

--001a1140ecbadecf120512c72c30--