Re: Thermos external component deprecation plan

2015-01-26 Thread Steve Niemitz
I agree with everything here. A big pain point from the docker integration side was/is the observer, and rolling the observer functionality into the executor would simplify things greatly. On Sat, Jan 24, 2015 at 12:29 PM, Bill Farner wrote: > +1, thanks for the braindump, Brian! This sounds g

Re: Thermos external component deprecation plan

2015-01-24 Thread Bill Farner
+1, thanks for the braindump, Brian! This sounds great. -=Bill On Sat, Jan 24, 2015 at 8:43 AM, Joe Smith wrote: > Thanks for the write up! > > > On Jan 22, 2015, at 13:27, Brian Wickman wrote: > > > > Thermos is a standalone task execution system that is not coupled to > Aurora > > or Mesos.

Re: Thermos external component deprecation plan

2015-01-24 Thread Joe Smith
Thanks for the write up! > On Jan 22, 2015, at 13:27, Brian Wickman wrote: > > Thermos is a standalone task execution system that is not coupled to Aurora > or Mesos. This is why by default, Thermos writes out of the sandbox > (/var/run/thermos), has a separate observability system (Thermos obs