Proposing Mesos patch releases 0.21.2-0.24.1 for MESOS-2986

Mesos users are having problems using stable Mesos releases with modern Docker due to the change in version strings in Docker 1.8 (also in Fedora 22) as described in https://issues.apache.org/jira/browse/MESOS-2986. There have been requests for patch releases ranging from 0.21.x to 0.24.x. I would

Re: Proposing Mesos patch releases 0.21.2-0.24.1 for MESOS-2986

Lgtm, thanks for taking care of this! On Mon, Sep 14, 2015 at 9:33 AM, Adam Bordelon wrote: > Mesos users are having problems using stable Mesos releases with modern > Docker due to the change in version strings in Docker 1.8 (also in Fedora > 22) as described in https://issues.apache.org/jira/b

Re: Proposing Mesos patch releases 0.21.2-0.24.1 for MESOS-2986

Cool Mesos team. 2015-09-14 18:52 GMT+08:00 Jörg Schad : > Lgtm, thanks for taking care of this! > > On Mon, Sep 14, 2015 at 9:33 AM, Adam Bordelon wrote: > > > Mesos users are having problems using stable Mesos releases with modern > > Docker due to the change in version strings in Docker 1.8 (

Re: Mesos 0.25.0

Following in the footsteps of the dashboard for the 0.23.0 release, here is the Mesos 0.25.0 Release Dashboard This dashboard was very successful at reducing the time required to triage the first release candidate. Let's

Do we still need to add InverseOffer support to Scheduler API?

Hi, In the maintenance epic (MESOS-1474), I see there are 3 tasks created to add InverseOffer support to Scheduler API: MESOS-2063 Add InverseOffer to C++ Scheduler API MESOS-2064 Add InverseOffer to Java Scheduler API MESOS-2065 Add InverseOffer to Python

Re: Do we still need to add InverseOffer support to Scheduler API?

Hi Qian, There is no current plan to add this to the old API. Those tickets were created pre-V1 API. Currently the goal is to encourage developers to use the V1 API to have access to new features such as maintenance primitives. Joris On Mon, Sep 14, 2015 at 10:22 AM, Qian AZ Zhang wrote: > > >

Re: Do we still need to add InverseOffer support to Scheduler API?

Hi Joris, I think that those APIs are still needed as HTTP API is mainly initiated by operator, the current call for HTTP API including TEARDOWN, ACCEPT, DECLINE, REVIVE, KILL, SHUTDOWN etc, but the offer related operations such as offer and InverserOffers are initiatedby mesos master, the master

Re: Do we still need to add InverseOffer support to Scheduler API?

The V1 API supports the full scheduler API. This means you can receive and act upon offers and (once the patches are committed) inverse offers through the V1 API. Please see https://reviews.apache.org/r/37283/ as an example of how the V1 API can be used to deal with inverse offers. Joris On Mon,

Re: Do we still need to add InverseOffer support to Scheduler API?

Hi @Guangya Liu. V1 API support both mesos call frameworks or frameworks call mesos. https://docs.google.com/document/d/1pnIY_HckimKNvpqhKRhbc9eSItWNFT-priXh_urR-T0/edit And I think Java or Python API libraries would be deprecated and more out to a better place to maintain in the future(Also mayb

Re: Do we still need to add InverseOffer support to Scheduler API?

Thanks Haosdent and Joris, I see that the host maintain patch ( https://reviews.apache.org/r/37180/diff/8#0) is also sending "ResourceOffersMessage" to framework so the framework can still use "ResourceOffer" to handle the inverseOffer when framework got the inverseOffer, right? Thanks, Guangya

Re: [jira] [Commented] (MESOS-3416) Publish egg for 0.24.0 to PyPI

[~kapil malik] I got your pain. You could install them through yum or apt-get. Mesosphere provides deb or rpm packages in their download pages. https://mesosphere.com/downloads/ On Sep 14, 2015 11:32 PM, "Kapil Malik (JIRA)" wrote: [ https://issues.apache.org/jira/browse/MESOS-3416?page=com.

RE: mesos.native could not found

Hi Haosdent, Thank you, yes it's working fine for 0.24. However, consider the scenario - I have a mesos cluster in production. I want to run a custom mesos framework written in python. However, for that, I need mesos.native package installed on the box. How do I do that? I see the interface eg

RE: mesos.native could not found

Sorry for spamming, just saw your reply on JIRA, let me checkout https://mesosphere.com/downloads/ -Original Message- From: Kapil Malik [mailto:kma...@adobe.com] Sent: 14 September 2015 21:20 To: dev@mesos.apache.org Subject: RE: mesos.native could not found Hi Haosdent, Thank you, ye

brew install mesos doesn't work for 0.24.0

I'm trying to update the homebrew formula per the release guide . But when following instructions from homebrew regarding testing the changes

Re: brew install mesos doesn't work for 0.24.0

Looks like you may need to update/install XCode on your Mac, perhaps? $ find / |grep svn_delta ... /Applications/Xcode.app/Contents/Developer/usr/lib/libsvn_delta-1.0.dylib /Applications/Xcode.app/Contents/Developer/usr/lib/libsvn_delta-1.dylib /Library/Developer/CommandLineTools/usr/lib/libsvn_de

Re: Apache Mesos Community Sync

We'll have the next community sync this Thursday (Sept. 17th) at 8:30am Pacific. Please add items to the agenda . We will try Hangouts on Air this time. We will post the video stream link

Re: brew install mesos doesn't work for 0.24.0

I do fine libsvn_delta libs in my file system ➜ twitter git:(vinod/0.24.0) ✗ sudo find / -name "*svn_delta*" Password: /Applications/Xcode.app/Contents/Developer/usr/lib/libsvn_delta-1.0.dylib /Applications/Xcode.app/Contents/Developer/usr/lib/libsvn_delta-1.dylib /Library/Developer/CommandLi

Re: Do we still need to add InverseOffer support to Scheduler API?

If we keep the current C++ scheduler API as it is, then I think framework can never receive inverse offer in its "resourceOffers()" callback, the reason is, In SchedulerProcess::initialize(), we have the following code: install( &SchedulerProcess::resourceOffers, &ResourceOffers

Re: brew install mesos doesn't work for 0.24.0

> On Sep 14, 2015, at 4:51 PM, Vinod Kone wrote: > > I do fine libsvn_delta libs in my file system > > ➜ twitter git:(vinod/0.24.0) ✗ sudo find / -name "*svn_delta*" > > Password: > > /Applications/Xcode.app/Contents/Developer/usr/lib/libsvn_delta-1.0.dylib > > /Applications/Xcode.app/Conte

Re: Do we still need to add InverseOffer support to Scheduler API?

Hi Qian, We currently don’t intend to move the old C++ Scheduler/Scheduler Driver Scheduler Driver interface to use the Mesos V1 API. If you want to use the new V

Re: Do we still need to add InverseOffer support to Scheduler API?

Just noticed that there is a framework example using Call/Event lingo for V1 API: https://github.com/apache/mesos/blob/master/src/examples/event_call_framework.cpp , it is a good reference/example for how to use V1 API in a framework. Thanks, Guangya On Tue, Sep 15, 2015 at 10:59 AM, Anand Mazum

Re: brew install mesos doesn't work for 0.24.0

Thanks, James. I don't suppose, then, that simply doing: LD_LIBRARYPATH=/opt/twitter:$LD_LIBRARYPATH would solve the issue? *Marco Massenzio* *Distributed Systems Engineerhttp://codetrips.com * On Mon, Sep 14, 2015 at 7:44 PM, James Peach wrote: > > > On Sep 14, 2015,

Re: brew install mesos doesn't work for 0.24.0

Fwiw, mesos does have a --with-svn option which looks at the correct homebrew directory. My guess is that the python toolchain doesn't pickup the with-svn path. @vinodkone > On Sep 14, 2015, at 10:01 PM, Marco Massenzio wrote: > > Thanks, James. > I don't suppose, then, that simply doing: >

Seeking a shepherd for MESOS-3408

Hi all, Is anyone willing to shepherd on MESOS-3408? Thanks! Regards, Qian Zhang

Re: Proposing Mesos patch releases 0.21.2-0.24.1 for MESOS-2986

If we can land https://issues.apache.org/jira/browse/MESOS-3136 soon, it may be worth including in Mesos 0.24.1. There were also requests to backport the fix to Mesos 0.23.1. Any objections? On Mon, Sep 14, 2015 at 5:36 AM, tommy xiao wrote: > Cool Mesos team. > > 2015-09-14 18:52 GMT+08:00 Jörg

Re: Seeking a shepherd for MESOS-3408

I'm on it. On Mon, Sep 14, 2015 at 11:14 PM, Qian AZ Zhang wrote: > > Hi all, > > Is anyone willing to shepherd on MESOS-3408? Thanks! > > > Regards, > Qian Zhang