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

[Adam Bordelon]

Hi all,

The vote for Mesos 1.2.2 (rc1) has passed with the following votes.

+1 (Binding)
--
Adam B
Alexander Rojas
Kapil Arya
Vinod Kone

There were no 0 or -1 votes.

Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/1.2.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 available at:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.2.2

The mesos-1.2.2.jar has been released to:
https://repository.apache.org

The website (http://mesos.apache.org) will be updated shortly to reflect
this release.

Thanks,
-Adam and Alexander-


On Wed, Aug 9, 2017 at 9:57 AM, Vinod Kone  wrote:

> +1 (binding)
>
> Tested on ASF CI. The red builds are known flaky tests.
>
>
> *Revision*: f954bb01e21d30ddc0d5f87244bc4c22478e6961
>
>- refs/tags/1.2.2-rc1
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl autotools
> [image: Failed]
>  Release/38/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Not run]
> cmake
> [image: Success]
>  Release/38/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%
> 7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Not run]
> --verbose autotools
> [image: Success]
>  Release/38/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_
> exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Not run]
> cmake
> [image: Success]
>  Release/38/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%
> 3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Not run]
> ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools
> [image: Success]
>  Release/38/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Failed]
>  Release/38/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> cmake
> [image: Success]
>  Release/38/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Success]
>  Release/38/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=-
> -verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> --verbose autotools
> [image: Failed]
>  Release/38/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
> label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Failed]
>  Release/38/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
> label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> cmake
> [image: Success]
>  Release/38/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%
> 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> [image: Failed]
>  Release/38/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=-
> -verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%
> 3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
>
> On Wed, Aug 9, 2017 at 1:53 AM, Alexander Rojas 
> wrote:
>
> > +1 (binding)
> >
> > Ran manual tests in Fedora 25 and Ubuntu 17.04
> >
> > Alexander Rojas
> > alexan...@mesosphere.io
> >
> >
> >
> >
> > > On 5. Aug 2017, at 02:12, Adam Bordelon  wrote:
> > >
> > > Hel

Register for MesosCon NA

[Judith Malnick]

Hi Everyone,

If you're planning on attending MesosCon NA you should register soon
.
Standard registration ends on the 14th, and late registration is more
expensive. You can use the code MCDCOS20 to get 20% off your registration
fee.

We have made exciting changes to the MesosCon format:

   -

   Dedicated Session Tracks
   

   -

  SMACK, GPUs, Analytics
  -

  Ops: Storage, Networking, Monitoring, Security, etc.
  -

  DevOps: Microservices, APIs, CI/CD, Artifact Repositories, etc.
  -

  Mesos Frameworks
  -

  Mesos Internals
  -

   MesosCon University
   

   -

   Community Town Hall meetings
   

   -

   And of course the hackathon
   



Don't hesitate to ask if you have any questions! Looking forward to seeing
you at MesosCon!


All the best!

Your Community Team

-- 
Judith Malnick
DC/OS Community Manager
310-709-1517

Mesos workloads

[Thodoris Zois]

Hello,

 I am planning on submitting a manuscript of my work later this year. I am 
trying to evaluate the results of my work on real workloads. Is there somebody 
that would like to help by giving workloads that his/her company use along with 
mesos? Or some traces so i can make my own workload? Sorry for notifying the 
whole channel. If somebody would like to help do not hesitate to send me pm.


Thank you,
Thodoris Zois

--
Institute of Computer Science, Greece
FORTH-ICS 

Re: Command Executor

[Oeg Bizz]

Till,  You got it, that is exactly what I need.  I guess I will have to 
implement an anonymous module even though the documentation warns you against 
it :) 
Oscar

On Wednesday, August 9, 2017, 11:41:32 AM EDT, Till Toenshoff 
 wrote:

If I got you right, then what you want is something that has the exact lifetime 
of the agent process and allows you any kind of a custom API.
Maybe you should consider using a module for this. There is this notion of so 
called anonymous modules. Such module simply coexists with the parent process, 
in your case the agent.See 
http://mesos.apache.org/documentation/latest/modules/ for more.
Such module in combination with a custom executor might get you where you need 
to be…. at least that is what I am hoping for.

On Aug 9, 2017, at 12:53 PM, Oeg Bizz  wrote:
Ben,  That is exactly what I did, the problem is that is not being invoked when 
the mesos-slave starts.  I am trying to avoid sending a bogus initial task just 
to kick it off, but it seems there is no way to tell the mesos-slave to start 
the executor at startup, is it?
Thanks for your reply, 
Oscar

On Tuesday, August 8, 2017, 3:38:17 PM EDT, Benjamin Mahler 
 wrote:

You're free to write your own long lived executor that can process multiple 
tasks. The built in executors self-terminate after running the tasks they are 
launched with.
On Tue, Aug 8, 2017 at 2:36 AM, Oeg Bizz  wrote:

It is used to notify some services that the agents are out there ready to 
process data.  The service takes into account who and how many are out there 
and some information from the HB to perform some sort of load balancing.  
Without the HB the service does not know how many agents are out and tasking is 
assigned only when an offer is received, but that is not as effective as it 
should be if the service would know in advance about the cluster's load.  
Thanks,
Oscar

On Monday, August 7, 2017, 11:13:10 AM EDT, James Peach  
wrote:


> On Aug 5, 2017, at 3:03 AM, Oeg Bizz  wrote:
> 
> I have a framework that relies on information sent by a custom Java Command 
> Executor; think of some sort of heartbeat.  I start getting hearbeats after I 
> send a task to that mesos-slave, but never before that.  That makes me assume 
> that the CommandExecutor is not started until a task is submitted to be 
> executed by that agent.  Is there a way to tell mesos-slave to start the 
> ComandExecutor as soon as it starts running?

Not AFAIK. Executors are always spawned in order to execute tasks. In your 
case, what is the heartbeat for, if there are no tasks on the agent?

J