Re: Failed to build Mesos module

On Wed, Sep 23, 2015 at 1:42 AM, zhiwei wrote: > Hi Kapil, > > I don't know how to contribute to modules project, but there are two > issues: > One possibility is to simply create a pull request on github :-). > > My testing machine is Ubuntu 14.04 amd64. > > *1. Mesos

Re: Why do we need slave_id in Kill message

This decision also makes it easier for us to explore relaxing the globally unique requirement on TaskID, instead requiring that be unique, which makes some problems easier to solve. For example: https://issues.apache.org/jira/browse/MESOS-3070. Also, it could allow us to further

Re: Request to add me to the contributors list

Added. Now you can assign JIRAs to yourself. Welcome to the project! Thanks for contributing On Tue, Sep 22, 2015 at 7:35 PM, Li Qiang QL Lin wrote: > Thanks! > > Regards > Liqiang Lin

Re: need help/shepherd on MESOS-1806

The registrar by default uses the replicated log as a storage backend, and the replicated log uses zookeeper for replica discovery, so this may be related to your etcd integration. On Thu, Sep 17, 2015 at 11:47 PM, Shuai Lin wrote: > Hi, > > I am working on MESOS-1806

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

+1 (binding) Tested on CI for CentOS7, Fedora22, and Ubuntu 14.04. On Tue, Sep 22, 2015 at 1:41 PM, Niklas Nielsen wrote: > +1 (binding) > > On 21 September 2015 at 11:46, Vinod Kone wrote: > >> +1 (binding) >> >> Tested on CI for CentOS5 and

Re: Failed to build Mesos module

Hi Kapil, Thank you for your guide, I have created two pull requests on Github. One is for using built-in picojson header file(git submodule), the other is let the script to choose the library path. https://github.com/mesos/modules/pull/6 https://github.com/mesos/modules/pull/7 Thanks. On

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

+1 (binding) Tested on CI for CentOS7, Fedora22, and Ubuntu 14.04. On Wed, Sep 23, 2015 at 10:25 AM, haosdent wrote: > +1 test on Ubuntu 14.04 > > On Tue, Sep 22, 2015 at 9:06 AM, Adam Bordelon wrote: > >> Hi friends, >> >> Please vote on releasing the

Re: [2/2] mesos git commit: Added masterSlaveLostHook.

On 23 September 2015 at 15:47, Benjamin Mahler wrote: > +dev > > Just so the rest of the dev community understands, are these kinds of event > based hooks going to be subsumed by a mechanism to stream out cluster > events? Or will these hooks co-exist alongside cluster

Re: [2/2] mesos git commit: Added masterSlaveLostHook.

+dev Just so the rest of the dev community understands, are these kinds of event based hooks going to be subsumed by a mechanism to stream out cluster events? Or will these hooks co-exist alongside cluster events? On Wed, Sep 23, 2015 at 3:38 PM, wrote: > Added

Re: [2/2] mesos git commit: Added masterSlaveLostHook.

Ok, any plan to add TODOs with this context? On Wed, Sep 23, 2015 at 4:11 PM, Niklas Nielsen wrote: > On 23 September 2015 at 15:47, Benjamin Mahler > wrote: > > > +dev > > > > Just so the rest of the dev community understands, are these kinds

Re: [2/2] mesos git commit: Added masterSlaveLostHook.

It applies to all hooks; so I don't think a TODO fit well around the mastSlaveLostHook() as a one-off. Do you want it for each hook or in the module docs? As long as the plans around eventing and subscribing to events from modules haven't been solidified more, I'd suggest we post-pone adding it as

Re: Working Group List

Rather than address these suggestions, I'd like to first understand the motivation behind them. Feel free to start a separate thread about any difficulties you're observing that you'd like the dev community to discuss. On Mon, Sep 21, 2015 at 3:12 PM, Jojy Varghese wrote: >

Re: Working Group List

The proposal lists the motivations in the "problem statement” section. -Jojy > On Sep 23, 2015, at 4:27 PM, Benjamin Mahler > wrote: > > Rather than address these suggestions, I'd like to first understand the > motivation behind them. Feel free to start a separate

Re: Working Group List

I see, could you start a thread about the difficulties so that we can explore them further? I just want to avoid hijacking this thread as these should be discussed independently. I will share my thoughts there, as I'm sure others will :) On Wed, Sep 23, 2015 at 4:54 PM, Jojy Varghese

Re: [2/2] mesos git commit: Added masterSlaveLostHook.

My understanding was that it doesn't apply to all hooks because some hooks mutate data (e.g. add labels), whereas some hooks are "read-only" event-like hooks. On Wed, Sep 23, 2015 at 4:37 PM, Niklas Nielsen wrote: > It applies to all hooks; so I don't think a TODO fit well

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

+1 (binding) Tested on CI for centos5/6 @vinodkone > On Sep 23, 2015, at 3:45 PM, Adam Bordelon wrote: > > +1 (binding) Tested on CI for CentOS7, Fedora22, and Ubuntu 14.04. > >> On Wed, Sep 23, 2015 at 10:25 AM, haosdent wrote: >> >> +1 test on

Re: Working Group List

I would be happy to start a new thread. I had the proposal in this thread on suggestion(verbal) from Nick who started this thread. Maybe because the underlying issues are same. -jojy On Wed, Sep 23, 2015 at 5:09 PM Benjamin Mahler wrote: > I see, could you start a