Re: Allowed whitelist devices in Mesos

+ dev list Thanks! We can iterate on the design on this thread. I noticed that k8s model this in their CRI interface, but not in the top level API: https://github.com/kubernetes/kubernetes/blob/release-1.5/pkg/kubelet/api/v1alpha1/runtime/api.proto#L490 There are some interesting discussion in

Mesos 1.2.1 release

Hello Mesos Developers, It's patch-release time, and we've got 34 patches in the 1.2.x branch since we cut 1.2.0-rc2 (2017/02/24) and voted it in as 1.2.0 (2017/03/08). We've also got ~10 patches targeted to 1.2.1 that still need to be resolved/backported:

Re: [VOTE] Release Apache Mesos 1.0.4 (rc1)

-0, wish we could include the fix for https://issues.apache.org/jira/browse/MESOS-7265 in 1.0.4, but I won't hold the release for it. On Mon, Apr 17, 2017 at 3:44 PM, Vinod Kone wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 1.0.4. >

[VOTE] Release Apache Mesos 1.0.4 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.4. 1.0.4 includes the following: * [MESOS-2537] - AC_ARG_ENABLED checks are broken * [MESOS-6606] - Reject optimized builds

Mesos 1.3 Release

Neil and I are volunteering to be the release managers for the 1.3 release! I'm hoping to cut an RC later this week, if the current blockers have been addressed. Please update the target versions of the tickets you're working on to either target the 1.3 release if it's a blocker, otherwise,

[Design doc] RPC: Fault domains in Mesos

Folks, I'd like to enhance Mesos to support a first-class notion of "fault domains" -- i.e., identifying the "rack" and "region" (DC) where a Mesos agent or master is located. The goal is to enable two main features: (1) To make it easier to write "rack-aware" Mesos frameworks that are portable