Re: Review Request 30961: Enabled label decorator to override.

/r/30961/diff/ Testing --- make check (with modified VerifyMasterLaunchTaskHook test) Thanks, Niklas Nielsen

Re: Review Request 30962: Enabled environment decorator to override.

src/hook/manager.cpp 7a4cb09bc221af502e867cfb7fff2900b599ff1f Diff: https://reviews.apache.org/r/30962/diff/ Testing --- make check Thanks, Niklas Nielsen

Re: Review Request 31028: Added slave run task hook tests.

: https://reviews.apache.org/r/31028/diff/ Testing --- make check (with newly added VerifySlaveRunTaskHook test) Thanks, Niklas Nielsen

Review Request 32948: Refactored VerifyMasterLaunchTaskHook to _not_ use command executor.

, Niklas Nielsen

Re: Review Request 31017: Fixed comment for remove executor hook.

. Changes --- rebased Repository: mesos Description --- See summary. Diffs (updated) - include/mesos/hook.hpp 9ae8b9455a86c7a5cbf4f1d1b1ce88f2811ce35d Diff: https://reviews.apache.org/r/31017/diff/ Testing --- make check Thanks, Niklas Nielsen

Re: Review Request 30961: Enabled label decorator to override.

--- On April 7, 2015, 5:57 p.m., Niklas Nielsen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30961

Re: Review Request 30961: Enabled label decorator to override.

--- On April 7, 2015, 5:57 p.m., Niklas Nielsen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30961

Re: Review Request 31016: Added slave run task decorator.

. To reply, visit: https://reviews.apache.org/r/31016/#review78193 --- On April 7, 2015, 5:57 p.m., Niklas Nielsen wrote: --- This is an automatically generated e-mail. To reply

Re: Review Request 31016: Added slave run task decorator.

)? This would prevent future developers from accidentally using `task` when they meant to use `task_`. Doing the label decoration before the error checks has an added benefit of generating notifications for dropped tasks as well for the hook modules. Niklas Nielsen wrote

Re: Review Request 32948: Refactored VerifyMasterLaunchTaskHook to _not_ use command executor.

be used with a command executor) Thanks, Niklas Nielsen

Re: Suggestion: Mesos 0.22.1 point release

generate some JIRA noise - I apologize in advance. Niklas On 3 April 2015 at 13:52, Niklas Nielsen nik...@mesosphere.io wrote: Hi everyone, I think we have everything for the point release now: https://docs.google.com/a/mesosphere.io/spreadsheets/d/1OzAWNjAL4zKtI-jOJqaQUcDNlnrNik2Dd7dHhwFLKcI

Re: Shepherd for MESOS-2637

I can help you out. On 5 June 2015 at 09:51, Colin Williams lack...@gmail.com wrote: Can I get a shepherd for https://issues.apache.org/jira/browse/MESOS-2637 ? It's been completed for a while and I think I've addressed all of the concerns raised. Thanks, Colin

Re: Native code error

regards, 2015-06-03 19:36 GMT+02:00 Niklas Nielsen nik...@mesosphere.io: Hi Alberto, Can you share the full crash report with us? Niklas On 2 June 2015 at 02:37, Alberto Rodriguez ardl...@gmail.com wrote: Hi all, I've got a bunch of tests that are checking whether my spark process

Re: Regarding old frameworks in Mesos repository

On 24 June 2015 at 10:55, Yan Xu y...@jxu.me wrote: If we anticipated further development we wouldn't have proposed moving them out. :) So I think it's safe to say that we are just looking for a graveyard for them. Do the policies still apply? That said, if they cannot be moved out, we

Re: Native code error

Hi Alberto, Can you share the full crash report with us? Niklas On 2 June 2015 at 02:37, Alberto Rodriguez ardl...@gmail.com wrote: Hi all, I've got a bunch of tests that are checking whether my spark process is able to connect to a mesos cluster. The happy path (mesos up running) is

Re: Why does allocator keep track of the revocable resources separately from regular resources

Hi Qian, Yes; frameworks will have to: 1) Register with the revocable resources framework capability set; the important bit here, is that frameworks running on oversubscribed resources will have to cope with frequent preemptions of their tasks. We wanted to gain experience with this

Re: Add klaus1982 as contributor for MESOS-3023

You should have been added by now On 14 July 2015 at 09:12, kl...@cguru.net wrote: Hi team, I'm working on MESOS-3023 (Factoring out the pattern for URL generation), and have a fix for it; would you help to add me into contributor list? so I can assign it to myself and trigger review

Re: Why does allocator keep track of the revocable resources separately from regular resources

On 16 August 2015 at 02:56, Qian AZ Zhang zhang...@cn.ibm.com wrote: Thanks Niklas and Christos. To Niklas, we'd like to try oversubscription feature with our framework. However, I do not quite understand your example below: For example: cpus: 0.5; cpus{REV}: 1.89; mem: 512. Here,

Re: NetworkInfo change - MESOS-3788

how multiple IP addresses might or might not > be assigned to multiple virtual network interfaces. Would you get one > interface with several IP addresses, or several interfaces with an IP > address each? > > How do we fix it? > > We've collaborated with Ben Hi

Notes from off-line sync on processes for Mesos road maps

Hi everyone, Yesterday, a few of us met up to discuss processes for Mesos road maps: how to capture core values of the project, how to prioritize features from users running different workloads and how to delegate specifics of road mapping to the working groups. The meeting notes are available

Re: Finish Oversubscription before 0.26.0?

Nope - go ahead and close On Thu, Nov 5, 2015 at 10:24 AM, Jie Yu wrote: > I would say the MVP is done. Of course, there'll be some followup > improvement to the feature, and all the remaining issues are within that > category. I am fine resolving this epic. Any one has any

Re: Contribution Request for Mesos

Hi Yong, You should be on the list now. Looking forward to your contributions! Niklas On 14 October 2015 at 12:29, Yong Tang wrote: > Hi > After using Mesos and following Mesos project for quite some time, I would > like to participate and contribute to the

[RESULT][VOTE] Release Apache Mesos 0.25.0 (rc3)

Hi all, The vote for Mesos 0.25.0 (rc3) has passed with the following votes. +1 (Binding) -- Joris Van Remoortere Michael Park Brenden Matthews +1 (Non-binding) -- Kapil Arya There were no 0 or -1 votes. Please find the

Re: Patch for the website's Rakefile

I can help out; Where can I find the patch? Niklas On 4 October 2015 at 12:31, Dave Lester wrote: > If anyone is attending MesosCon Europe this upcoming week and would like > to make enhancements here I should be available and could pair. There's > lots of low-hanging

[VOTE] Release Apache Mesos 0.25.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.25.0. 0.25.0 includes the following: * [MESOS-1474] - Experimental support for maintenance primitives. * [MESOS-2600] - Added master

[VOTE] Release Apache Mesos 0.25.0 (rc3)

Hi all, Following up with an RC with the build fix suggested by Kapil: Please vote on releasing the following candidate as Apache Mesos 0.25.0. 0.25.0 includes the following: * [MESOS-1474] - Experimental

Re: Proposal: moving Mesos website to project codebase

+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 @xujyan > > On Fri, Oct 9, 2015 at 5:21 PM, Paul Brett

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

gt; [17:18:48][Step 4/6] if (expected == actual) { > >> > >> [17:18:48][Step 4/6] ^ > >> > >> > >> Cherry-picking one commit (bfeb070a2aef52f445e "Fixed compiler warning

Mesos 0.25.0

Hi folks, While we have 0.24.0 in flight (voting and fixing is in progress), with a release cadence of 1 month, we should consider to start thinking about 0.25.0. I have cycles to release manage this one (and bring some of the newer committers on for shadowing). If others want to take this on

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

-1: sudo make check on centos 7 [--] Global test environment tear-down [==] 793 tests from 121 test cases ran. (606946 ms total) [ PASSED ] 786 tests. [ FAILED ] 7 tests, listed below: [ FAILED ] UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup, where TypeParam =

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

, and /lib64 when preparing test root filesystem. Review: https://reviews.apache.org/r/37684 On Thu, Aug 27, 2015 at 3:30 PM, Niklas Nielsen nik...@mesosphere.io wrote: -1: sudo make check on centos 7 [--] Global test environment tear-down [==] 793 tests from 121

Re: Mesos 0.25.0

the beta follow-up features for persistence > > > primitives (dynamic reservation + persistent volume): > > > > > >- Operator API > > >- Authorization > > > > > > Thanks, > > > > > > MPark. > > > > > > On Thu, Aug 2

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

+1 - tested on our CI On Tuesday, September 1, 2015, Vinod Kone wrote: > Hi all, > > > Please vote on releasing the following candidate as Apache Mesos 0.24.0. > > > 0.24.0 includes the following: > > >

Re: Request : Add to contributor list

You should be on the list now :) Niklas On 28 September 2015 at 20:04, Mandeep Chadha < mandeep_cha...@yahoo.com.invalid> wrote: > Thanks in advance ! > Best,Mandeep

Problems with deprecation cycles for critical/hard to adapt dependencies

Hi everyone, With a (targeted) release cadence of *one month*, we should revisit our deprecation cycles of 3 releases (e.g. in version N, we warn. In version N+1, support both old and new API. In Version N+2, we break compatibility). Sometimes we cannot do the first step, and we deprecate in

Re: Problems with deprecation cycles for critical/hard to adapt dependencies

cient time to react to deprecations > while > > still allowing them to move forward at a reasonable pace. > > > > On Mon, Sep 28, 2015 at 2:19 PM, Niklas Nielsen <nik...@mesosphere.io> > > wrote: > > > > > Hi everyone, > > > > > &g

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

+1 (binding) On 1 October 2015 at 20:27, Michael Park wrote: > +1 (binding) > > *make distcheck* passed with the Jenkins Build script with > > *OS=ubuntu:15.04 COMPILER=gcc CONFIGURATION="--enable-optimize" > ./support/jenkins_build.sh* > > On Fri, Sep 25, 2015 at 5:29 PM

Re: Mesos 0.25.0

. Please tag your tickets you want in this release with 0.25.0 target or fix version and we will track the progress of the tickets up to the deadlines. Let us know if this doesn't make sense or if you have any objections. Cheers, Joris, Mpark and Niklas On 31 August 2015 at 11:34, Niklas Nielsen

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

+1 (binding) On 21 September 2015 at 11:46, Vinod Kone wrote: > +1 (binding) > > Tested on CI for CentOS5 and CentOS6. > > On Fri, Sep 18, 2015 at 6:21 PM, Adam Bordelon wrote: > >> Hi friends, >> >> Please vote on releasing the following candidate as

Testing Mesos 0.25.0 RCs

Hi everyone, Mesos 0.25.0 rc1 should now be ready for testing! [1] While we already know of documentation additions we want in RC2, this is our chance to test and bake the release bits. *Please keep us posted with any failures, crashes, flaky test, unintuitive upgrade paths or deprecations we

Re: Testing Mesos 0.25.0 RCs

://dist.apache.org/repos/dist/release/mesos/KEYS The JAR is up in Maven in a staging repository here: https://repository.apache.org/content/repositories/orgapachemesos-1076 On 25 September 2015 at 11:14, Niklas Nielsen <nik...@mesosphere.io> wrote: > Hi everyone, > > Mesos 0.25.0

Re: Mesos 0.25.0

RCs (again, only regressions, test fixes and documentation at this point). Thanks! Mpark, Joris and Niklas On 24 September 2015 at 17:03, Niklas Nielsen <nik...@mesosphere.io> wrote: > Hi everyone! > > We promised to have 0.25.0 RC tagged yesterday and it slipped into thi

Working Group List

Hi folks, Per our last community meeting, I created a list on our Confluence Wiki to keep track of and increase visibility into the running working groups. We have previously created these groups implicitly, and as the community grow, we unfortunately ended up with duplicate meetings with

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

/1d86932c > > > > Branch: refs/heads/master > > Commit: 1d86932ce424f3e7b921cc6a436051a45f704dd0 > > Parents: f6706e8 > > Author: Niklas Nielsen <n...@qni.dk> > > Authored: Wed Sep 23 15:37:21 2015 -0700 > > Committer: Niklas Q. Nielsen <nik...

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

it as it isn't an alternative (yet). Niklas On 23 September 2015 at 16:29, Benjamin Mahler <bmah...@twitter.com.invalid> wrote: > Ok, any plan to add TODOs with this context? > > On Wed, Sep 23, 2015 at 4:11 PM, Niklas Nielsen <nik...@mesosphere.io> > wrote: > > &

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

+1 (binding) Tested on centos7 and ubuntu 14.04 On 24 September 2015 at 07:53, Alexander Rojas wrote: > +1 (non binding) > > Tested Ubuntu 14.04, OSX > > > On 22 Sep 2015, at 03:06, Adam Bordelon wrote: > > > > Hi friends, > > > > Please vote on

Re: Please review design doc for task resizing

Hi Qian, Thanks for the update and I apologize the response time. Do you have a PoC implementation of your proposal? I have trouble understanding the motivation of _not_ adding resizing as a usual operation. It seems much cleaner in my mind. To David G's and Alex R's comment: if you want to

Re: Please review design doc for task resizing

work yet, I'd maybe defer until we at least have the placement of the 'resize operation' nailed down. > > I'd like to have an online sync up with you, can you please let me know > when you will be online in IRC usually? Or you prefer other ways to sync > up? I will try to catch

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

Awesome guys! Kapil, we usually linked to the user documentation in the blog to the new features. Do you have a link to the docs on multiple disk resources? On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya wrote: > And here is the blog post: >

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

user doc for multi-disk support in > > Mesos. > > > > - Jie > > > > On Thu, Feb 4, 2016 at 1:22 AM, Niklas Nielsen <n...@qni.dk> wrote: > > > >> Awesome guys! > >> > >> Kapil, we usually linked to the user documentation in the blog to the &

Re: Performance isolation working group meeting on Friday 10am PST

mail.com> wrote: > > > > > > > > I'm having trouble joining the call. Keeps saying "Requesting to join > > > > the video call..." > > > > > > > >> On Wed, Feb 24, 2016 at 12:12 PM, Niklas Nielsen <n...@qni.dk> >

Performance isolation working group meeting on Friday 10am PST

Hi all, We will meet and talk performance isolation on Friday 10am PST, with the agenda: 1) New proposal for core affinity 2) CFS configuration status 3) Workload Benchmarking 4) Discussion on actuating isolation for resources that are accounted / not accounted by Mesos For now, this will be the

Re: Experimentation harnesses?

Hi Michael, We are working on this in context of generating workloads (with many different combinations of latency critical workloads co-located with best-effort ones) and testing scenarios for oversubscription and would love to chat Cheers, Niklas On Mon, Feb 22, 2016 at 4:14 PM, James Peach

Re: RFC: RevocableInfo Changes

Hi Ben, Just a quick note: Ian D. and the performance isolation working group are discussing similar annotations and we should meet and talk about the options. Niklas On Sat, Mar 12, 2016 at 12:05 AM, Klaus Ma wrote: > Yes, I think that's true for now; so we define

Re: RFC: RevocableInfo Changes

quick note: Ian D. and the performance isolation working group are > > discussing similar annotations and we should meet and talk about the > > options. > > > +1 > > Would love to understand the relationship between this and the > task/executor level annotations. >

Re: RFC: RevocableInfo Changes

Echoing Ben Mahler's comment. I still don't find the ThrottleInfo very intuitive. Did you discuss the general notion of resource quality further? On Mon, Mar 21, 2016 at 11:50 PM, Klaus Ma wrote: > @benm/joris, > > here's the user scenario in my mind: > > 1. master

Re: [Isolation][Containerization] - Add Intel Cache Allocation Technology(CAT) Isolator Support

My gut feeling is that it won't be very useful to expose LLC as a first class resource type at this point. It's very hard to pick for the user and requires framework support everywhere. Also, as Kevin mentioned, Mesos doesn't pin your tasks so you don't know which cores your tasks will be running

Re: [Isolation][Containerization] - Add Intel Cache Allocation Technology(CAT) Isolator Support

is all most ready in Mesos, > that’s all perf stuff. > Check MESOS-4955 and MESOS-4595 for details. Yep - Bartek had a patch for this > > > > > > On 2016/4/5 23:13, Niklas Nielsen wrote: > >> My gut feeling is that it won't be very useful to expose LLC as a first &g

Re: [Isolation][Containerization] - Add Intel Cache Allocation Technology(CAT) Isolator Support

fan...@intel.com> wrote: > 5:00 PM PST time is 8:00 AM on my timezone(UTC + 08:00) > I think time slot after 5:00 PM PST will be ok for me. > > Thanks Nik! > > > On 2016/4/9 6:11, Niklas Nielsen wrote: > >> Alright - with that in mind. Will morning, midday or evening PST b

Re: [Proposal] Use dev mailing list for working groups

SGTM - let's do it :) On Fri, Mar 25, 2016 at 12:44 AM, Jay JN Guo wrote: > +1 > > Although we really need to agree on one single style and stick to it. > > I thought all mails sending to dev@mesos.apache.org would be [MESOS-dev] > by > default. > So I don't know how much

Re: [Performance Isolation] Meeting on Thursday April 21 2016 5pm PST

wrote: > Likewise, I tried calling but no one was hosting the meeting. > > On Fri, Apr 22, 2016 at 10:04 AM, Kevin Klues <klue...@gmail.com> wrote: > > > I tried calling into this last night, but no one was there. Was it > > post-poned again? > > > > On Mon, Apr 1

Re: [Performance Isolation] Meeting on Thursday April 21 2016 5pm PST

Ian, Kevin: Would you be able to dial in this afternoon instead? On Mon, Apr 25, 2016 at 9:00 AM, Niklas Nielsen <n...@qni.dk> wrote: > Hi all, > > I apologize! this was on me: I got stuck in traffic and couldn't dial in > (and accept the external calls). > Do you ha

Re: [Performance Isolation] Meeting on Thursday April 21 2016 5pm PST

We will use the same hangout link: https://hangouts.google.com/hangouts/_/intel.com/isolation?hl=en=1 On Thu, Apr 28, 2016 at 7:30 AM, Niklas Nielsen <n...@qni.dk> wrote: > Ian, Kevin: Would you be able to dial in this afternoon instead? > > On Mon, Apr 25, 2016 at 9:00 AM, Ni

Re: [Performance Isolation] Meeting on Thursday May 12 5pm PST

2:30 AM, Niklas Nielsen <n...@qni.dk> wrote: > > Ian, Kevin: Would you be able to dial in this afternoon instead? > > > > On Mon, Apr 25, 2016 at 9:00 AM, Niklas Nielsen <n...@qni.dk> wrote: > > > >> Hi all, > >> > >> I apologize

Re: [Isolation][Containerization] - Add Intel Cache Allocation Technology(CAT) Isolator Support

Hi everyone, Moving off this thread but wanted to bring up that Ian can't join today. Proposing a new time in another thread. Niklas On Mon, Apr 11, 2016 at 10:53 AM, Niklas Nielsen <n...@qni.dk> wrote: > Suggesting Monday April 18 5pm PST - I will send out a hangout link when > w

[Performance Isolation] Meeting on Thursday April 21 2016 5pm PST

Hi everyone, Per our conversation about Intel CAT enablement in Mesos, we are scheduling a Performance Isolation Working Group meeting at Thursday April 21 2016 5pm-6pm PST. Feel free to suggest agenda topics here:

<    7   8   9   10   11   12