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 4C6B910F9E for ; Sat, 29 Mar 2014 17:15:25 +0000 (UTC) Received: (qmail 92399 invoked by uid 500); 29 Mar 2014 17:15:24 -0000 Delivered-To: apmail-ambari-user-archive@ambari.apache.org Received: (qmail 92283 invoked by uid 500); 29 Mar 2014 17:15:24 -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 92274 invoked by uid 99); 29 Mar 2014 17:15:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Mar 2014 17:15:23 +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 (nike.apache.org: domain of swagle@hortonworks.com designates 209.85.219.52 as permitted sender) Received: from [209.85.219.52] (HELO mail-oa0-f52.google.com) (209.85.219.52) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Mar 2014 17:15:18 +0000 Received: by mail-oa0-f52.google.com with SMTP id l6so7347202oag.25 for ; Sat, 29 Mar 2014 10:14:55 -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=aAoLCQJ6AAefyk7y9an73yiAsx+hiXVmvPtVDzuEsC0=; b=A1LPTrOZlVJSqT4FjNm3Fbf0JVSs0tPi791Qw6O89njVcQCH0/uP9o1M+f8jSchaY8 VAq1WuG9HRWZyNEUS5h1nqQRtpK9CdC+/Bt5c97lFJOWROEUZZbz9ZB58o/p3H5Q3Ecc xYvP9USvzTo50IHpFSqOU2Jt3TnfoYCRbIKY8HyX1+BYicviZBFZGBfmcEL4PfuhvXcm 2D3ZOwYklkZ3BDqgh49Vw/lYpI7zGRj3ldUCtWh2ePobSRgaRiRUpSA26fxTSSLfb3NW edmjCqSoFQgPPZg0MOKuUxEWk05cjpajsmRsJ9ePq8z5FgMtUaSbhhEI6I1b29DbwUsX Ul8Q== X-Gm-Message-State: ALoCoQkuYQ5XasyRzryCEIJHZguYIX97G3x/JJDcTqtSjzYdptPUthU1i5UjPNj/FTNWagVPSGZQ/UdGTo8guK0McKjfCh+BmNlUz9oGBpDXulMimOQjOiA= MIME-Version: 1.0 X-Received: by 10.60.94.231 with SMTP id df7mr23619oeb.69.1396113295680; Sat, 29 Mar 2014 10:14:55 -0700 (PDT) Received: by 10.76.122.114 with HTTP; Sat, 29 Mar 2014 10:14:55 -0700 (PDT) In-Reply-To: References: Date: Sat, 29 Mar 2014 10:14:55 -0700 Message-ID: Subject: Re: role dependency question From: Siddharth Wagle To: "user@ambari.apache.org" Content-Type: multipart/alternative; boundary=089e011761830e606504f5c1f56c X-Virus-Checked: Checked by ClamAV on apache.org --089e011761830e606504f5c1f56c Content-Type: text/plain; charset=US-ASCII We use Role Command order to figure out what can be run in parallel within a stage and what cannot. However, we do Install and Start as separate stages, the Start / Stop API calls are designed to do State transitions which effectively mean create Start stage after and Install stage is successful. So, looking at the RoleCommandOrder.java, there does not seem to be anything stopping you from adding that dependency, I might be wrong with a cursory look, but still that would not help with achieving what you are trying to do since those tasks will be part of separate Stages. Could you open a Jira for this with some use case documentation? The use case would really help with the discussion flow. Best Regards, Sid On Fri, Mar 28, 2014 at 3:10 PM, Yusaku Sako wrote: > AFAIK, we currently don't have a way to express "A must be running > before installing B". > Perhaps others can chime in. > BTW, which specific components do you have in mind? > > Yusaku > > On Mon, Mar 24, 2014 at 5:17 PM, Aaron Cody wrote: > > I have two components, A and B > > B requires A to be running while it installs... > > Q: is there a way to express this in the role-dependencies? (I know > how to > > say 'A must run before B can run' .. or 'A must be installed before B is > > installed', but how about 'A must be running before installing B') > > > > TIA > > > > -- > 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. --089e011761830e606504f5c1f56c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
We use Role Command order to figu= re out what can be run in parallel within a stage and what cannot.

<= /div>However, we do Install and Start as separate stages, the Start / Stop = API calls are designed to do State transitions which effectively mean creat= e Start stage after and Install stage is successful.

So, looking at the RoleCommandOrder.java, there does not seem to = be anything stopping you from adding that dependency, I might be wrong with= a cursory look, but still that would not help with achieving what you are = trying to do since those tasks will be part of separate Stages.

Could you open a Jira for this with some use case documentation? = The use case would really help with the discussion flow.

Best = Regards,
Sid


On Fri, Mar 28, 2014 at 3:10 PM, Yusaku Sako <yusaku@hortonworks.com= > wrote:
AFAIK, we currently don't have a way to express "A must be running=
before installing B".
Perhaps others can chime in.
BTW, which specific components do you have in mind?

Yusaku

On Mon, Mar 24, 2014 at 5:17 PM, Aaron Cody <acody@hexiscyber.com> wrote:
> I have two components, A and B
> B requires A to be running while it installs...
> Q: is there a way to express t= his in the role-dependencies? =A0 (I know how to
> say 'A must run before B can run' .. or 'A must be install= ed before B is
> installed', but how about 'A must be running before installing= B')
>
> TIA
>

--
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 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. --089e011761830e606504f5c1f56c--