Re: Build Mesos on Windows

Hey folks. Microsoft is putting on their annual developer conference, "//build", next week, so I don't have time to respond in detail, but I did want to address the immediate questions of the .patch file and contributing. For contributing at the state of the art, the two most valuable things you

Re: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii characters)

+1 2016-03-25 23:26 GMT+08:00 Yong Tang : > Hi > > Just bump the email to look for shepherd for MESOS-4033. > > This issue (commit hook for non ascii characters) has already been fairly > discussed on the review board. Thanks Deshi, Neil, and haosdent for the >

Re: Build Mesos on Windows

Thank you Tommy and Benjamin, it would be very nice if someone could update with any news. However, I continued trying to build and, after unload the stout_tests project, I am stuck building the Zookeeper dependency. CMake is trying to patch zookeeper-06d3f3f (using that version as 3.4.5 does

Re: Build Mesos on Windows

+ Alex Clemmer On Thu, Mar 24, 2016 at 7:50 PM, tommy xiao wrote: > i remember microsoft team invovled in this case, but not found any update > on it? anyone can update news? > > 2016-03-25 6:08 GMT+08:00 Juan Larriba : > > > Hi all, > > > > I have been

Re: Event bus for Mesos

I think the consensus is that event streaming will come at some point. The status is that we opted to focus instead on making some significant performance improvements to the json endpoints and providing finer-grained endpoints, since these were a much simpler effort. The need at the time was

Re: [proposal] MESOS-4610: MasterContender/MasterDetector should be loadable as modules

Hello Kapil, I just wanted to know if you'd had a chance to take a look at the changes and had any comments on them. Thanks. On Wed, Mar 23, 2016 at 4:07 PM, Anurag Singh < anurag.prakash.si...@gmail.com> wrote: > Thanks, Kapil. I've added you as reviewer. > > On Wed, Mar 23, 2016 at 11:45 AM,

[RFC] Mesos Releases and Support

Hi folks, There has been some interest recently about Mesos releases and support policy. As promised, I spent some time thinking about this and written my thoughts down in a doc. https://docs.google.com/document/d/1A8MglUWST6pWan3cVw98v8uxTPew8RMKxxrRqiSENM0/edit?usp=sharing Please take a look

[RFC] Mesos Releases and Support

Hi folks, There has been some interest recently about Mesos releases and support policy. As promised, I spent some time thinking about this and written my thoughts down in a doc. https://docs.google.com/document/d/1A8MglUWST6pWan3cVw98v8uxTPew8RMKxxrRqiSENM0/edit?usp=sharing Please take a look

Re: Event bus for Mesos

There is this design doc that was circulating a few months back, but I'm not sure what the status of it is: https://docs.google.com/document/d/1b2gheqWPw4V-60RdKu-dGWTy-qLGL5p5xJwmUXteDYE/edit?pli=1#heading=h.86u1r3w05n13 On Fri, Mar 25, 2016 at 10:02 AM, Zhitao Li wrote:

Vote TODAY MesosCon voting closes today, Friday March 25

If you haven't already, please take a few minutes the next few days and review what members of the community have submitted! Voting forms close TODAY, Friday, March 25, 2016, 11:55 PST A total of 154 proposals were submitted in time for #MesosCon review, up significantly from 63 submitted for

Event bus for Mesos

Hi, Has anyone thought about the idea of building some kind of event bus (similar to what Marathon provided) directly inside Mesos? What I roughly have in mind: 1. The HTTP API effort already defined a very rich set of events, which Mesos master/agent could send to scheduler/executor;

Design doc: ordered delivery in libprocess

A few months ago, there was a dev list thread on whether libprocess should provide ordered delivery [1]. The consensus then was that libprocess doesn't provide ordered delivery in a few corner cases, but that we should fix that behavior to guarantee ordered (but unreliable) message delivery.

Re: [Proposal] Use dev mailing list for working groups

SGTM - let's do it :) On Fri, Mar 25, 2016 at 12:44 AM, Jay JN Guo wrote: > +1 > > Although we really need to agree on one single style and stick to it. > > I thought all mails sending to dev@mesos.apache.org would be [MESOS-dev] > by > default. > So I don't know how much

RE: Looking for Shepherd for MESOS-4033 (commit hook for non-ascii characters)

Hi Just bump the email to look for shepherd for MESOS-4033. This issue (commit hook for non ascii characters) has already been fairly discussed on the review board. Thanks Deshi, Neil, and haosdent for the great inputs. It really would be nice if there is anyone that could shepherd so that

Looking for Shepherd for MESOS-3059

Hello, Can anyone please shepherd the following JIRA: https://issues.apache.org/jira/browse/MESOS-3059 This issue add http endpoint to dynamically change the slave attributes. we want to push the design docs and patches so on. -- Deshi Xiao Twitter: xds2000 E-mail: xiaods(AT)gmail.com

Re: [Proposal] Use dev mailing list for working groups

+1 Although we really need to agree on one single style and stick to it. I thought all mails sending to dev@mesos.apache.org would be [MESOS-dev] by default. So I don't know how much sense it would make to have this first label. Even though I strongly agree with @guangya on hierarchical labels.

Re: [Proposal] Use dev mailing list for working groups

+1 On Thu, Mar 24, 2016 at 11:47 PM, Timothy Chen wrote: > +1 > > Tim > > On Thu, Mar 24, 2016 at 8:17 PM, Chris Lambert > wrote: > > Another +1. These WGs are great, and more visibility (with the ability > to > > filter) will be awesome. > > > > > >

Re: [Proposal] Use dev mailing list for working groups

+1 Tim On Thu, Mar 24, 2016 at 8:17 PM, Chris Lambert wrote: > Another +1. These WGs are great, and more visibility (with the ability to > filter) will be awesome. > > > On Thu, Mar 24, 2016 at 8:13 PM, Klaus Ma wrote: > >> +1, that's helpful to