Mailing-List: contact dev-help@aurora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.apache.org
MIME-Version: 1.0
Sender: jeffschroed@gmail.com
In-Reply-To: 
 <CAJ4qn4m7CujsNMr81ngWUB_FW6EYTnXm+LFQMA4U4ibTvnWYpQ@mail.gmail.com>
References: 
 <CAOTkfX5m6Vs50NiR+MbJHqgHwaW81x13UYsusqSoc1OhJet8Cg@mail.gmail.com>
	<1445414309661.77792@blue-yonder.com>
	<CAK7Zj12KiUG7X4=+3SsZV=16UnjasjiwWwxryjf9=EvB3eVcjw@mail.gmail.com>
	<CAJ4qn4kwC4EHWK6FebSbcR=M4HN=iSbE=O2pETdsZmEh2v8bow@mail.gmail.com>
	<CAJvN1BMvUHuNZ2v0Tt20kbjx9hi_CZ0vSKGSw=hL8o1Wxd9s4A@mail.gmail.com>
	<CAJ4qn4=ARVDizDUNrV2zQRqyiGAEPL=mmMLir7P95ovJZH85Fw@mail.gmail.com>
	<CAMReA914FrSSJwd=aeDmwmd9HnebWCcozAfbMWUC+JLRSfLwtg@mail.gmail.com>
	<CAJ4qn4m7CujsNMr81ngWUB_FW6EYTnXm+LFQMA4U4ibTvnWYpQ@mail.gmail.com>
Date: Thu, 22 Oct 2015 10:28:40 -0500
Message-ID: 
 <CAMReA93yJo7xtJL6sT48=EhPj9h5JkSEvD6ztiN5mV7s_1eKbQ@mail.gmail.com>
Subject: Re: Unified container support in Aurora
From: Jeff Schroeder <jeffschroeder@computer.org>
To: "dev@aurora.apache.org" <dev@aurora.apache.org>
Content-Type: multipart/alternative; boundary=001a113f8e164bca2b0522b3260b

--001a113f8e164bca2b0522b3260b
Content-Type: text/plain; charset=UTF-8

Ah excellent. I was a bit confused as I know the Tellapart team, which I
believe you're a member of, really knows this stack really well. Hopefully
you sent that back upstream :)

I still see more outages due to weird docker bugs than virtually anything
else and am pretty excited to see this support land.

This doesn't seem like a discussion that should really happen here though
as it is the mesos direction more than Aurora's. Perhaps we should move
this to the mesos users list?

On Thursday, October 22, 2015, Steve Niemitz <sniemitz@twitter.com.invalid>
wrote:

> I'm in fact more familiar with them than I'd like, as I've had to modify
> the docker containerizer to support both CFS and correct memory and CPU
> stats. ;)
>
> On Thu, Oct 22, 2015 at 11:09 AM, Jeff Schroeder <
> jeffschroeder@computer.org <javascript:;>
> > wrote:
>
> > On Thursday, October 22, 2015, Steve Niemitz
> <sniemitz@twitter.com.invalid
> > >
> > wrote:
> >
> > > >
> > > > because docker's runtime isolation (e.g., cpu, memory, etc) is not
> > > > compatible with Mesos's runtime isolation
> > >
> > >
> > > I find that kind of an odd statement, as they both just use cgroups to
> > > achieve said isolation.
> >
> >
> > I suspect you aren't familiar with the mesos isolators. Yes they both use
> > control groups under the hood, but they are different. They are also
> > plugins that fit in with the rest of mesos, docker does not. I'm quite
> > excited about this as the docker daemon is far and above the least stable
> > part of my infrastructure.
> >
> > These are native mesos modules which means mesos can track and manage the
> > resource consumption:
> > http://mesos.apache.org/documentation/latest/network-monitoring/
> >
> >
> > --
> > Text by Jeff, typos by iPhone
> >
>


-- 
Text by Jeff, typos by iPhone

--001a113f8e164bca2b0522b3260b--