Re: Backport r/44230 to 0.27 branch

On Tue, Mar 15, 2016 at 2:39 PM, Jie Yu wrote: > Mesos currently has no notion of long term stable releases (i.e., LTS). I > think the consensus in the last community sync was to introduce LTS after > 1.0. You don't need LTS as kernel, even talking about short term stable

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

+1 (binding) Tested on ASF CI (ubuntu 14.04 w/ gcc and clang). On Wed, Mar 16, 2016 at 6:07 PM, Vinod Kone wrote: > > On Wed, Mar 16, 2016 at 5:59 PM, Daniel Osborne < > daniel.osbo...@metaswitch.com> wrote: > >> Is this issue a blocker? Are we moving to rc3 or proceeding

Re: Backport r/44230 to 0.27 branch

I understand your frustration. I am curious what review/ticket are you talking about, and who is the shepherd for your review/ticket? Mesos project has a clear guide how to contribute to the project, that's what the community has agreed on:

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: [RESULT][VOTE] Release Apache Mesos 0.27.2 (rc1)

On Wed, Mar 16, 2016 at 11:56 AM, Joseph Wu wrote: > Cong Wang, > > The tags are sync'd. See: https://github.com/apache/mesos/releases > > You might not have done: git pull --tags Yeah, I figured it out by myself too. This is why I hate tags personally, branches are

Re: Backport r/44230 to 0.27 branch

On Wed, Mar 16, 2016 at 11:57 AM, Zameer Manji wrote: > Cong brings up a good point here. Currently Mesos has a very aggressive > release cadence. This results in several questions as a cluster operator > and framework author. > >- What is the support from the

Re: Unzip should work in non interactive mode

I can shepherd it. Do you have a patch ready? - Jie On Fri, Mar 18, 2016 at 3:13 AM, Tomek Janiszewski wrote: > Hi > > Consider situation when deployed zip file is malformed and contains > duplicated files . > When fetcher downloads malformed zip file, that contains

Re: Looking for a shepherd for MESOS-4878

Shuai, thanks for the patch. Taking a look at it now. On Thu, Mar 17, 2016 at 8:30 PM, Shuai Lin wrote: > Ping. > > > On Thu, Mar 10, 2016 at 3:55 PM, Shuai Lin wrote: > >> The bug is: if a framework launches a task with mesos containerizer and a

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

On Wed, Mar 16, 2016 at 5:59 PM, Daniel Osborne < daniel.osbo...@metaswitch.com> wrote: > Is this issue a blocker? Are we moving to rc3 or proceeding with 0.28.0? > It was not marked as such, so I'm guessing not. @Jie and @Zhitao, can you confirm? Also, we still need some binding votes for this

Re: Vote on #MesosCon proposals, deadline Friday March 25

Hi Jay, Thanks for your feedback! The reason we're asking for you to rank the topics is that this will allow us to better understand everyone's relative preferences--next, we'll use standard voting algorithms to determine the schedule, to ensure most people get as many talks they want as

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

On Wed, Mar 16, 2016 at 11:49 AM, Cong Wang wrote: > On Mon, Mar 7, 2016 at 8:29 PM, Michael Park wrote: >> Please find the release at: >> https://dist.apache.org/repos/dist/release/mesos/0.27.2 >> >> It is recommended to use a mirror to download the

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

Jake - i think that would be wonderful! On Thu, Mar 17, 2016 at 11:17 AM, Jake Farrell wrote: > I've been maintaining a deb/rpm set for Mesos and for Aurora and Thrift we > have been using the infra supported Bintray to make it available to the > community via

Re: Contributor request

Hi Vinod has already added me and I successfully assigned to MESOS-3243. Thanks Tomek czw., 17 mar 2016, 00:45 użytkownik Artem Harutyunyan napisał: > Hi Tomek, > > Sorry for the delay. Just tried to add you but couldn't find you. Which > email did you use

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

Is this issue a blocker? Are we moving to rc3 or proceeding with 0.28.0? Sorry if this is a silly question, a bit new to the release / voting process. Best, -Dan From: Zhitao Li [mailto:zhitaoli...@gmail.com] Sent: Tuesday, March 15, 2016 8:15 AM To: Jörg Schad Cc:

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

I like the idea of using branches to manage releases. We can use that to manage point releases and backports as well. Say we want to cut 0.29.0 now, we fork a branch 0.29.0 and tag RCs in that branch. Once the RC is accepted, the head of that branch will become the release. Then, we immediate

Re: Backport r/44230 to 0.27 branch

On Wed, Mar 16, 2016 at 5:19 PM, Vinod Kone wrote: > Cong, I understand your frustration with the review process and backports. > I've already created a ticket to track the latter. Would love your > input/feedback on it. > > Regarding the former, we understand the pain. Our

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

Cong Wang, The tags are sync'd. See: https://github.com/apache/mesos/releases You might not have done: git pull --tags On Wed, Mar 16, 2016 at 11:49 AM, Cong Wang wrote: > On Mon, Mar 7, 2016 at 8:29 PM, Michael Park wrote: > > Please find the

0.28.1

Hi, We recently noticed two bugs in 0.28.0 related to the unified containerizer: Because of that, I propose we cut a point release (0.28.1) once these

Re: [DISCUSS] Fetching Docker Images Requiring User Credentials.

This might be a bit far fetched, but does it make sense to associate these credential configurations with roles? Roles identify the capability of frameworks in obtaining resources so was wondering if we can use the same capability to distinguish (and control access) to credentials ? On Wed, Mar

Re: Backport r/44230 to 0.27 branch

On Wed, Mar 16, 2016 at 11:58 AM, Jie Yu wrote: > > Currently, it's based on request. We definitely need to improve this part. It simply doesn't work, like many other review requests are burned or take 6+ months to merge. I am sure you need to improve that too, but after

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

Thanks for the hard work! Do we need to backport the rmdir fixes on the outstanding release candidates? commit 5278e5cc50544ed7af28b15a1acd2b2e96a15a47 Author: Jojy Varghese Date: Tue Mar 15 17:12:01 2016 -0700 Added support for FTS_SLNONE in rmdir. Review:

Re: Looking for shepherd (MESOS-4355 - Docker Volume Isolator)

Guangya, I'd be happy to shepherd this work if no other committers volunteer for this work. - Jie On Thu, Mar 17, 2016 at 6:05 AM, Guangya Liu wrote: > Hi, > > I was now working on the FS for MESOS-4355 with some EMC guys, can anyone > help shepherd for this? There are some

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

+1 @vinodkone > On Mar 17, 2016, at 11:27 AM, Bill Farner wrote: > > Jake - i think that would be wonderful! > >> On Thu, Mar 17, 2016 at 11:17 AM, Jake Farrell wrote: >> I've been maintaining a deb/rpm set for Mesos and for Aurora and Thrift we >>

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

On Mon, Mar 7, 2016 at 8:29 PM, Michael Park wrote: > Please find the release at: > https://dist.apache.org/repos/dist/release/mesos/0.27.2 > > It is recommended to use a mirror to download the release: > http://www.apache.org/dyn/closer.cgi > > The CHANGELOG for the release is

Re: Backport r/44230 to 0.27 branch

On Wed, Mar 16, 2016 at 2:21 PM, Jie Yu wrote: > I understand your frustration. I am curious what review/ticket are you > talking about, and who is the shepherd for your review/ticket? Why not check your backlog for your answer? Or do you need me to write a script to scan

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

The project itself doesn't officially release rpms/debs, but the community members do. For example, Mesosphere is planning to release rpms/debs shortly. On Thu, Mar 17, 2016 at 10:38 AM, craig w wrote: > Great news. Do the rpm's get automatically built and released or will

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

These are be captured under: https://issues.apache.org/jira/browse/MESOS-4979 On Thu, Mar 17, 2016 at 5:04 PM, Benjamin Mahler wrote: > Thanks for the hard work! Do we need to backport the rmdir fixes on the > outstanding release candidates? > > commit

Re: Backport r/44230 to 0.27 branch

Formalizing Mesos release strategy and support is something that I've been thinking about a lot lately. In my mind, this is a blocker for Mesos reaching 1.0. I've filed https://issues.apache.org/jira/browse/MESOS-4962 to track this work and added it to our current sprint; hopefully I/we can come

Re: RFC: RevocableInfo Changes

Thanks for the good explanations so far Ben and Klaus. Apologies if you guys already covered these questions in the meeting: If throttling is tolerable but preemption is not, how would that be expressed? (Is that supported?) How does this work with the QoS controller? Will there be a new

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

I don't think it's a blocking issue after some initial investigation. Changing my vote to +1 (nonbinding) On Wed, Mar 16, 2016 at 6:07 PM, Vinod Kone wrote: > > On Wed, Mar 16, 2016 at 5:59 PM, Daniel Osborne < > daniel.osbo...@metaswitch.com> wrote: > >> Is this issue a

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

Ben, Do I understand correctly that this is not a regression, but a fix important enough for us to backport? I'm curious as to what makes it significant. Could you elaborate a little as to what the consequences are? Thanks! MPark On 18 March 2016 at 16:20, Benjamin Mahler

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

As there are insufficient votes on this rc along with a request from Evan Krall to include additional fixes: https://www.mail-archive.com/user@mesos.apache.org/msg06205.html, I'm declaring this rc failed, and will cut be cutting an rc3 early next week. Thanks, MPark On 13 March 2016 at 20:57,

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

+1 (binding) Tested on ASF CI. On Sun, Mar 13, 2016 at 4:33 PM, Michael Park wrote: > +1 (binding) > > Internal CI results with the corresponding JIRA tickets for the failed > tests: > > CentOS 6 (non-SSL): > -

Possibility to work on Apache Mesos for GSoC 2016

Hi, I'm Milindu Sanoj Kumarage, an undergraduate of University of Colombo School of Computing doing my 4th year of Computer Science major. I have just started my 4th year and I am working on a research base on distributed computing( on Pub/Sub ), therefor I'm working with tools and technologies

Re: Backport r/44230 to 0.27 branch

Cong, I understand your frustration with the review process and backports. I've already created a ticket to track the latter. Would love your input/feedback on it. Regarding the former, we understand the pain. Our use of shepherds is a way to tackle the problem. While it's not perfect it has

Re: RFC: RevocableInfo Changes

Also please show your comments if any for the name here, the current name is *ThrottleInfo*, in Kubernetes resources qos design document, they are using scavenging as the key work for such behaviour, so a possible name here could be *ScavengeInfo , *please show your comments if any for those

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

Hi all, The vote for Mesos 0.28.0 (rc2) has passed with the following votes. +1 (Binding) -- Vinod Kone Michael Park Kapil Arya +1 (Non-binding) -- Greg Mann Daniel Osborne Jorg Schad Zhitao Li There were no 0 or -1 votes.

Looking for shepherd (MESOS-4355 - Docker Volume Isolator)

Hi, I was now working on the FS for MESOS-4355 with some EMC guys, can anyone help shepherd for this? There are some issues need to discuss with the shepherd. Thanks, Guangya

Re: Recent changes to MesosTest helpers

We tried to reduce segfaults of this particular pattern (de-referencing out-of-scope stack variables), as much as possible. This means the test suite shouldn't crash due to flaky tests anymore. And the test suite should run to completion each time. (I also replaced a bunch of CHECK_* statements

Re: RFC: RevocableInfo Changes

@team, in the latest meeting, we agree to keep current name *ThrottleInfo.* If any more comments, please let me know. On Wednesday, March 16, 2016 at 9:32:37 PM UTC+8, Guangya Liu wrote: > > Also please show your comments if any for the name here, the current name > is *ThrottleInfo*, in

Re: Backport r/44230 to 0.27 branch

On Wed, Mar 16, 2016 at 2:50 PM, Jie Yu wrote: >> >> Why not check your backlog for your answer? Or do you need me to write >> a script to scan all the pending review requests for you? > > > OK, i just looked at your pending patches: >

RE: Upgrade to clang-format-3.8

> Subject: Re: Upgrade to clang-format-3.8 > From: jor...@gmail.com > Date: Fri, 18 Mar 2016 09:45:22 -0700 > To: dev@mesos.apache.org > > > > On Mar 17, 2016, at 10:41 AM, Yong Tang > > wrote: > > > > Hi All > > > > > > This email is to announce that the

Compute event at Twitter HQ - 03/31

Hello everyone, I'd like to call attention to an event the Compute group at Twitter is holding at the end of the month where there will be a few Aurora/Mesos-related talks: 1. David Robinson, one of our SREs, will talk about how our small team of SREs manages what is possibly the largest Mesos

Re: Recent changes to MesosTest helpers

Got it, thank you for explanation. On Thu, Mar 17, 2016 at 12:51 AM, Joseph Wu wrote: > We tried to reduce segfaults of this particular pattern (de-referencing > out-of-scope stack variables), as much as possible. This means the test > suite shouldn't crash due to flaky

Re: Recent changes to MesosTest helpers

Does it exit like segment when CHECK_xxx failed? Or exit until finish all test cases? On Mar 16, 2016 11:03 PM, "Joseph Wu" wrote: > Hello Devs & Contributors, > > We recently committed a refactor of the MesosTest suite and underlying > "Cluster" abstraction. This affects

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

I agree with Kevin -- tags are immutable, so they're naturally suited for labeling releases, which ought to be immutable too. 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,

Re: Recent changes to MesosTest helpers

This is awesome! Thanks for working on this. On Wed, Mar 16, 2016 at 9:53 AM, haosdent wrote: > Got it, thank you for explanation. > > On Thu, Mar 17, 2016 at 12:51 AM, Joseph Wu wrote: > > > We tried to reduce segfaults of this particular pattern

Re: Backport r/44230 to 0.27 branch

Cong brings up a good point here. Currently Mesos has a very aggressive release cadence. This results in several questions as a cluster operator and framework author. - What is the support from the community/committers for each release? - Do cluster operators and framework authors need to

Re: Backport r/44230 to 0.27 branch

> > You don't need LTS as kernel, even talking about short term stable releases > like 0.27.2 (?), they look horrible too, I don't see any git tags or > branches for > these releases, just a tar ball?! Huh... Jies-MacBook-Pro:mesos jie$ git tag | grep 0.27 0.27.0 0.27.0-rc1 0.27.0-rc2 0.27.1

Re: shepherd for MESOS-4735, and proposal

Bump. This should be a pretty small change, any takers? On Mon, Mar 14, 2016 at 6:39 PM, Shuai Lin wrote: > +1 for the new `filename` field for the URI. It would also be useful for > implementing base64:// or data:// scheme uri fetcher, so that the scheduler > can pass

Re: Compute event at Twitter HQ - 03/31

Would it have youtube live link? On Thu, Mar 17, 2016 at 12:38 AM, Ian Downes wrote: > Hello everyone, > > I'd like to call attention to an event the Compute group at Twitter is > holding at the end of the month where there will be a few > Aurora/Mesos-related talks: > >

Re: Upgrade to clang-format-3.8

> On Mar 17, 2016, at 10:41 AM, Yong Tang wrote: > > Hi All > > > This email is to announce that the default configuration and the recommended > version of the clang-format is being upgraded to 3.8 (from 3.5) in mesos. > > > In clang-format-3.8, the newly

Unzip should work in non interactive mode

Hi Consider situation when deployed zip file is malformed and contains duplicated files . When fetcher downloads malformed zip file, that contains duplicated files (e.g., dist zips generated by gradle) and try to uncompress it, deployment hang in staged phase because unzip prompt if file should