Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Received-SPF: pass (athena.apache.org: domain of joris@mesosphere.io
 designates 74.125.82.72 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADKthhA8pYp8JBKWRVDFezy0HKejA-5_M9vKo2qU5=5r-OwEdg@mail.gmail.com>
References: 
 <CADKthhA8pYp8JBKWRVDFezy0HKejA-5_M9vKo2qU5=5r-OwEdg@mail.gmail.com>
Date: Tue, 14 Apr 2015 11:22:31 -0700
Message-ID: 
 <CAKgKkU6U-MF_ocvL0NatNDJtHDoOk_1QiayJf8601Wz0mH=s9g@mail.gmail.com>
Subject: Re: Oversubscription design doc
From: Joris Van Remoortere <joris@mesosphere.io>
To: "dev@mesos.apache.org" <dev@mesos.apache.org>
Cc: "user@mesos.apache.org" <user@mesos.apache.org>
Content-Type: multipart/alternative; boundary=e89a8f234d455159da0513b350fa

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

We have a dedicated IRC channel for this: "mesos-oversubscription". Feel
free to drop in and chat.

On Tue, Apr 14, 2015 at 11:09 AM, Niklas Nielsen <niklas@mesosphere.io>
wrote:

> Hi everyone,
>
> In context of some of the recent discussions on 'Resource overcommittal',
> we are very interested and invested in enabling oversubscription in Mesos
> in a safe and efficient way. Some of the community members have been
> working on an architecture document and prototypes recently and feel we
> have something we can start working out of:
>
> https://docs.google.com/document/d/1pUnElxHy1uWfHY_FOvvRC73QaOGgdXE0OXN-gbxdXA0/edit#
>
> We will continue meeting up and discussing the approach, as it is a
> significant change to how workloads are run on Mesos.
> Feel free to jump in, add suggestions, raise concerns and participate in
> the development of this feature.
>
> Cheers,
> Niklas
>

--e89a8f234d455159da0513b350fa--