Re: [jira] [Updated] (MESOS-3583) Introduce stream IDs in HTTP Scheduler API

> > Until we call them out as ready for production in a release, we are > allowed to make breaking changes. This gives us flexibility to design and > produce a better API. Makes sense, thanks for the info! On Sat, Mar 5, 2016 at 2:02 AM, Vinod Kone wrote: > It was called out in the CHANGELOG u

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

I am seeing the following crash when I run mesos build of 0.28.0-rc1 `sudo bin/mesos-tests.sh` : [ RUN ] MemIsolatorTest/1.MemUsage F0305 02:43:01.791003 32494 isolator_tests.cpp:905] CHECK_SOME(isolator): Failed to create memory cgroup: Failed to mount cg roups hierarchy at '/sys/fs/cgroup/me

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

Sorry, Forgot to mention the platform details. Seeing the crash on Debian 8 dmin@ip-172-31-26-151:~/mesos/build$ cat /etc/issue Debian GNU/Linux 8 \n \l admin@ip-172-31-26-151:~/mesos/build$ uname -a Linux ip-172-31-26-151 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 GNU/

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 fine in the CHANGELOG.

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

+1 (binding) Greg's upgrade scripts & CI results The missing commit is for a flaky test which doesn't influence the production binaries. Unless we need to cut another RC for a bug, I suggest we move ahead. On Wed, Mar 2, 2016 at 10:36 AM, Jörg Schad wrote: > Except the missing fix for Mesos-451

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

+1 (binding) On Mon, Feb 29, 2016 at 3:24 PM, Greg Mann wrote: > +1 (non-binding) > > `sudo make check` on Ubuntu 14.04, using gcc with libevent and SSL enabled. > All tests pass except MemoryPressureMesosTest.CGROUPS_ROOT_Statistics, > which is a known failure in 0.24. > > Cheers, > Greg > > >

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

+1 (binding) Greg's upgrade scripts & CI results On Tue, Mar 1, 2016 at 4:37 PM, Greg Mann wrote: > I was also able to successfully test a simple upgrade scenario between > 0.24.2-rc1 and 0.25.1-rc1 using Niklas's upgrade testing script, which I've > modified slightly and reposted here: https://

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

+1 (binding) Greg's upgrade scripts & CI results On Fri, Mar 4, 2016 at 11:30 AM, Vinod Kone wrote: > +1 (binding) > > On Tue, Mar 1, 2016 at 5:03 PM, Kevin Klues wrote: > > > I committed a fix for this in: > > > > > https://github.com/apache/mesos/commit/42f746937233349660c687ea7a66cc0a7887166

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

Steven, sorry about the delay. I'll finish the doc today. On Fri, Mar 4, 2016 at 10:29 AM, Steven Schlansker < sschlans...@opentable.com> wrote: > > > On Mar 3, 2016, at 5:43 PM, Vinod Kone wrote: > > > > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 0.28.0. > > 0.

Re: Making 'curl' a prerequisite for installing Mesos

Thanks for the feedback, guys! I think we all agree that using libcurl is the ideal solution. I've already created a ticket for this: https://issues.apache.org/jira/browse/MESOS-4853 Currently, only docker/appc image puller is using 'curl' directly. I guess it's not a problem on Windows yet. Bas

Re: Making 'curl' a prerequisite for installing Mesos

I also have my doubts about this idea. Given that we support some legacy systems and the user interface tends to be less stable than an API (though comparing the flags between curl 7.38.0 in Debian 8 and curl 7.19.7 in CentOS 6.7, I don’t see a lot of differences in the important ones). So I gu

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

+1 (binding) On Tue, Mar 1, 2016 at 5:03 PM, Kevin Klues wrote: > I committed a fix for this in: > > https://github.com/apache/mesos/commit/42f746937233349660c687ea7a66cc0a78871663 > > Looks like that's post 0.26 though, so maybe it should be included in the > .1 rc > > On Mon, Feb 29, 2016 at 2

Re: Contributor request

Done. Welcome! On Fri, Mar 4, 2016 at 10:52 AM, Rob Todd wrote: > Hello all, > Please add me as a contributor in the Mesos JIRA project. Apache JIRA > username: rtodd > > Thanks! > > > --- > This email message is for

Contributor request

Hello all, Please add me as a contributor in the Mesos JIRA project. Apache JIRA username: rtodd Thanks! --- This email message is for the sole use of the intended recipient(s) and may contain confidential informati

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

I will rename mesos-provisioner.md -> container-image.md, and do some re-writing. - Jie On Fri, Mar 4, 2016 at 10:35 AM, Jie Yu wrote: > I am writing that as you speaking > > On Fri, Mar 4, 2016 at 10:34 AM, Vinod Kone wrote: > >> I think this was supposed to refer to >> https://github.com/apa

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

I am writing that as you speaking On Fri, Mar 4, 2016 at 10:34 AM, Vinod Kone wrote: > I think this was supposed to refer to > https://github.com/apache/mesos/blob/master/docs/mesos-containerizer.md > > @Jie ^^ ? > > On Fri, Mar 4, 2016 at 10:29 AM, Steven Schlansker < > sschlans...@opentable.co

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

I think this was supposed to refer to https://github.com/apache/mesos/blob/master/docs/mesos-containerizer.md @Jie ^^ ? On Fri, Mar 4, 2016 at 10:29 AM, Steven Schlansker < sschlans...@opentable.com> wrote: > > > On Mar 3, 2016, at 5:43 PM, Vinod Kone wrote: > > > > Hi all, > > Please vote on r

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

Bad copy paste into the email, sorry. It looks fine in the CHANGELOG. On Fri, Mar 4, 2016 at 12:52 AM, Shuai Lin wrote: > * [MESOS-4712] - Remove 'force' field from the Subscribe Call in v1 >> Scheduler API. >> * [MESOS-4591] - Change the object of ReserveResources and CreateVolume >> ACLs t

Re: [jira] [Updated] (MESOS-3583) Introduce stream IDs in HTTP Scheduler API

It was called out in the CHANGELOG under Additonal API Changes. Both the scheduler v1 API and executor v1 API are considered (and called out as) experimental. Until we call them out as ready for production in a release, we are allowed to make breaking changes. This gives us flexibility to design an

Re: [jira] [Updated] (MESOS-3583) Introduce stream IDs in HTTP Scheduler API

I don't think there are currently any frameworks using the HTTP API? But you have a good point, it's a breaking change to the API, so it's probably worth calling it out prominently. On Fri, Mar 4, 2016 at 12:58 AM, Shuai Lin wrote: > If I understand it correctly, this change would break all exis

Re: Performance isolation working group meeting: March 4th 2016

Apologies, but I'm still on the bus in traffic so I expect to be ~10 minutes late. On Fri, Mar 4, 2016 at 8:23 AM, Ian Downes wrote: > Please let me know directly if anyone is attending at Twitter as I need to > advise security. > > Ian > > On Fri, Mar 4, 2016 at 12:51 AM, wrote: > >> Hi Vipin,

Re: Performance isolation working group meeting: March 4th 2016

Please let me know directly if anyone is attending at Twitter as I need to advise security. Ian On Fri, Mar 4, 2016 at 12:51 AM, wrote: > Hi Vipin, > > We'll share the hangout in the agenda doc ( > https://docs.google.com/document/d/11mlGPZSABItP47J6VX-zB0fAK6Qr1mCIOI7nhlATMqk/edit#) > and also

Re: [jira] [Updated] (MESOS-3583) Introduce stream IDs in HTTP Scheduler API

If I understand it correctly, this change would break all existing frameworks that use the http scheduler api, should we include a notice for it in the release note? On Fri, Mar 4, 2016 at 5:48 AM, Vinod Kone (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/MESOS-3583?page=com.at

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

> > * [MESOS-4712] - Remove 'force' field from the Subscribe Call in v1 > Scheduler API. > * [MESOS-4591] - Change the object of ReserveResources and CreateVolume > ACLs to `roles`. > * [MESOS-4712] - Remove 'force' field from the Subscribe Call in v1 > Scheduler API. MESOS-4712 is included

Re: Performance isolation working group meeting: March 4th 2016

Hi Vipin, We'll share the hangout in the agenda doc (https://docs.google.com/document/d/11mlGPZSABItP47J6VX-zB0fAK6Qr1mCIOI7nhlATMqk/edit#) and also announce in the Mesos IRC channel. Just be patient around meeting start time; last week we began about 10 minutes late. -- Connor Sent from my i

Re: Performance isolation working group meeting: March 4th 2016

Hi Daniel, Is three a hangout/online details for this meeting? I would really like to attend. Thanks, -Vipin From: daniel.osbo...@metaswitch.com When: 9:00 AM - 9:30 AM March 4, 2016 Subject: Performance isolation working group meeting: March 4th 2016 The

Re: GSoC query

I could found some past gsoc ideas in mesos, maybe you could have a look first. https://issues.apache.org/jira/browse/MESOS-1016?jql=project%20%3D%20MESOS%20AND%20text%20~%20gsoc And I not sure whether Mesos take parts in GSOC this year or not. You may join our next community sync (March 10, 9pm –