Re: Allowed whitelist devices in Mesos

[Jie Yu]

+ 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 this thread:
https://github.com/kubernetes/kubernetes/issues/5607

I made some suggestion in the following review, but I'd like to hear about
what you guys think.
https://reviews.apache.org/r/58337/

- Jie

On Tue, Apr 18, 2017 at 10:14 AM, haosdent  wrote:

> Got it, have reverted. Let's discuss the API changes first.
>
> On Tue, Apr 18, 2017 at 9:02 AM, Jie Yu  wrote:
>
>> Hi,
>>
>> I noticed this recent commit:
>> https://reviews.apache.org/r/58337/
>>
>> First of all, thanks for the patch and the review. But I think there is
>> some discussion that needs to be carried out at the API level. See my
>> comments in the review.
>>
>> @haosdent, I'd prefer we revert this patch for now so that we can discuss
>> what the correct API is going to be. What do you think?
>>
>> - Jie
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>

Mesos 1.2.1 release

[Adam Bordelon]

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:
https://issues.apache.org/jira/issues/?filter=12340606

Please commit/backport your 1.2.1 changes ASAP so I can cut 1.2.1-rc1 this
week.

Thanks!
-Adam-

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

[Adam Bordelon]

-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.
>
>
> 1.0.4 includes the following:
>
> 
> 
>
> * [MESOS-2537] - AC_ARG_ENABLED checks are broken
>
>
> * [MESOS-6606] - Reject optimized builds with libcxx before 3.9
>
>
> * [MESOS-7008] - Quota not recovered from registry in empty cluster.
>
>
> * [MESOS-7366] - Agent sandbox gc could accidentally delete the entire
> persistent volume content.
>
> * [MESOS-7383] - Docker executor logs possibly sensitive parameters.
>
>
>
> The CHANGELOG for the release is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_
> plain;f=CHANGELOG;hb=1.0.4-rc1
>
> 
> 
>
>
> The candidate for Mesos 1.0.4 release is available at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/mesos-1.0.4.tar.gz
>
>
> The tag to be voted on is 1.0.4-rc1:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.4-rc1
>
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/
> mesos-1.0.4.tar.gz.md5
>
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/
> mesos-1.0.4.tar.gz.asc
>
>
> The PGP key used to sign the release is here:
>
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
>
> The JAR is up in Maven in a staging repository here:
>
> https://repository.apache.org/content/repositories/orgapachemesos-1184
>
>
> Please vote on releasing this package as Apache Mesos 1.0.4!
>
>
> The vote is open until Thu Apr 20 15:42:56 PDT 2017 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
>
> [ ] +1 Release this package as Apache Mesos 1.0.4
>
> [ ] -1 Do not release this package because ...
>
>
> Thanks,
>

[VOTE] Release Apache Mesos 1.0.4 (rc1)

[Vinod Kone]

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 with libcxx before 3.9


* [MESOS-7008] - Quota not recovered from registry in empty cluster.


* [MESOS-7366] - Agent sandbox gc could accidentally delete the entire
persistent volume content.

* [MESOS-7383] - Docker executor logs possibly sensitive parameters.



The CHANGELOG for the release is available at:

https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.4-rc1




The candidate for Mesos 1.0.4 release is available at:

https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/mesos-1.0.4.tar.gz


The tag to be voted on is 1.0.4-rc1:

https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.4-rc1


The MD5 checksum of the tarball can be found at:

https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/mesos-1.0.4.tar.gz.md5


The signature of the tarball can be found at:

https://dist.apache.org/repos/dist/dev/mesos/1.0.4-rc1/mesos-1.0.4.tar.gz.asc


The PGP key used to sign the release is here:

https://dist.apache.org/repos/dist/release/mesos/KEYS


The JAR is up in Maven in a staging repository here:

https://repository.apache.org/content/repositories/orgapachemesos-1184


Please vote on releasing this package as Apache Mesos 1.0.4!


The vote is open until Thu Apr 20 15:42:56 PDT 2017 and passes if a
majority of at least 3 +1 PMC votes are cast.


[ ] +1 Release this package as Apache Mesos 1.0.4

[ ] -1 Do not release this package because ...


Thanks,

Mesos 1.3 Release

[Michael Park]

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, please push it off to 1.4.

Here's the dashboard for the release: https://issues.apache.org/jira/secure/
Dashboard.jspa?selectPageId=12331153

Thanks,

MPark

[Design doc] RPC: Fault domains in Mesos

[Neil Conway]

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 to different Mesos clusters.

(2) To improve the experience of configuring Mesos with a set of
masters and agents in one DC, and another pool of "remote" agents in a
different DC.

For more information, please see the design doc:

https://docs.google.com/document/d/1gEugdkLRbBsqsiFv3urRPRNrHwUC-i1HwfFfHR_MvC8

I'd love any feedback, either directly on the Google doc or via email.

Thanks,
Neil