Re: Compile with CFLAGS=-DWITH_NETWORK_ISOLATOR

Hi, Problem solved, thanks guys. Just for future reference, here's a summary of what should be done to enable --network-isolator 1. Make sure kernel version is >= 3.15 or apply proper patches 2. Install libnl with version >= 3.2.26, make sure headers are installed into /usr/include (using

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

On Tue, Mar 22, 2016 at 5:10 AM, Kevin Klues wrote: > This way it's easy to track the full set of release candidates, as well as > how they relate to previous release candidates, minor releases, and point > releases. There is no essential difference with the current approach

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

On Fri, Mar 18, 2016 at 4:59 PM, Kevin Klues wrote: > I respectfully disagree. > > The whole purpose of tags is to mark permanent things like releases, > whereas branches are designed as temporary lines of development that > come and go (and grow and shrink) dynamically all the

Re: Compile with CFLAGS=-DWITH_NETWORK_ISOLATOR

> On Mar 22, 2016, at 6:21 AM, Jay Guo wrote: > > Hi, > > I got error trying to compile Mesos > on Ubuntu > with CFLAG WITH_NETWORK_ISOLATOR > > Here's what I did: > 1. apt-get install libnl-dev > 2. ./bootstrap > 3. mkdir build && cd build > 4.

Re: Compile with CFLAGS=-DWITH_NETWORK_ISOLATOR

On Tue, Mar 22, 2016 at 6:21 AM, Jay Guo wrote: > > Also, does this work with OSX? Is there any equivalent library as libnl? No, netlink is a very specific and powerful feature on Linux, and it is one big reason why Linux is MUCH better than OSX on networking. See:

Re: Looking for Shepherd for MESOS-5002

Thanks Neil. I added you to the Review request. Best, -- Jiří Šimša On Tue, Mar 22, 2016 at 9:30 AM, Neil Conway wrote: > Sure, I'd be happy to review the change. > > Neil > > > On Tue, Mar 22, 2016 at 9:01 AM, Jie Yu wrote: > > + Neil > > > > Neil

Re: Compile with CFLAGS=-DWITH_NETWORK_ISOLATOR

As haosdent said, the default libnl-3 that comes with ubuntu is not new enough. It will cause the following check in configure.ac to fail: AC_CHECK_LIB([nl-3], [nl_has_capability], ... because the default ubuntu version does not contain the function nl_has_capability. You need to install the

Re: Usage of protobuf 'enum' fields

+1 I have run into this issue before and it was very confusing. On Tue, Mar 22, 2016 at 1:37 AM, tommy xiao wrote: > yes, following apache upgrade doc guide, the step is master update firstly, > than upgrade slave. it can't support slave firstly. so this is rule on our > ops

Re: Looking for Shepherd for MESOS-5002

Sure, I'd be happy to review the change. Neil On Tue, Mar 22, 2016 at 9:01 AM, Jie Yu wrote: > + Neil > > Neil is driving the documentation improvement in Mesos. Neil, do you have > time for that? I can help commit the patch if you give a shipit. > > - Jie > > On Tue, Mar

Re: Compile with CFLAGS=-DWITH_NETWORK_ISOLATOR

I did try this feature before, and you may want to follow here https://github.com/apache/mesos/blob/master/docs/network-monitoring.md#prerequisites to install the right version prerequisites first. On Tue, Mar 22, 2016 at 9:21 PM, Jay Guo wrote: > Hi, > > I got error

Re: Compile with CFLAGS=-DWITH_NETWORK_ISOLATOR

Hi, this only works in linux. Please install this libnl https://github.com/thom311/libnl/releases/tag/libnl3_2_27 On Tue, Mar 22, 2016 at 9:21 PM, Jay Guo wrote: > Hi, > > I got error trying to compile Mesos > on Ubuntu > with CFLAG WITH_NETWORK_ISOLATOR > > Here's

Compile with CFLAGS=-DWITH_NETWORK_ISOLATOR

Hi, I got error trying to compile Mesos on Ubuntu with CFLAG WITH_NETWORK_ISOLATOR Here's what I did: 1. apt-get install libnl-dev 2. ./bootstrap 3. mkdir build && cd build 4. CXXFLAGS=-DWITH_NETWORK_ISOLATOR ../configure --disable-java --disable-python 5. make check Although I got following

Re: [jira] [Created] (MESOS-4993) FetcherTest.ExtractZipFile assumes `unzip` is installed

My bad. Fix is ready for review https://reviews.apache.org/r/45134/diff/2 - Tomek pon., 21.03.2016 o 22:03 użytkownik Benjamin Mahler napisał: > +jie, Tomasz > > Looks like this new test needs a filter. Can one of you follow up with a > fix? > > On Mon, Mar 21, 2016 at

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

The way I've dealt with this on other projects in the past is the following: 1) RC1s for minor releases (e.g., 0.28.0-rc1, 0.29.0-rc1, 0.30-rc1, etc.) are *always* tagged at some commit on the master branch. ​ This is only true for actual minor release (i.e. not point releases, e.g. 0.28.1,

Re: Filing bugs and flaky test tickets

+1 2016-03-22 18:33 GMT+08:00 Joris Van Remoortere : > If you are filing a bug, please do set the `affected version` for all the > versions that you are sure it affects. > > This will assist us in identifying potential backport targets, as well as > identify which things are

Re: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

+1 for branch per RC (if we go with branches). I like your argument against re-writing history if we make a mistake. I think the 2 issues that have come up are: 1) visibility into the release process 2) pain / lack of context for the release manager of backports to resolve merge conflicts for

Re: Filing bugs and flaky test tickets

If you are filing a bug, please do set the `affected version` for all the versions that you are sure it affects. This will assist us in identifying potential backport targets, as well as identify which things are critical to fix before the next release cycle. Starting with 0.28 we added a new

Re: Usage of protobuf 'enum' fields

yes, following apache upgrade doc guide, the step is master update firstly, than upgrade slave. it can't support slave firstly. so this is rule on our ops step. 2016-03-22 10:29 GMT+08:00 Benjamin Mahler : > Hi folks, > > I wanted to surface the following ticket to our

Re: RFC: RevocableInfo Changes

@benm/joris, here's the user scenario in my mind: 1. master offers resources to the framework, e.g. 2 cpu 2. framework launch a task (2 cpu) and *mark the task/executors as throttleable* 3. in ResourceEstimator, it should only consider the throttleable task/executors: - keep enough resources

Re: [jira] [Created] (MESOS-4948) MasterMaintenanceTest.InverseOffers is flaky

Sorry, I didn't realize the summary of this ticket had changed since this email was generated, and the plan is now to migrate the test to the new scheduler library. On Mon, Mar 21, 2016 at 11:21 PM, Benjamin Mahler wrote: > +joseph > > Have you seen this? > > On Tue, Mar 15,

Re: [jira] [Created] (MESOS-4948) MasterMaintenanceTest.InverseOffers is flaky

+joseph Have you seen this? On Tue, Mar 15, 2016 at 7:13 AM, Greg Mann (JIRA) wrote: > Greg Mann created MESOS-4948: > > > Summary: MasterMaintenanceTest.InverseOffers is flaky > Key: MESOS-4948 >

Re: [jira] [Created] (MESOS-4635) CoordinatorTest.AppendDiscarded is flaky

+jie Jie, have you seen this? On Wed, Feb 10, 2016 at 7:46 AM, Greg Mann (JIRA) wrote: > Greg Mann created MESOS-4635: > > > Summary: CoordinatorTest.AppendDiscarded is flaky > Key: MESOS-4635 >

Filing bugs and flaky test tickets

Folks, Our JIRA volume is very high and I'm finding that important bugs and flaky tests are getting lost in the noise. When filing a bug or a flaky test ticket as a dev in the project, it's critical to 'git blame' the code to determine who is responsible for it, in order to notify them of the

Re: [jira] [Updated] (MESOS-4984) MasterTest.SlavesEndpointTwoSlaves is flaky

I'm finding these are getting lost in the noise, it would be great when filing test issue tickets to 'git blame' the code and figure out who to notify to fix the test. Could you do that here? On Fri, Mar 18, 2016 at 3:55 PM, Neil Conway (JIRA) wrote: > > [ >