Re: [VOTE] Release Apache Mesos 1.7.0 (rc3)

+1 (binding). Internal CI succeeded. The binary deb/rpm packages for this RC can be found here: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.7.0-rc3 On Fri, Sep 14, 2018 at 4:18 AM Alex Rukletsov wrote: > +1 (binding) > > Mesosphere's internal CI run with the aforementioned

[RESULT][VOTE] Release Apache Mesos 1.4.2 (rc1)

Hi all, The vote for Mesos 1.4.2 (rc1) has passed with the following votes. +1 (Binding) -- *** Ben Mahler *** Kapil Arya *** Alex Ruklestov There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.4.2

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

+1 binding (internal CI). The Apache CI failures reported by Vinod are all known flaky tests. I have inserted the details inline. Best, Kapil On Tue, Aug 14, 2018 at 11:03 AM Vinod Kone wrote: > I see some flaky tests in ASF CI, that I don't see already reported. > > @Kapil Arya

[VOTE] Release Apache Mesos 1.4.2 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.4.2. 1.4.2 is a bug fix release. The CHANGELOG for the release is available at: https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.4.2-rc1 The candidate for Mesos 1.4.2 release is available at:

Re: Getting write access to our GitHub repo

+1. On Wed, Jun 20, 2018 at 10:59 PM Vinod Kone wrote: > Hi folks, > > Looks like ASF now supports giving write > access to committers for their GitHub mirrors, which means we can merge PRs > directly on GitHub! > > FWICT, this requires us moving our repo to a new

Re: API working group

I'm interested in participating. On Tue, Jan 30, 2018 at 1:42 PM, Vinod Kone wrote: > Hi folks, > > We've had good success with our containerization, performance and community > working groups and so we would like to keep the momentum going and spin up > new WGs as

[RESULT][VOTE] Release Apache Mesos 1.4.1 (rc1)

Hi all, The vote for Mesos 1.4.1 (rc1) has passed with the following votes. +1 (Binding) -- *** Vinod Kone *** Kapil Arya *** Anand Mazumdar There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.4.1

Re: .deb packages of mesos releases

> > Yeah, the ASF CI has Ubuntu workers that should work. However, to ensure a sane environment, I would recommend using Debian/Ubuntu containers just like we do for the CentOS builds. That way we can test/run it locally to debug any issues and so on. Does that sound reasonable? > Regards,

Re: .deb packages of mesos releases

Hi Adam, I am wondering if you would have some time to bring your debian packaging into Mesos source tree. We can then use the ASF Jenkins CI to build and publish packages to bintray just like we started doing for CentOS 6/7? This will also allow the community to more actively participate in

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

M-R/view/Mesos/job/Mesos- > Release/43/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=-- > verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu% > 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&am

[VOTE] Release Apache Mesos 1.4.1 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.4.1. 1.4.1 includes the following: * [MESOS-7873] - Expose `ExecutorInfo.ContainerInfo.NetworkInfo` in Mesos `state` endpoint. *

Binary RPM packages for CentOS

Hi All, We have some updates regarding the binary RPM build/release process for Mesos. Here are some important bullet points: * Jira: https://issues.apache.org/jira/browse/MESOS-7981 * The RPM packages are now built using a jenkins job [1] on the Apache CI. * The build scripts are part of the

1.4.1 release

Please reply to this email if you have pending patches to be backported to 1.4.x as we are aiming to cut a release candidate for 1.4.1 early next week. Thanks, Anand and Kapil

Re: mesos.interface==1.4.0

> Kapil was this missed during the 1.4.0 release? Yeah, it was missed due to PyPi deprecating the legacy API which our CI job depended on. The failure to publish went unnoticed unfortunately and hence the missing package. I have uploaded it manually for now and will fix the CI script as well.

[RESULT][VOTE] Release Apache Mesos 1.4.0 (rc5)

Hi all, The vote for Mesos 1.4.0 (rc5) has passed with the following votes. +1 (Binding) -- Vinod Kone Kapil arya Anand Mazumdar There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.4.0 It is recommended to use

Re: [VOTE] Release Apache Mesos 1.4.0 (rc5)

verbose autotools >>> [image: Success] >>> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel >>> ease/42/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=-- >>> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu% >>> 3A14.04,label_exp=(doc

[VOTE] Release Apache Mesos 1.4.0 (rc5)

Hi all, [NOTE: Starting with this RC candidate, we will not be "releasing" RC jar files in the Maven release channel. This prevents polluting of the Maven repositories with numerous RC tags. As before, you can continue to test the release candidate using the Maven staging repository provided

Re: [VOTE] Release Apache Mesos 1.4.0 (rc4)

Looks like an important patch (https://reviews.apache.org/r/62053/) is missing from this RC and so we're canceling the vote. We will publish another RC shortly. Sorry for the inconvenience. Best, Anand and Kapil On Thu, Sep 7, 2017 at 1:57 PM, Kapil Arya <ka...@mesosphere.io> wrote: &g

[VOTE] Release Apache Mesos 1.4.0 (rc4)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.4.0. 1.4.0 includes the following: * Ability to recover the agent ID after a host reboot. * File-based and image-pull secrets. *

[VOTE] Release Apache Mesos 1.4.0 (rc3)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.4.0. 1.4.0 includes the following: * Ability to recover the agent ID after a host reboot. * File-based and image-pull secrets. * Linux

Re: [VOTE] Release Apache Mesos 1.4.0 (rc2)

Hi All, Due to a discrepancy in the CHANGELOG, we are retracting this release candidate and will put out a new release candidate for voting in a little while. Best, Anand and Kapil On Mon, Aug 28, 2017 at 12:44 PM, Kapil Arya <ka...@mesosphere.io> wrote: > Hi all, > > Please vo

[VOTE] Release Apache Mesos 1.4.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.4.0. 1.4.0 includes the following: * Ability to recover the agent ID after a host reboot. * File-based and image-pull secrets. *

[VOTE] Release Apache Mesos 1.4.0 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.4.0. 1.4.0 includes the following: * Ability to recover the agent ID after a host reboot. * File-based and image-pull secrets. *

Re: Mesos 1.4.0

1.4.0 Update We currently have 5 blockers, 4 critical, and 4 major issues. To ramp up the process, we are cutting the 1.4.x branch today to allow master to continue without affecting the 1.4.0 release. Please contact the 1.4.0 release managers for getting your changes cherry-picked from master

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

+1 Green build on internal CI. The RC packages are available at: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.2.2-rc1 The following docker images based on Ubuntu 16.04 are also available: * mesosphere/mesos:1.2.2-rc1 * mesosphere/mesos-master:1.2.2-rc1 *

[RFC] File-based secrets

Hi All, Recently, we started working on providing file-based secrets for Mesos tasks (MESOS-7418 ). The goal is to allow users to populate files within a task's environment with contents fetched from a backend secret store. A new secret fetching

Re: [VOTE] Release Apache Mesos 1.0.3 (rc2)

+1 binding. Built rpm/deb packages on internal build jobs. Packages are available here: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.3-rc2 On Mon, Feb 6, 2017 at 3:01 PM, Adam Bordelon wrote: > +1 binding > > Tests passed against DC/OS 1.8.8

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

+1 (binding). Here is a link to the rpm/deb packages: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.1.0-rc1 Kapil On Fri, Oct 21, 2016 at 5:37 PM, Zhitao Li wrote: > +1 (non-binding) > > make check passes on Debian 8. > > Docker related tests pass. >

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

+1 (binding) You can find the rpm/deb packages here: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.1-rc1 The following docker tags (built off of ubuntu 14.04) are also available: mesosphere/mesos:1.0.1-rc1 mesosphere/mesos-master:1.0.1-rc1

Re: Anonymous modules

It hasn't been removed, but was moved around a bit: https://github.com/apache/mesos/blob/master/src/master/main.cpp#L334 On Tue, Aug 9, 2016 at 5:07 PM, Marco Massenzio wrote: > Hi folks, > > I've recently updated my repo to the 1.0.0 release and noticed that the >

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

nod Kone <vinodk...@apache.org> wrote: > >> Hi all, >> >> The vote for Mesos 1.0.0 (rc4) has passed with the following votes. >> >> >> +1 (Binding) >> >> -- >> >> Kapil Arya >> >> Jie

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

ript successfully from 0.28.2 -> 1.0.0-rc4 >> > >> > Cheers, >> > Greg >> > >> > On Tue, Jul 26, 2016 at 1:58 AM, haosdent <haosd...@gmail.com> wrote: >> > >> >> +1 >> >> >> >> * make check in CentOS 7.2

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

One can find the deb/rpm packages here: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc4 And here are the corresponding docker images based off of Ubuntu 14.04: mesosphere/mesos:1.0.0-rc4 mesosphere/mesos-master:1.0.0-rc4 mesosphere/mesos-slave:1.0.0-rc4

Re: [VOTE] Release Apache Mesos 1.0.0 (rc2)

om/downloads/mesos is using the new configuration? > > On Sun, Jul 10, 2016 at 10:07 AM, Kapil Arya <ka...@mesosphere.io> wrote: > >> The binary rpm/deb packages can be found here: >> http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc2 >> . >

Re: [VOTE] Release Apache Mesos 1.0.0 (rc2)

The binary rpm/deb packages can be found here: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc2. Please note that starting with the 1.0.0 release (including RCs and recent nightly builds), Mesos is configured with SSL and 3rdparty module dependency installation. Here is

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

+1 (binding) Internal CI build. Here is a link to the deb/rpm packages: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-0.26.2-rc1 On Mon, Jun 20, 2016 at 6:07 PM, Vinod Kone wrote: > +1 (binding) > > Tested on ASF CI w/ ubuntu. Note that centos:7 build

Re: Slack as the canonical chat channel

+1 Slack! On Fri, Jun 17, 2016 at 4:37 PM, Yan Xu wrote: > +1 Slack. > > On Friday, June 17, 2016, José Guilherme Vanz > wrote: > > > +1 Slack > > > > On Fri, 17 Jun 2016 at 17:05 Joris Van Remoortere > > wrote: > > > > > +1

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

Here is a link to the rpm/deb packages for Mesos 1.0.0-rc1: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc1 Please note that from this release (>=1.0.0-rc1) onwards, we are configuring Mesos with SSL support. We have also added `--enable-install-module-dependencies`

Re: 0.28.2 has been released

Hi All, The 0.28.2 rpm/deb packages can be found here: http://open.mesosphere.com/downloads/mesos/#apache-mesos-0.28.2 Best, Kapil On Mon, Jun 6, 2016 at 5:21 PM, Kapil Arya <ka...@mesosphere.io> wrote: > Hi Craig, > > I should be sending out a link to the RPM packages in a

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

+1 (binding) Ran CI builds for various distros. The deb/rpm packages can be found here: http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-0.27.3-rc1 Kapil On Tue, Jun 7, 2016 at 1:42 PM, Jie Yu wrote: > Hi all, > > Please vote on releasing the following

Re: 0.28.2 has been released

Hi Craig, I should be sending out a link to the RPM packages in a couple of days. (Our packaging scripts had some issues and I am working on fixing them). Kapil On Mon, Jun 6, 2016 at 6:15 AM, craig w wrote: > Jie, > > Thanks for the updates. When will the packages be

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

+1 (binding) Distro package building for Ubuntu, Debian and CentOS. Here is the link to the RC downloads page: http://open.mesosphere.com/downloads/mesos-rc/ Best, Kapil On Mon, May 30, 2016 at 3:17 PM, Till Toenshoff wrote: > +1 > > Tested on OSX and various distros via

Re: Reorganize 3rdparty directory

ized as we want them > >> >> first, and then start thinking about pulling libprocess/stout out > into > >> >> submodules later (while also preserving their history!) > >> >> > >> >> I disagree with moving libprocess and stout up to the sam

Re: [VOTE] Release Apache Mesos 0.28.1 (rc2)

+1 (binding) CI runs with: amd64/centos/6 amd64/centos/7 amd64/debian/jessie amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid amd64/ubuntu/wily On Wed, Apr 6, 2016 at 11:51 PM, Vinod Kone wrote: > +1 (binding) > > Tested on ASF CI. There was one flaky test

Re: [VOTE] Release Apache Mesos 0.26.1 (rc4)

+1 (binding) CI runs with: amd64/centos/6 amd64/centos/7 amd64/debian/jessie amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid amd64/ubuntu/wily On Wed, Apr 6, 2016 at 11:53 PM, Vinod Kone wrote: > +1(binding) > > Tested on ASF CI. > > The centos failures are

Re: [VOTE] Release Apache Mesos 0.25.1 (rc4)

+1 (binding) CI runs for amd64/centos/6 amd64/centos/7 amd64/debian/jessie amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid amd64/ On Wed, Apr 6, 2016 at 9:43 PM, Vinod Kone wrote: > +1 (binding) > > `./configure && make check` on ubuntu 14.04 > > On Wed, Apr

Re: [VOTE] Release Apache Mesos 0.24.2 (rc5)

+1 (binding) CI runs for amd64/centos/6 amd64/centos/7 amd64/debian/jessie amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid amd64/ On Thu, Apr 7, 2016 at 12:44 AM, Vinod Kone wrote: > +1 (binding) > > make check on ubuntu 14.04 > > On Wed, Apr 6, 2016 at

Re: [02/11] mesos git commit: Added support for contender and detector modules.

Already posted a RR https://reviews.apache.org/r/45876/ :) On Thu, Apr 7, 2016 at 12:29 PM, James Peach wrote: > > > On Apr 6, 2016, at 3:48 PM, ka...@apache.org wrote: > > > > Added support for contender and detector modules. > > > > > > >

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

Anurag, Yan, I can also help in reviewing this stuff. If Yan, has cycles to shepherd it, great, otherwise, I can shepherd it too. Best, Kapil On Wed, Mar 23, 2016 at 2:38 PM, Anurag Singh < anurag.prakash.si...@gmail.com> wrote: > Yan, would you like me to add you as the reviewer on the

Re: [RESULT][VOTE] Release Apache Mesos 0.28.0 (rc2)

t; > > come later this week? >> > > >> > > On Thu, Mar 17, 2016 at 1:28 PM, Vinod Kone <vinodk...@apache.org> >> > wrote: >> > > >> > >> Hi all, >> > >> >> > >> >> > >> The vote for Mesos 0.28.0 (

Re: [VOTE] Release Apache Mesos 0.28.0 (rc2)

+1 (binding). You can find the links to rpm/deb files for this RC here: http://open.mesosphere.com/downloads/mesos-rc/ On Thu, Mar 17, 2016 at 12:58 PM, Michael Park wrote: > +1 (binding) > > Internal CI results with the corresponding JIRA tickets for the failed > tests: > >

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

+1 (Binding) Successful CI builds for the following distros: amd64/centos/6 amd64/centos/7 amd64/debian/jessie amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid On Fri, Mar 4, 2016 at 1:06 PM, Vinod Kone wrote: > Bad copy paste into the email, sorry. It looks

Re: Discussion about upgrading 3rdparty libraries

> > *3. 3rdparty/libprocess/3rdparty/stout/tests/protobuf_tests.pb.cc/h > files.* > > Can anyone tell me why hardcode these two files in Mesos repo? I think > these two files can be dynamically generated during make check, this will > make it not depend on

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

+1 (binding) Successful CI builds for the following distros: amd64/centos/6 amd64/centos/7 amd64/debian/jessie amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid Kapil On Sat, Feb 27, 2016 at 12:53 AM, Michael Park wrote: > Hi all, > > Please vote on releasing the

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

+1 (binding) Successful CI builds for the following distros: amd64/centos/6 amd64/centos/7 amd64/debian/jessie amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid Kapil On Sat, Feb 27, 2016 at 12:26 AM, Michael Park wrote: > Hi all, > > Please vote on releasing the

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

+1 (binding) Successful CI builds for the following distros: amd64/centos/6 amd64/centos/7 amd64/debian/jessie amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid Kapil On Fri, Feb 26, 2016 at 11:54 PM, Michael Park wrote: > Hi all, > > Please vote on releasing

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

+1 (binding) Successful CI builds for the following distros: amd64/centos/6 amd64/centos/7 amd64/debian/jessie amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid Kapil On Sat, Feb 27, 2016 at 1:12 AM, Michael Park wrote: > Hi all, > > Please vote on releasing the

Proposing Mesos patch releases 0.24.2 - 0.26.1

Hi All, We are planning on doing patch releases from 0.24.2 - 0.26.1. Here is the exhaustive list of patches for each release: * Fixes for 0.24.2 only + (MESOS-3052 ) Allocator filter performance fix + (MESOS-3051

Re: Reorganize 3rdparty directory

, but the structure which has led that the stout tests (which do >> need to be compiled) are actually managed in the libprocess Makefile, on >> top of all the things you have already mentioned. >> >> >> > On 09 Feb 2016, at 17:53, Kapil Arya <ka...@mesosphere.io> wro

Re: Mesos 0.27.1

ge- > From: Adam Bordelon [mailto:a...@mesosphere.io] > Sent: Tuesday, February 9, 2016 2:31 AM > To: dev <dev@mesos.apache.org>; Tim Chen <t...@mesosphere.io>; Kapil Arya < > ka...@mesosphere.io> > Subject: Re: Mesos 0.27.1 > > Travis, you need to get

Reorganize 3rdparty directory

Hi All, TLDR: Move everything from 3rdparty/libprocess/3rdparty/* into 3rdparty/. (Optionally) Move libprocess/stout to the top-level directory. I wanted to start some discussion around reorganizing stuff inside "3rdparty". I apologize for the length of the email, please bear with me.

Re: Reorganize 3rdparty directory

that, the gist here is that we have somewhat deviated from original motivation behind the 3rdparty directory and it would be nice if we can have a flatter structure. > > > - Jie > > On Tue, Feb 9, 2016 at 4:14 PM, Kapil Arya <ka...@mesosphere.io> wrote: > > > Hi

Re: Reorganize 3rdparty directory

can decide later and leave stout as an exception for now. BTW, if we were to install all the 3rdparty packages in 3rdparty/, that would also cut down a lot on the compiler flags (i.e., fewer "-I" and "-L" flags) :-). Kapil > > - Jie > > On Tue,

Re: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

the docs on multiple disk resources? >> >> On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya <ka...@mesosphere.io> wrote: >> >> > And here is the blog post: >> > http://mesos.apache.org/blog/mesos-0-27-0-released. >> > >> > On Wed, Feb 3

Re: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

, in my mind. > > Should we line up some expectations to available user docs, example > framework code, etc. before announcing the availability of a feature? > > Niklas > > On Thu, Feb 4, 2016 at 5:41 PM, Kapil Arya <ka...@mesosphere.io> wrote: >> >> And here is

Re: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

And here is the blog post: http://mesos.apache.org/blog/mesos-0-27-0-released. On Wed, Feb 3, 2016 at 4:48 PM, Michael Park wrote: > Kapil is currently working on it. We'll publish it shortly :) > > On 3 February 2016 at 13:41, Benjamin Mahler wrote: >> >>

Re: Shephard Reqeust: patch for MESOS-4370

Thanks for the explanation, Greg!! Travis, Thanks for contributing to Mesos. Please go through the contributor guidelines as suggested by Greg. I can then shepherd the patch for you. Best, Kapil On Tue, Feb 2, 2016 at 2:56 PM, Greg Mann wrote: > Hi Travis, > Thanks for

Re: Install some 3rdparty packages needed for building Mesos modules

nge any semantics of --prefix at all. > > >> On 26 Jan 2016, at 19:54, Kapil Arya <ka...@mesosphere.io> wrote: >> >> Thanks for the feedback, Alex! I have inlined my responses. >> >>> First, I think we should support two use cases: installing 3rdparty

Re: Need a shepherd for MESOS--3317

Hi Abhishek, I can shepherd this for you. Please add me to the RR. Kapil On Wed, Jan 27, 2016 at 12:31 AM, Abhishek Dasgupta wrote: > Vinod, Can you point me someone whom I can ask for the review? > > > On Wednesday 27 January 2016 12:07 AM, Vinod Kone wrote: >> >>

Re: Install some 3rdparty packages needed for building Mesos modules

hard to do. Just that we need to decide which modules should be installed. Best, Kapil > On Wed, Jan 20, 2016 at 8:09 AM, Kapil Arya <ka...@mesosphere.io> wrote: > >> On Wed, Jan 20, 2016 at 2:04 AM, Marco Massenzio <m.massen...@gmail.com> >> wrote: >> >

Install some 3rdparty packages needed for building Mesos modules

Hi All, I wanted to get your opinion on installing the 3rdparty packages glog, protobuf, boost and picojson[1] when installing Mesos itself. These packages are required to build Mesos modules. Currently, a module write has to manually install these 3rdparty packages, either system-wide or

Re: Install some 3rdparty packages needed for building Mesos modules

On Tue, Jan 19, 2016 at 11:58 PM, James Peach <jor...@gmail.com> wrote: > >> On Jan 19, 2016, at 2:03 PM, Kapil Arya <ka...@mesosphere.io> wrote: >> >> Hi All, >> >> I wanted to get your opinion on installing the 3rdparty packages glog, >> pr

Re: Install some 3rdparty packages needed for building Mesos modules

n has not a standard package, so we can include it in Mesos. > But for others, I prefer to let users install them when they need. > > > Thanks, > Zhiwei > > On Wed, Jan 20, 2016 at 6:03 AM, Kapil Arya <ka...@mesosphere.io> wrote: > >> Hi All, >> >> I

Re: Install some 3rdparty packages needed for building Mesos modules

ability as they get out-of-sync whenever a 3rdparty component is updated in Mesos :-/. > > My 2c. > > -- > *Marco Massenzio* > http://codetrips.com > > On Tue, Jan 19, 2016 at 10:22 PM, Kapil Arya <ka...@mesosphere.io> wrote: > >> On Tue, Jan 19, 2016 at 11:58

Re: Add JIRA ticket# to `TODO`s in comments

in the code, there are TODO’s which are no relevant anymore or > > > probably cannot be understood from their actual context. > > > > > > > On 08 Nov 2015, at 05:50, Kapil Arya <ka...@mesosphere.io> wrote: > > > > > > > > Folks, > >

Add JIRA ticket# to `TODO`s in comments

Folks, I wanted to bring up a style issue related to the TODO tag in comments. I have filed a Jira ticket (https://issues.apache.org/jira/browse/MESOS-3850) with the following description: Currently, we have a TODO() tags to note stuff has "should be"/"has to be" done in future. While this

Re: Mesos Style Guideline Adjustments

As far as setting a soft limit goes, I think there are several different style guides and it basically boils down to personal preferences as well. The Linux `fmt` command wraps by 75 columns by default; others use 72 or as extreme as 60 columns. Having said that, it's nice to have tools that

Re: Proposal: move towards #pragma and away from #include guards

+1. I think we should do it all at once as Artem mentioned. This doesn't really affect the history (git-blame, etc.) because we are not touching code per se. On Thu, Nov 5, 2015 at 12:29 PM, Artem Harutyunyan wrote: > Hi Alex, > > While I agree with the idea in general, I

Re: Welcome Kapil as Mesos committer and PMC member!

il! > > > > On Thu, Nov 5, 2015 at 2:02 AM, Till Toenshoff <toensh...@me.com> wrote: > > > > > I'm happy to announce that Kapil Arya has been voted a Mesos committer > > and > > > PMC member! > > > > > > Welcome Kapil, and thanks for

Re: Backticks in comments

+1 for backticks. Also allows us to differentiate ordinary string literals like names, etc., from code. On Mon, Nov 2, 2015 at 2:18 PM, Marco Massenzio wrote: > +1 > > I much favor using backticks everywhere for consistency, since (as you > correctly pointed out) our

Re: Community Sync Interval

+1 for bi-weekly. On Thu, Oct 15, 2015 at 4:40 PM, Jan Schlicht wrote: > +1 for weekly. > > On Thu, Oct 15, 2015 at 1:36 PM, Artem Harutyunyan > wrote: > > > +1 for weekly. > > > > On Thu, Oct 15, 2015 at 10:41 AM, haosdent wrote: >

Re: [VOTE] Release Apache Mesos 0.25.0 (rc3)

+1 (non-binding) On Sat, Oct 10, 2015 at 9:58 AM, Joris Van Remoortere wrote: > +1 (binding) > > On Fri, Oct 9, 2015 at 5:36 PM, Niklas Nielsen > wrote: > > > Hi all, > > > > Following up with an RC with the build fix suggested by Kapil: > > > >

Re: custom(ized) conteinerization

On Sat, Oct 10, 2015 at 2:38 AM, Timothy Chen wrote: > As Ben said containierizers don't conflict since the framework specifies > which containerizer the task should be launched from. > > And isolators are not configurable per task but per slave, so all tasks > will use the

Re: Proposal: moving Mesos website to project codebase

+1 On Fri, Oct 9, 2015 at 1:02 PM, Niklas Nielsen wrote: > +1 > > On 9 October 2015 at 09:50, Yan Xu wrote: > > > +1 for making it easier for contributors to understand the website code > and > > collaboratively maintain it! > > > > -- > > Jiang Yan Xu

Re: Removing external containerizer from code base

On Thu, Oct 8, 2015 at 1:57 PM, Jie Yu wrote: > Alex, > > Implementing your own containerizer totally makes sense. The containerizer > interface can be modulized and your own containerizer can be implemented as > a module. Please take a look at the module documentation >

Re: Removing external containerizer from code base

On Thu, Oct 8, 2015 at 2:19 PM, Jie Yu wrote: > Alex, > > but I don't see 'containerizer' as one of the supported module types listed > > in the documentation.. Can you, please, clarify? > > > Not right now, but should be very trivial to do. Kapil or I can definitely > help

Re: [VOTE] Release Apache Mesos 0.25.0 (rc2)

-1 (non-binding) Compilation fails on OpenSUSE Tumbleweed (Linux 4.1.6, gcc 5.1.1, glibc 2.22) with the following errors: [Created Issue: https://issues.apache.org/jira/browse/MESOS-3603] In file included from ../../src/tests/values_tests.cpp:22:0:

Re: Failed to build Mesos module

n not find picojson.h. And I checked the source code tree of > > Mesos, and found picojson as a 3rd party lib are here: > > mesos/3rdparty/libprocess/3rdparty/picojson-4f93734.tar.gz, maybe we > should > > put the picojson.h to /usr/local/include during "make install&qu

Re: Failed to build Mesos module

Hello Qian, Please follow the instructions on https://github.com/mesos/modules to get up and running with building a mesos module. Apparently, building mesos modules requires you to build Mesos without bundled protobuf, glog and boost libraries. Thus, you need to have them installed system wide.

Re: [Mesos][Patch] How to make the patches under review board link to a mesos bug

You need to click on the pencil icon near Bugs: and type in the Jira ticket number, e.g. MESOS-1234. You can do this only if you are logged in into Reviewboard and have created the review request yourself. Kapil PS: The dev list doesn't allow images, so if you had attached any, they were

Re: Update minimum required automake version to 1.13

/distro to upgrade automake. Is this a reasonable things to do/ask for? Kapil On Fri, Jun 26, 2015 at 4:24 PM, James Peach jor...@gmail.com wrote: On Jun 25, 2015, at 11:01 PM, Kapil Arya ka...@mesosphere.io wrote: On Fri, Jun 26, 2015 at 1:38 AM, Benjamin Mahler benjamin.mah...@gmail.com

Re: Update minimum required automake version to 1.13

= :-). Kapil On Thu, Jun 25, 2015 at 4:10 PM, Kapil Arya ka...@mesosphere.io wrote: Apparently, there is a way to get latest the autotools on CentOS 5 through the same community that provides devtoolset: https://www.softwarecollections.org/en/scls/praiskup/autotools/ If the tools

Update minimum required automake version to 1.13

Hi All, First off, I am not sure if we record the minimum required version of automake/autoconf somewhere in the documentation. Having said that, I want to propose to move to automake 1.13 in order to be able to use the AM_EXTRA_RECURSIVE_TARGETS macro which allows us to add a test target to

Re: Update minimum required automake version to 1.13

://en.wikipedia.org/wiki/CentOS#End-of-support_schedule Also, how does this interact with the effort to use CMake? https://issues.apache.org/jira/browse/MESOS-898 On Thu, Jun 25, 2015 at 10:40 AM, Kapil Arya ka...@mesosphere.io wrote: Hi All, First off, I am not sure if we record

Re: Update minimum required automake version to 1.13

). On Thu, Jun 25, 2015 at 3:17 PM Kapil Arya ka...@mesosphere.io wrote: It's not available for CentOS 5/6 or the previous debian stable. I guess since we still want to keep supporting the older distros, one possibility is to create a patch for configure.ac which is applied during

Re: Enabling 'network' namespace for custom network isolators

if no one has any objections. Best, Kapil [1]. https://issues.apache.org/jira/browse/MESOS-2884 [2a]. https://reviews.apache.org/r/35585/ [2b]. https://reviews.apache.org/r/35586/ On Mon, May 11, 2015 at 7:42 PM, Niklas Nielsen nik...@mesosphere.io wrote: (inlined) On 11 May 2015 at 14:30, Kapil

Re: Enabling 'network' namespace for custom network isolators

On Mon, May 11, 2015 at 4:29 PM, Ian Downes idow...@twitter.com.invalid wrote: TLDR: We want to use a custom network isolator, but there is no way to enable the 'network' namespace from within an isolator module. We are working on creating a custom network isolator as a Mesos module.

Re: Enabling 'network' namespace for custom network isolators

On Mon, May 11, 2015 at 4:58 PM, Jie Yu yujie@gmail.com wrote: Yes. The simplest (cleanest?) way that I see would be to refactor the launcher to take the desired flags when executing the executor, i.e., (Linux)Launcher::fork() takes the namespace flags. The launcher would be

Enabling 'network' namespace for custom network isolators

Hi All, TLDR: We want to use a custom network isolator, but there is no way to enable the 'network' namespace from within an isolator module. We are working on creating a custom network isolator as a Mesos module. However, the way Mesos Slave is setup, there is no way to enable 'network'

Re: Review Request 29947: Fixed a race condition in hook tests for remove-executor hook.

: https://reviews.apache.org/r/29947/diff/ Testing --- make check Thanks, Kapil Arya

  1   2   3   4   5   6   7   8   9   >