Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mesos-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of wanggd04@gmail.com designates
 209.85.215.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAFeOQnWjtkka3Vav-E8-YiP5aiqTEZXeh3=Gw1o6e7ne=RuMfQ@mail.gmail.com>
References: 
 <CAPXBsRC9cekoGZ0wEeBtdiJBUF2KLCWvL6KFu_j_fLGdG-jNWQ@mail.gmail.com>
 <CAFeOQnWjtkka3Vav-E8-YiP5aiqTEZXeh3=Gw1o6e7ne=RuMfQ@mail.gmail.com>
From: =?UTF-8?B?546L5Zu95qCL?= <wanggd04@gmail.com>
Date: Tue, 4 Jun 2013 10:47:13 +0800
Message-ID: 
 <CAPXBsRD_f_rZcHVt_YcioMKhcQNgiXh_RUwd6FA0YCe69kSV4A@mail.gmail.com>
Subject: Re: options '--conf' in Mesos-master and mesos-slave are removed?
To: mesos-dev <mesos-dev@incubator.apache.org>
Content-Type: multipart/mixed; boundary=001a11c368de6b92f304de4b1a4b

--001a11c368de6b92f304de4b1a4b
Content-Type: multipart/alternative; boundary=001a11c368de6b92f004de4b1a49

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

Hi Ben,

Yesterday, I changed the mesos-daemon. In my solution, I split the old conf
file into 2 conf files, one for masters, the other for slaves.

My patch is attached. But I am not sure whether my solution matches your
purpose. If your purpose is to discard the conf file, I think the second
way you mentioned(using env vars) will be a better way.

If my solution is OK, I would like to post a review.

Thanks.


Guodong


On Tue, Jun 4, 2013 at 1:48 AM, Benjamin Hindman <benh@eecs.berkeley.edu>wr=
ote:

> Hi Guodong,
>
> We'd like to simplify things a bit so we're moving to only allowing flags
> on the command line or via environment variables. I have two suggestions:
>
> (1) If you currently use a configuration file, turn that configuration fi=
le
> into a script that actually launches one of the binaries and puts the fla=
gs
> directly on the command line.
>
> (2) Change your configuration file to actually just put all the options i=
n
> the environment via MESOS_ (e.g., master=3Dip:port would now be
> MESOS_master=3Dip:port). You can then source this file before launching t=
he
> master or slave.
>
> Thanks for pointing out that mesos-daemon.sh needs to get updated too. I'=
ve
> created this ticket <https://issues.apache.org/jira/browse/MESOS-490> tha=
t
> you can track (or better yet, please contribute!).
>
> Ben.
>
>
> On Sun, Jun 2, 2013 at 7:27 PM, =E7=8E=8B=E5=9B=BD=E6=A0=8B <wanggd04@gma=
il.com> wrote:
>
> > Hi guys,
> >
> > I have checked out the latest code from the git repo.
> >
> > But I can not run the mesos-slave and mesos-master with the
> > script mesos-daemon.sh. I check the option of mesos-master and
> mesos-slave,
> > is the '--conf' removed ?
> >
> > How to start the cluster for the new code?
> >
> > Best
> >
> > Guodong
> >
>

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

<div dir=3D"ltr">Hi Ben,<div><br></div><div style>Yesterday, I changed the =
mesos-daemon. In my solution, I split the old conf file into 2 conf files, =
one for masters, the other for slaves.</div><div style><br></div><div style=
>

My patch is attached. But I am not sure whether my solution matches your pu=
rpose. If your purpose is to discard the conf file, I think the second way =
you mentioned(using env vars) will be a better way.</div><div style><br>

</div><div style>If my solution is OK, I would like to post a review.</div>=
<div style><br></div><div style>Thanks.</div><div style><br></div></div><di=
v class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr">Guodong</di=
v>

</div>
<br><br><div class=3D"gmail_quote">On Tue, Jun 4, 2013 at 1:48 AM, Benjamin=
 Hindman <span dir=3D"ltr">&lt;<a href=3D"mailto:benh@eecs.berkeley.edu" ta=
rget=3D"_blank">benh@eecs.berkeley.edu</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">

Hi Guodong,<br>
<br>
We&#39;d like to simplify things a bit so we&#39;re moving to only allowing=
 flags<br>
on the command line or via environment variables. I have two suggestions:<b=
r>
<br>
(1) If you currently use a configuration file, turn that configuration file=
<br>
into a script that actually launches one of the binaries and puts the flags=
<br>
directly on the command line.<br>
<br>
(2) Change your configuration file to actually just put all the options in<=
br>
the environment via MESOS_ (e.g., master=3Dip:port would now be<br>
MESOS_master=3Dip:port). You can then source this file before launching the=
<br>
master or slave.<br>
<br>
Thanks for pointing out that mesos-daemon.sh needs to get updated too. I=
9;ve<br>
created this ticket &lt;<a href=3D"https://issues.apache.org/jira/browse/ME=
SOS-490" target=3D"_blank">https://issues.apache.org/jira/browse/MESOS-490<=
/a>&gt; that<br>
you can track (or better yet, please contribute!).<br>
<br>
Ben.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Sun, Jun 2, 2013 at 7:27 PM, =E7=8E=8B=E5=9B=BD=E6=A0=8B &lt;<a href=3D"=
mailto:wanggd04@gmail.com">wanggd04@gmail.com</a>&gt; wrote:<br>
<br>
&gt; Hi guys,<br>
&gt;<br>
&gt; I have checked out the latest code from the git repo.<br>
&gt;<br>
&gt; But I can not run the mesos-slave and mesos-master with the<br>
&gt; script mesos-daemon.sh. I check the option of mesos-master and mesos-s=
lave,<br>
&gt; is the &#39;--conf&#39; removed ?<br>
&gt;<br>
&gt; How to start the cluster for the new code?<br>
&gt;<br>
&gt; Best<br>
&gt;<br>
&gt; Guodong<br>
&gt;<br>
</div></div></blockquote></div><br></div>

--001a11c368de6b92f004de4b1a49--

--001a11c368de6b92f304de4b1a4b--