Re: Failed to build Mesos module

Hi Kapil, Any updates? :-) I have resolved that issue with a workaround by using the option "--disable-java", like: ../configure --with-glog=/usr --with-protobuf=/usr --with-boost=/usr --disable-java And then I did "make" and "make install" successfully. However, after I cloned the code

need help/shepherd on MESOS-1806

Hi, I am working on MESOS-1806 (substitute zookeeper with etcd) based on the former work of Cody Maloney. After a general understanding of mesos code base, this week I rebased the code to the latest master (with necessary changes), and it compiles well. The code is here:

[VOTE] Release Apache Mesos 0.24.1 (rc1)

Hi friends, Please vote on releasing the following candidate as Apache Mesos 0.24.1. 0.24.1 includes the following: * [MESOS-2986] - Docker version output is not compatible with Mesos * [MESOS-3136] - COMMAND health

Re: Working Group List

+1 On Fri, Sep 18, 2015 at 10:55 AM, Niklas Nielsen wrote: > Hi folks, > > Per our last community meeting, I created a list on our Confluence Wiki to > keep track of and increase visibility into the running working groups. > We have previously created these groups

need help/shepherd on MESOS-3435

I plan to add Hyper support on Marathon. So i proposal this request on Marathon, https://github.com/mesosphere/marathon/issues/1815 but in discussion and tim mentioned, i first need familiar with mesos docker implement. I want to know which way is best: does it good start:

Re: need help/shepherd on MESOS-3435

I think it helps to write a design doc first, as I'm not familiar with hyper and basically how it works and how it maps to the containerizer API. But yes docker.cpp can be a reference how to integrate another containerizer, and it's not the only way which depends on the containerizer. Tim >

Working Group List

Hi folks, Per our last community meeting, I created a list on our Confluence Wiki to keep track of and increase visibility into the running working groups. We have previously created these groups implicitly, and as the community grow, we unfortunately ended up with duplicate meetings with