Re: Surfacing additional issues on agent host to schedulers

> On Feb 20, 2018, at 11:11 AM, Zhitao Li wrote: > > Hi, > > In one of recent Mesos meet up, quite a couple of cluster operators had > expressed complaints that it is hard to model host issues with Mesos at the > moment. > > For example, in our environment, the only

Feb 21 Performance WG Meeting Canceled

Hi folks, since there's nothing on the agenda for this month's meeting. I will cancel it and plan to meet next month. If there are any topics folks would like to discuss let me know and we can schedule one sooner!

Save the date: ApacheCon North America, September 24-27 in Montréal

Dear Apache Enthusiast, (You’re receiving this message because you’re subscribed to a user@ or dev@ list of one or more Apache Software Foundation projects.) We’re pleased to announce the upcoming ApacheCon [1] in Montréal, September 24-27. This event is all about you — the Apache project

Re: Follow up on providing `--reconfiguration_policy=any` in future versions

Hi Benno, Thanks for the the diff. I took a quick look and cannot anticipate issues with it in our environment. I'll talk to our release manager to try it out in our environment. w.r.t. to the health check issue, is there meeting notes or a JIRA issue capturing existing discussions? On Mon, Feb

Surfacing additional issues on agent host to schedulers

Hi, In one of recent Mesos meet up, quite a couple of cluster operators had expressed complaints that it is hard to model host issues with Mesos at the moment. For example, in our environment, the only signal scheduler would know is whether Mesos agent has disconnected from the cluster. However,

Re: API working group

Hi everyone, Please vote for your favorite WG times in this doodle poll . Greg and Vinod, please let me know ASAP if you need me to add poll options. Best! Judith On Wed, Feb 14, 2018 at 6:00 PM, Greg Mann wrote: > Sounds good to

[GitHub] mesos issue #263: Allow nested containers in pods to have separate namespace...

Github user Gilbert88 commented on the issue: https://github.com/apache/mesos/pull/263 A quick note that we could have a followup patch to add documents here: http://mesos.apache.org/documentation/latest/containerizer-internals/#linux-namespaces ---

[GitHub] mesos issue #263: Allow nested containers in pods to have separate namespace...

Github user jdef commented on the issue: https://github.com/apache/mesos/pull/263 What's the high level use case that's driving this change request? One of the major goals of task-groups (pods) is to allow containers to share networking and storage. What point is there in launching a