Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of yasumoto7@gmail.com
 designates 209.85.220.41 as permitted sender)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: [proposal] Deprecate the Thermos CLI
From: Joseph Smith <yasumoto7@gmail.com>
In-Reply-To: 
 <CAOTkfX5AOLfya+8OkCDix5PSvL40Ao-uA_5pYoqqG7mjnzN1zw@mail.gmail.com>
Date: Mon, 23 Feb 2015 13:12:39 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AA1F59F-0954-46CC-A687-B6FFE3BE4C47@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>
 <CAK7Zj10KQEU-Skf9MEw69ZEL+z7wt7kmf_2BoG-MukWPHxTS4g@mail.gmail.com>
 <CAGRA8uPK0MWwqqyL-EHg8BEbVvR=02aASaF6SuoPZmvBWGESXw@mail.gmail.com>
 <CAOTkfX5NG6pOHqfLHyhJhs3YcKuY-x9pTE8zLLbJ9Odod9AobA@mail.gmail.com>
 <CAFTdr0Au65OWNkZNPc-OK=2_Ko=jCVezKPFcZCXR3XPygeEx+Q@mail.gmail.com>
 <CAGRA8uO1eN9tF1HqavnL1MHVV___627pB3WQw4VPp+O9ODEvKA@mail.gmail.com>
 <CAOTkfX5AOLfya+8OkCDix5PSvL40Ao-uA_5pYoqqG7mjnzN1zw@mail.gmail.com>
To: dev@aurora.incubator.apache.org

I actually find that the observer fits this usecase just as well, and is =
a better interface since the scheduler gives users a link to it on each =
host as well.

I=E2=80=99m looking to decrease build complexity, and removing this =
would be a great victory for that.

> On Feb 18, 2015, at 12:56 PM, Maxim Khutornenko <maxim@apache.org> =
wrote:
>=20
> Running "thermos status --verbosity=3D3" gives full thermos task =
history
> including the sandbox path and process table contents. This really
> saves time when trying to get to the failed task details or see what
> else is running on a host.
>=20
> On Wed, Feb 18, 2015 at 12:04 PM, Bill Farner <wfarner@apache.org> =
wrote:
>> Can either of you elaborate on the type of debugging you currently
>> accomplish with this tool?
>>=20
>> On Wednesday, February 18, 2015, Brian Wickman <wickman@apache.org> =
wrote:
>>=20
>>> I agree it is a valuable component.  However, I think that until it =
has
>>> test coverage we should consider it an unsupported tool.  Filed =
AURORA-1131
>>> <https://issues.apache.org/jira/browse/AURORA-1131>.  This is =
already on
>>> my
>>> radar as part of AURORA-1027
>>> <https://issues.apache.org/jira/browse/AURORA-1027>.
>>>=20
>>> On Wed, Feb 18, 2015 at 9:19 AM, Maxim Khutornenko <maxim@apache.org
>>> <javascript:;>> wrote:
>>>=20
>>>>> Moving parts should either provide value or be obliterated from =
our
>>>> source tree.
>>>>=20
>>>> I generally agree. In this particular case it's still unclear to me =
-
>>>> in the absence of Thermos CLI and Observer, how do we conduct live
>>>> site executor/thermos troubleshooting?
>>>>=20
>>>> On Tue, Feb 17, 2015 at 7:45 PM, Bill Farner <wfarner@apache.org
>>> <javascript:;>> wrote:
>>>>>>=20
>>>>>> I think we would be better served by advertising it as an
>>>>>> optional component that provides operators and users with =
debugging
>>>>>> ability.
>>>>>=20
>>>>>=20
>>>>> Slightly tangential discussion, but i think we should be very =
skeptical
>>>> of
>>>>> fringe components.  Moving parts should either provide value or be
>>>>> obliterated from our source tree.
>>>>>=20
>>>>> -=3DBill
>>>>>=20
>>>>> On Tue, Feb 17, 2015 at 6:51 PM, Zameer Manji <zmanji@apache.org
>>> <javascript:;>> wrote:
>>>>>=20
>>>>>> 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.
>>>>>>=20
>>>>>> On Tue, Feb 17, 2015 at 6:38 PM, Joseph Smith =
<yasumoto7@gmail.com
>>> <javascript:;>>
>>>> wrote:
>>>>>>=20
>>>>>>> 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
>>>>>> of
>>>>>>> an Aurora/Mesos cluster.
>>>>>>>=20
>>>>>>>> On Feb 17, 2015, at 6:33 PM, Zameer Manji <zmanji@apache.org
>>> <javascript:;>>
>>>> wrote:
>>>>>>>>=20
>>>>>>>> Joe,
>>>>>>>>=20
>>>>>>>> If I understand Brian's proposal correctly <
>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>=20
>>> =
http://mail-archives.apache.org/mod_mbox/aurora-dev/201501.mbox/%3CCAFTdr0=
DZvH21tR=3DNLK0qP-Y9-oL9SyULy6GLah=3DCApuW0SVvnw@mail.gmail.com%3E
>>>>>>>> ,
>>>>>>>> we are going to depreciate the Observer. This combined with =
your
>>>>>> proposal
>>>>>>>> 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?
>>>>>>>>=20
>>>>>>>> On Tue, Feb 17, 2015 at 6:26 PM, Joseph Smith <
>>> yasumoto7@gmail.com <javascript:;>>
>>>>>>> wrote:
>>>>>>>>=20
>>>>>>>>> Hi everyone,
>>>>>>>>>=20
>>>>>>>>> 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:
>>>>>>>>>=20
>>>>>>>>> Can we deprecate the Thermos CLI?
>>>>>>>>>=20
>>>>>>>>> Removing this would decrease the number of components required
>>> for
>>>> a
>>>>>>>>> functional Aurora installation (a huge victory, in my opinion)
>>> and
>>>>>> also
>>>>>>>>> enable the Observer to fully take over the duty of providing
>>>>>> visibility
>>>>>>>>> into what=E2=80=99s running on a most. In addition, =
maintenance is
>>>> performed
>>>>>> via
>>>>>>>>> the HostMaintenance API <
>>>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>=20
>>> =
https://github.com/apache/incubator-aurora/blob/master/src/main/python/apa=
che/aurora/admin/host_maintenance.py#L26
>>>>>>>>=20
>>>>>>>>> and should not be done using thermos kill, which would cause =
LOST
>>>>>> tasks.
>>>>>>>>>=20
>>>>>>>>> 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.
>>>>>>>>>=20
>>>>>>>>> Any thoughts and opinions would be much appreciated!
>>>>>>>>>=20
>>>>>>>>> Thanks!
>>>>>>>>> Joe
>>>>>>>>>=20
>>>>>>>>> --
>>>>>>>>> Zameer Manji
>>>>>>>>>=20
>>>>>>>>>=20
>>>>>>>=20
>>>>>>> --
>>>>>>> Zameer Manji
>>>>>>>=20
>>>>>>>=20
>>>>>>=20
>>>>=20
>>>=20
>>=20
>>=20
>> --
>> -=3DBill