Re: 1.0.0 RC2

a 1.0.x branch and update the version on trunk to 1.1.0. Any further fixes for RC2 will be cherry picked on to that branch. On Wed, Jun 15, 2016 at 4:09 PM, Vinod Kone wrote: > There are still 17 un-resolved issues targeted for 1.0. We have only > couple more days left for the RC cut.

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

+1 (binding) Tested on ASF CI w/ ubuntu. Note that centos:7 build issue is due to a known configuration issue (unable to find JAVA_HOME), fixed in 0.27.0, with the build script. *Revision*: 5edc7bab79649341c44df21c8842e05fb6d6c2bb - refs/tags/0.26.2-rc1 Configuration Matrix gcc clang centos:

Re: 1.0.0 RC2

There are still 8 outstanding issues, including 1 blocker. We are waiting for these to land for RC2. On Fri, Jun 17, 2016 at 5:11 PM, Vinod Kone wrote: > We still have 12 issues, including 1 blocker, targeted for 1.0. > > Dashboard: https://issues.apache.org/jira/secure/Dashboard.js

Re: Mesos CLI

+1 for keeping it in repo. Would be nice if the CLI can be written entirely in C++ though, to avoid supporting more languages. On Tue, Jun 21, 2016 at 12:12 PM, Jie Yu wrote: > I personally prefer it being part of the Mesos repo so that when people > install our package, they'll get the command

Re: Slack as the canonical chat channel

> From: haosdent > > Sent: Friday, June 17, 2016 6:48:02 PM > > To: dev > > Cc: Benjamin Hindman; Jake Farrell > > Subject: Re: Slack as the canonical chat channel > > > > +1 For Slack > > On Jun 18, 2016 4:04 AM, "Vinod Kone" wrote: > >

Re: [HTTP API] Should we remove the the duplicate GET_WEIGHTS in Operator APIs

We had a long discussion about this in the design doc: https://docs.google.com/document/d/1XfgF4jDXZDVIEWQPx6Y4glgeTTswAAxw6j8dPDAtoeI/edit?disco=Ar0igSQ TL:DR; is that we kept GET_WEIGHTS because we had its counter part UPDATE_WEIGHTS. On Thu, Jun 23, 2016 at 8:16 PM, haosdent wrote: > Hi,

Re: Slack as the canonical chat channel

ack is popular than gitter.im. so i suggest based on > slack. > > 2016-06-24 8:11 GMT+08:00 Jay JN Guo : > > > Great, thanks for your effort! We'd love to see it's opening up soon! > > > > /J > > > > Vinod Kone wrote on 06/24/2016 00:36:44: >

Re: Slack as the canonical chat channel

ools like https://github.com/rauchg/slackin to let anyone signup. On Fri, Jun 24, 2016 at 9:28 AM, Vaibhav Khanduja wrote: > We should atleast open this to contributors or who has access to assign > issue to them ... > > > > On 6/23/16, 10:50 PM, "Vinod Kone" wrote:

Re: Slack as the canonical chat channel

Yup. It is linked in the channel description. http://mesos.slackarchive.io/ On Fri, Jun 24, 2016 at 11:36 AM, James Peach wrote: > Are there public archives of the slack channel > > > On Jun 24, 2016, at 10:31 AM, Vinod Kone wrote: > > > > The plan is to open them up

Canonical contributors list

Hi, As discussed in the previous community sync, we would like to start storing a canonical list of contributors to the project. The main goal is to constantly measure how we are growing and improving as a community. For example, we want to track what % of reviews getting committed are from a giv

Re: Slack as the canonical chat channel

, Vinod Kone wrote: > Yup. It is linked in the channel description. > http://mesos.slackarchive.io/ > > On Fri, Jun 24, 2016 at 11:36 AM, James Peach wrote: > >> Are there public archives of the slack channel >> >> > On Jun 24, 2016, at 10:31 AM, Vinod Kone wrote

Re: Extend HTTP Endpoint to allow querying for metric types

Hey Tuan. Can I ask what you are trying to accomplish here? Does your metric collection system need to distinguish between different metrics? On Mon, Jun 27, 2016 at 10:35 AM, Tuan-Anh Hoang-Vu wrote: > Hello, > > I am planning to extend current metrics endpoint (/metrics/snapshot) to > only > r

Re: Please add me as contributor

Great. Can you send a PR adding yourself to https://github.com/apache/mesos/blob/master/docs/contributors.yaml ? On Mon, Jun 27, 2016 at 4:36 AM, Philip Winder wrote: > Hi, > Could you add me as a contributor. I would like to add a PR for improved > documentation for this issue: > https://issues

Re: Conceptual question Task Container

A task doesn't get its own cgroup because task was supposed to represent a unit of work. That unit of work doesn't have to be necessarily done via a unix process or container. For example, the executor might realize a task as a thread! That said, we did talk about providing an API for executors to

Re: Extend HTTP Endpoint to allow querying for metric types

collection system need to distinguish between different > > metrics. > > Currently we hard coded all metric types into our system, but it's not > very > > scalable and error prone. > > For example I recently discovered that we misclassified `timestamp` as > > gauge inste

Re: Extend HTTP Endpoint to allow querying for metric types

metrics/ > > > > > > > > On Mon, Jun 27, 2016 at 4:37 PM, Tuan-Anh Hoang-Vu < > > hvtuan...@gmail.com> > > > > wrote: > > > > > > > > > Hi Vinod, > > > > > > > > > > Yes, my metric collection syst

Re: Extend HTTP Endpoint to allow querying for metric types

eam? > > On Mon, Jun 27, 2016 at 6:39 PM, Vinod Kone wrote: > > > I was thinking more along the lines of : > > > > ``` > > GetMetrics { > > repeated Metric gauges = 1; > > repeated Metric counters = 2; > > } > > ``` > > > >

Re: Contributor Addition

Please send a PR/review to add yourself to https://github.com/apache/mesos/blob/master/docs/contributors.yaml. On Tue, Jun 28, 2016 at 4:13 PM, Haris Choudhary wrote: > Hi, > > Can I be please added as a contributor to the project? > > My Jira email is different to this one. > > Username: HarisC

Re: GPU channel on slack

Mind updating https://github.com/apache/mesos/blob/master/docs/working-groups.md with this info? On Thu, Jun 30, 2016 at 8:44 AM, Kevin Klues wrote: > If you are interested in the ongoing GPU work on Mesos, please join the > #gpus channel at mesos.slack.com. The big announcements for the GPU wor

Re: Shepherd for 49422

I'm happy to shepherd. On Thu, Jun 30, 2016 at 10:24 AM, Charles Allen < charles.al...@metamarkets.com> wrote: > https://reviews.apache.org/r/49422/ is a short patch which causes maven > related targets to run in batch mode, thus reducing and cleaning log output > during a build process for the m

Re: 1.0.0 RC2

lectPageId=12328715 On Tue, Jun 21, 2016 at 11:48 AM, Vinod Kone wrote: > There are still 8 outstanding issues, including 1 blocker. We are waiting > for these to land for RC2. > > > On Fri, Jun 17, 2016 at 5:11 PM, Vinod Kone wrote: > >> We still have 12 issues, inc

Re: Shepherd for 49422

> > Looks like there was already some activity from haosdent huang (thanks > Haosdent!). So I'm not sure if the next step is on me, you, or Haosdent > > On Thu, Jun 30, 2016 at 11:04 AM Vinod Kone wrote: > > > I'm happy to shepherd. > > > > On Thu, J

Re: Patch for website

Thanks Rich! The easiest is to just send a PR to our github repo: https://github.com/apache/mesos On Thu, Jul 7, 2016 at 10:35 AM, Rich Bowen wrote: > I'm not sure what the usual procedure is for docs patches, but here's a > patch for the website to point to lists.apache.org for mail archives: >

[VOTE] Release Apache Mesos 1.0.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.0. 1.0.0 includes the following: * Scheduler and Executor v1 HTTP APIs are now considered stable. * [MESOS-4791] - **Experimen

Re: Coverity Scan: Analysis completed for Mesos

On Mon, Jul 11, 2016 at 6:35 AM, Jörg Schad wrote: > b) Furthermore, we will set up a weekly Coverity build for HEAD (and maybe > we should also consider runs for RCs and releases). > I'm guessing this will be on ASF CI? Also, why weekly instead of continuously?

Re: getting added to contributors

Welcome to the community! Mind sending a PR to add yourself to https://github.com/apache/mesos/blob/master/docs/contributors.yaml ? On Mon, Jul 11, 2016 at 10:28 AM, Lawrence Wu wrote: > Hi, I will be working on https://issues.apache.org/jira/browse/MESOS-5376. > idownes already added me as a c

Re: Registering and framework failover

As Neil mentioned, we plan to add error codes for asynchronous errors (error() callback in the old API, Error event in the new API) and synchronous errors (HTTP 4xx/5xx responses in the new API). Having said that, I would advise against adding logic in your framework to do something smart (like re

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

aoli...@gmail.com> > > >>>>>>> wrote: > > >>>>>>> > > >>>>>>> > Hi Kapil, > > >>>>>>> > > > >>>>>>> > Do you mean that the stable builds from > > &

Re: Review Request 49943: Made vector reserve some spaces for allocator benchmark test.

On Mon, Jul 18, 2016 at 12:27 PM, Benjamin Mahler wrote: > Note that support/push_commits.py will do this for you, I should start > using it too.. ;) > Not yet, unless someone fixes the TODO :)

[VOTE] Release Apache Mesos 1.0.0 (rc3)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.0. *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a majority of at least 3 +1 PMC votes are cast.* 1.0.0 includes the following:

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

Looks like we missed a cherry pick. I'm cancelling this vote and spinning up rc4. On Fri, Jul 22, 2016 at 2:24 PM, Vinod Kone wrote: > Hi all, > > > Please vote on releasing the following candidate as Apache Mesos 1.0.0. > > *The vote is open until Tue Jul 25 11:00:00 P

[VOTE] Release Apache Mesos 1.0.0 (rc4)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.0. *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a majority of at least 3 +1 PMC votes are cast.* 1.0.0 includes the following:

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

gt; > wrote: > > > 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 >

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

otherwise. > > > > On Tue, Jul 26, 2016 at 6:52 PM, Benjamin Hindman < > > benjamin.hind...@gmail.com> wrote: > > > >> I agree with Vinod that we should go with option 1. I think redirect is > a > >> valuable feature but it's not imperativ

[RESULT][VOTE] Release Apache Mesos 1.0.0 (rc4)

e mesos-1.0.0.jar has been released to: https://repository.apache.org The website (http://mesos.apache.org) will be updated shortly to reflect this release. Thanks, On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone wrote: > Hi all, > > > Please vote on releasing the following ca

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

The 1.0 blog post is up: http://mesos.apache.org/blog/mesos-1-0-0-released/ Thank you all for making this possible! @vinodkone > On Jul 27, 2016, at 7:39 AM, Vinod Kone wrote: > > Hi all, > > The vote for Mesos 1.0.0 (rc4) has passed with the following votes. > &

Re: Rate-limiting agent removal w/ PARTITION_AWARE

Rate limiting task kills (or more specifically framework shutdowns on agents) of non-partition aware frameworks sounds good to me. I would like us to have as much backwards compatibility as possible here. We can update the flags' help saying that this doesn't apply to partition aware frameworks. O

1.0.1 release

Hi, As discussed on the 1.0 voting thread, we plan to cut a 1.0.1 as early as this week. So if you have anything that needs to absolutely go into the patch release, please work with your shepherd and get it landed on trunk and backported to the 1.0.x branch. Thanks,

Support for tasks groups aka pods in Mesos

Hi folks, One of the most requested features in Mesos has been first class support for managing pod like containers. We finally have some time to focus and shepherd this work. The epic tracking this work is : https://issues.apache.org/jira/browse/MESOS-2449 Design doc: https://issues.apache.org/

Re: Support for tasks groups aka pods in Mesos

Sorry, sent the wrong link earlier for design doc. Design doc: https://issues.apache.org/jira/browse/MESOS-6009 > Direct link: https://docs.google.com/document/d/1FtcyQkDfGp-bPHTW4pUoqQCgVlPde936bo-IIENO_ho/edit#heading=h.ip4t59nlogfz

Re: tutorial for mesos developer

Try this: https://github.com/mesosphere/RENDLER On Tue, Aug 9, 2016 at 3:21 PM, Rongqing Tu wrote: > Hi, > Is there any document to help how to develop a framework on mesos besides > the development guide? After making, installing, and running mesos master > and slaves, I would like to create a

[VOTE] Release Apache Mesos 1.0.1 (rc1)

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

Re: Integer version macro in header for conditional compilation

+kapil,till,adam On Thu, Aug 11, 2016 at 10:51 AM, Zhitao Li wrote: > Hi all, > > I sent a review request https://reviews.apache.org/r/50992/ to change the > MAJOR/MINOR/PATCH version macro in version.hpp to be integer rather than > string, so module writers can perform easier version comparison

Re: Need a Sherpherd for MESOS-5662

On Sat, Aug 13, 2016 at 8:36 PM, Sivaram Kannan wrote: > Can someone add me to the Contributors list? Can someone shepherd me for > the ticket 5662. > > I have few questions regarding general process. How does you guys have test > environment setup for your local changes? Say for example I take t

Re: Still don't support SLURM as a framework?

Slurm sounds like it could be a Mesos framework. It was marked as "Won't Fix" because the Apache Mesos project doesn't host code (or issues) for custom frameworks; those live in their own repos. On Sat, Aug 20, 2016 at 1:39 PM, Namgon Lucas Kim wrote: > Hi, > > I found that SLURM for Mesos fram

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

Hi all, The vote for Mesos 1.0.1 (rc1) has passed with the following votes. +1 (Binding) -- Alex Rukletsov Kapil Arya Yan Xu Adam Bordelon +1 (Non-binding) -- Greg Mann Haosdent Zhitao Li There were no 0 or -1 votes. Please

Re: jobs are stuck in agents and staying in stagged state

AFAICT, your agent is listening on port 8082 and not the default 5051. - I0829 14:24:21.750063 2679 slave.cpp:193] Slave started on 1)@ 128.226.116.69:8082 The fact that agent is receiving a task from the master means that the firewall on the agent allows incoming connections

Re: Inconsistent naming of support scripts

Nope. Didn't get around to doing it. Feel free to take over. @vinodkone > On Sep 2, 2016, at 8:56 AM, Michael Park wrote: > > Vinod, are there patches out for these? I would like to help close this off. > >> On Tue, Feb 16, 2016 at 6:30 PM, Vinod Kone wrote: >>

Fwd: REMINDER: MesosCon Asia’s CFP Deadline is September 9! Submit your Proposal Today

Hi folks, Just a friendly reminder that the CFP for MesosCon Asia is fast approaching! If you were planning to submit a talk please do so ASAP. If you weren't, please do :) Thanks, Vinod -- Forwarded message -- From: Linux Foundation Events Date: Fri, Aug 26, 2016 at 2:09 AM Sub

Re: Choice between LOG(FATAL) and EXIT(EXIT_FAILURE)

We typically used LOG(FATAL) when we were interested in the stack trace. If not, we preferred to use EXIT(EXIT_FAILURE). While that was the original intention, not sure if we have been following that distinction diligently. Separately, we should fix EXIT to log at ERROR level instead of just print

Re: Ask for a shepherd for MESOS-4440

Adam, looks like you shepherded MESOS-3763. Can you shepherd this as well? On Sun, Sep 4, 2016 at 6:38 PM, Yongqiao Wang wrote: > Hi guys, > > > In MESOS-3763 ticket, we have exposed http::internal::request function in > libprocess/http, so in MESOS-4440 ticket, we need to cleaning up the > http

Re: Need Champion for MESOS-6210

I can shepherd this. Thanks for the patch! On Tue, Sep 20, 2016 at 4:36 PM, Charles Allen < charles.al...@metamarkets.com> wrote: > https://reviews.apache.org/r/52105/ for > https://issues.apache.org/jira/browse/MESOS-6210 > > Anyone willing to be champion for that, please? >

Re: Mesos 1.1.0 release date

We are planning to release it in a week or so. Till has agreed to be the release manager for the release and will be supported by AlexR. @Till: Can you create a release dashboard and reply to this thread?

Target version vs Fixed Version

-- Forwarded message ------ From: Vinod Kone (JIRA) Date: Mon, Oct 3, 2016 at 6:13 PM Subject: [jira] [Updated] (MESOS-6026) Tasks mistakenly marked as FAILED due to race b/w ⁠sendExecutorTerminatedStatusUpdate()⁠ and ⁠_statusUpdate()⁠ To: iss...@mesos.apache.org [ https://is

Re: Target version vs Fixed Version

. > > On Tue, Oct 4, 2016 at 9:17 AM, Vinod Kone wrote: > >> Hi, >> >> Going forward, if you want an unresolved issue to be targeted for a >> specific version please set the "Target Version". The committer that >> commits the fix and resolves

1.0.2 release

Hi, As the Release Manager for 1.0, I'm responsible for all subsequent patch releases. I'm planning to cut the next patch release (1.0.2) within a week. So, if you have any patches that need to get into 1.0.2 make sure that either it is already in the 1.0.x branch or the corresponding ticket has

Re: LXC Container Support

Hi Tom, Your description of the current state of art is on point. Regarding support for LXC/LXD, what exactly does it mean? Is there an image spec for those that you want Mesos to support? What's your use case? Thanks, On Wed, Oct 5, 2016 at 3:10 PM, Tom Barber wrote: > Hello folks, > > I've

Re: 1.0.2 release

Release dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329719 I'm waiting for 2 issues to be resolved. Once that's done, I'll start prepping the release. On Wed, Oct 5, 2016 at 4:11 PM, Vinod Kone wrote: > Hi, > > As the Release Manager

Re: 1.1.0 release

I think you need to clean up the JIRA a bit. 1) Make sure unresolved tickets do not have fix version (1.1.0) set. 2) Move "Fix version 1.1.0" to "Target version 1.1.0". 2) might obviate the need for 1). On Fri, Oct 7, 2016 at 7:24 AM, Till Toenshoff wrote: > Hi everyone! > > its us who will

Re: Deprecate MESOS_DIRECTORY executor environment variable

If the sandbox host path is not yet available in v1 API, it should be made available. I'll be happy to shepherd. The rules for APIs stipulate that the deprecation period doesn't start > until the next major release (2.0). > We need to revise the API compatibility rules a bit. Right now the rules

Re: Welcome Qian Zhang as a new committer!

Congrats Qian. Looking forward to more contributions! @vinodkone > On Oct 8, 2016, at 11:35 AM, haosdent wrote: > > Congrats to Qian!!! Looking forward work more with you in the community! > >> On Sun, Oct 9, 2016 at 2:20 AM, Jie Yu wrote: >> Hi folks, >> >> I' happy to announce that the P

Allowing both CommandInfo and ExecutorInfo on TaskInfo

Hi, We are contemplating whether to allow both CommandInfo and ExecutorInfo on TaskInfo (MESOS-6294 ). Currently we only allow one or the other. The motivation is to allow custom executors a more structured way to pass information (e.g, command) ab

Re: A Plan for Mesos Community Syncs

Huge +1. Thanks for taking ownership of this. On Thu, Oct 13, 2016 at 1:34 PM, Michael Park wrote: > I would like to try to get the community syncs back on track. They have not > been organized well recently, and I would like to take ownership of being > the driver/host of the meetings. I think

Re: On Mesos versioning and deprecation policy

We will chat about this in the upcoming community sync (thursday 3 PM). So, please make sure to attend if you are interested. On Fri, Oct 14, 2016 at 3:44 PM, Yan Xu wrote: > > On Fri, Oct 14, 2016 at 3:37 PM, Yan Xu wrote: > >> Thanks Alex for starting this! >> >> In addition to comments below

[VOTE] Release Apache Mesos 1.0.2 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.2. 1.0.2 includes the following: ** Bug * [MESOS-5613] - mesos-local fails to start if MESOS_WORK_DIR isn't set. * [MESOS-60

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

+1 (binding) Tested on ASF CI. *Revision*: c2cb47f78f1d99630b133b00bdd4c9d4c523c02b - refs/tags/1.1.0-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Success]

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

fixed by Santhosh. > > - Jie > > On Tue, Oct 18, 2016 at 2:51 PM, Vinod Kone wrote: > >> Hi all, >> >> >> Please vote on releasing the following candidate as Apache Mesos 1.0.2. >> >> >> 1.0.2 includes the following: >> >> --

Re: Does libprocess support multi-port?

No it doesn't. On Wed, Oct 26, 2016 at 1:10 AM, Suteng wrote: > Hi, > > Does libprocess support multi port? Some process bind to a port, and some > other process bind to another port in the same OS process. > > > > Thanks, > > Teng > > > > > > > > > > Su Teng 00241668 > > > > Distributed and Pa

Re: On Mesos versioning and deprecation policy

But in case that we didn't or forgot to write it explicitly in the > document, should we give up to update the API? Just like user Alice said > this is a BUG while user Bob said this is a feature. I think we still need > to raise it case by case to ensure most users are not affected by t

Re: Jenkins Build Labels

I can't remember now what the issue was with ubuntu-us1 and untuntu-6. I can remove the labels and see if things continue to work ok. Are all `Hadoop` nodes now tagged with `docker` as well? On Mon, Oct 31, 2016 at 12:23 PM, Daniel Takamori wrote: > Greetings from the Infra Team, > We've notice

[VOTE] Release Apache Mesos 1.0.2 (rc2)

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

[VOTE] Release Apache Mesos 1.0.2 (rc3)

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

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

+1 (binding) Tested on ASF CI. *Revision*: a44b077ea0df54b77f05550979e1e97f39b15873 - refs/tags/1.1.0-rc3 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Success]

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

Hi all, The vote for Mesos 1.0.2 (rc3) has passed with the following votes. +1 (Binding) -- Alex Rukletsov Till Toenshoff Yan Xu There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.0.2 It is recommen

Re: Updating review board request

Just run the support/post-reviews.py tool against your rebased branch. It will update the same review on ReviewBoard. On Thu, Nov 17, 2016 at 11:27 PM, Vijay Srinivasaraghavan < vijikar...@yahoo.com.invalid> wrote: > Hello, > I have submitted a patch to the Mesos review board using post-reviews.p

Re: Updating review board request

17, 2016 at 11:49 PM, Vijay Srinivasaraghavan < vijikar...@yahoo.com> wrote: > I tried running support/post-reviews.py but it creates a new RB request > instead of updating existing one. > > > On Thursday, November 17, 2016 11:37 PM, Vinod Kone > wrote: > > > Just run

Re: Force offer from all of the slaves

Once you set GLOG_v, you should be able to see lines like these "Framework filtered agent for <123> seconds" On Sun, Nov 27, 2016 at 8:18 AM, haosdent wrote: > > I choose the right offer and decline the rest. > Hi, @krishnanvr Do you use up all available resources in that agent's > offer? If

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

+1 (binding) Tested on ASF CI. *Revision*: 52a0b0a41482da35dc736ec2fd445b6099e7a4e7 - refs/tags/0.28.3-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Success]

Re: Building on OS X 10.12

Thanks! On Thu, Dec 1, 2016 at 12:34 PM, Benjamin Mahler wrote: > I ran into some compilation issues after upgrading to OS X 10.12.1, and was > able to build successfully with Jie's help. > > The first thing was that I encountered a lot of these deprecation warnings: > > ../../../3rdparty/libpro

Re: Adding a reload end-point to `network/cni` isolator

We are trying to move away from un-versioned REST endpoints like "/reload" in favor of versioned endpoint(s) that take calls. We don't have a good story yet for endpoints that are not hosted by Master and Agent actors. So, at first blush, I'm wary of this solution. - Why not scan the config direct

Re: Quota

How many resources does the agent register with the master? How many resources does spark task need? I'm guessing marathon is not registered with "test" role so it is only getting un-reserved resources which are not enough for spark task? On Fri, Dec 9, 2016 at 2:54 PM, Vijay Srinivasaraghavan <

Re: Quota

"unreserved_resources":{ > "disk":12099.0, > "mem":14863.0, > "gpus":0.0, > "cpus":4.0, > "ports":"[1025-2180, 2182-3887, 3889-5049, > 5052-8079, 808

Welcome Haosdent Huang as Mesos Committer and PMC member!

Hi folks, Please join me in formally welcoming Haosdent Huang as Mesos Committer and PMC member. Haosdent has been an active contributor to the project for more than a year now. He has contributed a number of patches and features to the Mesos code base, most notably the unified cgroups isolator a

Re: Welcome Guangya Liu as Mesos Committer and PMC member!

Congrats Guangya! Welcome to the PMC! On Fri, Dec 16, 2016 at 7:03 PM, Sam wrote: > congratulations Guangya > > Sent from my iPhone > > On 17 Dec 2016, at 3:23 AM, Avinash Sridharan > wrote: > > Congrats Guangya !! > > On Fri, Dec 16, 2016 at 11:20 AM, Greg Mann wrote: > >> Congratulations Gua

Re: thread_local supported on Apple

A consequence of using `__thread` on Apple is that initializers for thread locals are required to be constant expressions. This is not the case for the c++11 standard `thread_local`. Can you expand on the benefits of 'thread_local'? Is the above statement alluding to tech debt or preventing new f

Re: Mesos 1.1.1 release dashboard

Same deal with the next patch release for 1.0.x ;) @vinodkone > On Dec 22, 2016, at 10:15 AM, Alex Rukletsov wrote: > > Folks, > > We are planning to cut the 1.1.1 release early next week. If you have any > patches that need to get into 1.1.1, please make sure that either it is > already in th

Re: Review Request 29973: Passed framework ID instead framework info to Master::receive.

973/#comment113290> framework id will be empty for REGISTER event. - Vinod Kone On Jan. 20, 2015, 6:49 p.m., Jie Yu wrote: > > --- > This is an automatically generated e-mail. To reply, visit: > https://reviews.

Re: Review Request 29974: Added stream function for repeated protobuf messages.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29974/#review68825 --- Ship it! Ship It! - Vinod Kone On Jan. 20, 2015, 6:49 p.m., Jie

Re: Review Request 29975: Renamed the Accept call handler to accept.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29975/#review68826 --- Ship it! Ship It! - Vinod Kone On Jan. 20, 2015, 6:49 p.m., Jie

Re: Review Request 29976: Moved launchTasks logics to ACCEPT call handler in master.

g a separate temp right now is a bit confusing. src/tests/resource_offers_tests.cpp <https://reviews.apache.org/r/29976/#comment113311> Any reason to not do this is a subsequent patch? - Vinod Kone On Jan. 20, 2015, 6:49 p.m., Jie Yu wrote: > >

Re: Review Request 29989: Renamed MockAllocatorProcess to TestAllocatorProcess.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29989/#review69029 --- Ship it! Ship It! - Vinod Kone On Jan. 16, 2015, 11:12 p.m

Re: Review Request 29990: Updated TestAllocatorProcess to avoid the test warnings.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29990/#review69033 --- Ship it! cool trick. - Vinod Kone On Jan. 16, 2015, 11:12 p.m

Re: Review Request 29973: Passed framework ID instead framework info to Master::receive.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29973/#review69039 --- Ship it! Ship It! - Vinod Kone On Jan. 20, 2015, 6:49 p.m., Jie

Re: Review Request 29973: Passed framework ID instead framework info to Master::receive.

> On Jan. 21, 2015, 12:43 a.m., Vinod Kone wrote: > > src/master/master.cpp, line 1326 > > <https://reviews.apache.org/r/29973/diff/2/?file=827013#file827013line1326> > > > > framework id will be empty for REGISTER event. > > Jie Yu wrote: > Yes

Re: Review Request 29976: Moved launchTasks logics to ACCEPT call handler in master.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/29976/#review69041 --- forgot to update the diff? - Vinod Kone On Jan. 20, 2015, 6:49

Re: Review Request 30129: Style fixes for master.hpp.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30129/#review69043 --- Ship it! Ship It! - Vinod Kone On Jan. 21, 2015, 6:09 p.m., Jie

Re: Review Request 29600: Moved Task and StatusUpdate from mesos/messages.proto.

odules and are not to be used by frameworks directly. src/Makefile.am <https://reviews.apache.org/r/29600/#comment113826> s/need/needed/ - Vinod Kone On Jan. 22, 2015, 1:17 a.m., Kapil Arya wrote: > > --- > Thi

Review Request 30191: Moved RateLimiter tests into its own file.

/libprocess/src/tests/process_tests.cpp 3bbfe0a7a65acb52d139fda81816acf305d891f5 Diff: https://reviews.apache.org/r/30191/diff/ Testing --- make check Thanks, Vinod Kone

Review Request 30192: Updated RateLimiter to allow discard semantics.

Thanks, Vinod Kone

Re: Review Request 30192: Updated RateLimiter to allow discard semantics.

E-CREATION Diff: https://reviews.apache.org/r/30192/diff/ Testing --- make check Thanks, Vinod Kone

<    1   2   3   4   5   6   7   8   9   10   >