Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <2197832A-4BA8-4F30-A950-E98ED742A60A@gmail.com>
References: <6CFAD16F-C42C-415E-BC35-A4BA60CB8C9E@gmail.com>
 <CAK7Zj10SpMcLp+yRS-o5AUo=pC+wAFoWmxRvsCGdWqTi_+ND+A@mail.gmail.com>
 <2197832A-4BA8-4F30-A950-E98ED742A60A@gmail.com>
From: Zameer Manji <zmanji@apache.org>
Date: Tue, 17 Feb 2015 18:51:18 -0800
Message-ID: 
 <CAK7Zj10KQEU-Skf9MEw69ZEL+z7wt7kmf_2BoG-MukWPHxTS4g@mail.gmail.com>
Subject: Re: [proposal] Deprecate the Thermos CLI
To: "dev@aurora.incubator.apache.org" <dev@aurora.incubator.apache.org>
Content-Type: multipart/alternative; boundary=001a1136feb690bb41050f53e6f2

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

One thing I would like to point out is the thermos CLI is not required for
Aurora operation. I think we would be better served by advertising it as an
optional component that provides operators and users with debugging ability=
.

On Tue, Feb 17, 2015 at 6:38 PM, Joseph Smith <yasumoto7@gmail.com> wrote:

> I believe it absolutely is- ideally as we deprecate the Observer, we can
> then lean on the Mesos Slave for this information instead. This will
> further decrease the number of moving pieces, simplifying the operation o=
f
> an Aurora/Mesos cluster.
>
> > On Feb 17, 2015, at 6:33 PM, Zameer Manji <zmanji@apache.org> wrote:
> >
> > Joe,
> >
> > If I understand Brian's proposal correctly <
> >
> http://mail-archives.apache.org/mod_mbox/aurora-dev/201501.mbox/%3CCAFTdr=
0DZvH21tR=3DNLK0qP-Y9-oL9SyULy6GLah=3DCApuW0SVvnw@mail.gmail.com%3E
> >,
> > we are going to depreciate the Observer. This combined with your propos=
al
> > will make the executor the only component that can read the thermos
> > checkpoints and produce some output that is human readable. Is that
> > something we want to do?
> >
> > On Tue, Feb 17, 2015 at 6:26 PM, Joseph Smith <yasumoto7@gmail.com>
> wrote:
> >
> >> Hi everyone,
> >>
> >> After reviewing the functionality offered by the Thermos Commandline
> tool
> >> vs. what=E2=80=99s exported via the Thermos Observer, I was hoping to =
bring up a
> >> question I had:
> >>
> >> Can we deprecate the Thermos CLI?
> >>
> >> Removing this would decrease the number of components required for a
> >> functional Aurora installation (a huge victory, in my opinion) and als=
o
> >> enable the Observer to fully take over the duty of providing visibilit=
y
> >> into what=E2=80=99s running on a most. In addition, maintenance is per=
formed via
> >> the HostMaintenance API <
> >>
> https://github.com/apache/incubator-aurora/blob/master/src/main/python/ap=
ache/aurora/admin/host_maintenance.py#L26
> >
> >> and should not be done using thermos kill, which would cause LOST task=
s.
> >>
> >> That said, removing this tool makes it much more difficult for Thermos
> to
> >> be used as a monit <http://mmonit.com/monit/> replacement, which is
> >> actually rather feasible now. In addition, it also forces people to
> >> remember + learn the port the Observer is running on in order to get
> >> information about tasks.
> >>
> >> Any thoughts and opinions would be much appreciated!
> >>
> >> Thanks!
> >> Joe
> >>
> >> --
> >> Zameer Manji
> >>
> >>
>
> --
> Zameer Manji
>
>

--001a1136feb690bb41050f53e6f2--