[VOTE] Release Apache Mesos 1.3.3 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.3.3. 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.3.3-rc1

Doc-a-thon Thursday

Hi everyone, I'm looking forward to seeing you at the doc-a-thon on Thursday! A couple important reminders: - Sign up for a project on this spreadsheet [1] before the event! - If you're attending in person please make sure to RSVP on the meetup page [2] so we make sure to get enough food.

Re: Resource offers - DRF - Mesos

Thank you very much, This is exactly the answer I was searching for! - Thodoris > On 22 May 2018, at 21:10, Joseph Wu wrote: > > 1) DRF is based on the _current_ allocation of resources (from the master's > perspective) rather than a historical allocation of resources. > > 2) So when a new c

Re: Resource offers - DRF - Mesos

1) DRF is based on the _current_ allocation of resources (from the master's perspective) rather than a historical allocation of resources. 2) So when a new cluster is started, all frameworks will have a current allocation of 0. And assuming all else (like quotas, roles, and weights) are equivalen

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

+1 On Tue, May 15, 2018 at 2:56 PM, Greg Mann wrote: > +1 (binding) > > I did `sudo make check` and verified that only expected flaky tests failed. > > > Cheers, > Greg > > On Fri, May 11, 2018 at 12:35 PM, Gilbert Song wrote: > >> Hi all, >> >> Please vote on releasing the following candidate

Resource offers - DRF - Mesos

Hello list, I have some questions about resource offers for Mesos and I am experiencing some problems that I hope somebody will be able to help. 1) The allocation module of Mesos master uses DRF (according to previous allocation history) and decides which framework will get an offer, and how many