aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joseph Smith <>
Subject [proposal] Deprecate the Thermos CLI
Date Wed, 18 Feb 2015 02:26:55 GMT
Hi everyone,

After reviewing the functionality offered by the Thermos Commandline tool vs. what’s 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 also enable the Observer to fully take over the duty of
providing visibility into what’s running on a most. In addition, maintenance is performed
via the HostMaintenance API <>
 and should not be done using thermos kill, which would cause LOST tasks.

That said, removing this tool makes it much more difficult for Thermos to be used as a 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!

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message