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

[Michael Park]

Okay, it's been 2 weeks since that email, and I haven't heard any requests.
I am now officially cancelling the 1.3.3 release.

Thanks,

MPark

On Fri, Jul 20, 2018 at 10:39 AM Alex Rukletsov  wrote:

> MPark—
>
> what's the decision regarding the 1.3.3 release?
>
> On Mon, Jul 9, 2018 at 8:52 PM, Michael Park  wrote:
>
> > I'm considering simply abandoning the 1.3.3 release and bringing the
> 1.3.x
> > branch to end of life.
> > If anyone really wants a 1.3.3, I'm certainly willing to finish the
> > release portion of this
> > but I don't have time to dig into the CI issue that Vinod pointed out. If
> > someone feels compelled
> > to investigate the issue and wants 1.3.3 released, please speak up.
> >
> > I'll wait for some time (say, a week) to gauge the interest and take
> > corresponding action.
> >
> > Thanks,
> >
> > MPark
> >
> > On Thu, May 31, 2018 at 11:55 AM Vinod Kone 
> wrote:
> >
> >> -1 (binding).
> >>
> >>
> >> Ran it in ASF CI and found an issue worth investigating. Other 3 issues
> >> looks to be related to known flaky tests and/or known core dump issue
> (that
> >> has been fixed in later versions).
> >>
> >> *Revision*: c78e56e4ea217878dd604de638623be166a18db0
> >>
> >>- refs/tags/1.3.3-rc1
> >>
> >> Configuration Matrix gcc clang
> >> centos:7 --verbose --enable-libevent --enable-ssl autotools
> >> [image: Failed]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/49/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]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/49/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]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/49/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]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/49/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]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/49/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]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/49/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]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/49/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: Failed]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/49/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]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/49/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)

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

[Michael Park]

org/view/M-R/view/Mesos/job/Mesos-Release/49/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)/console>
>  Looks
> related to MESOS-6799
> <https://issues.apache.org/jira/browse/MESOS-6799?jql=project%20%3D%20MESOS%20AND%20text%20~%20%22Scheme%2FHTTPTest.Endpoints%22>
>  but
> that is supposed to have been fixed in 1.2.
>
> [ RUN  ] Scheme/HTTPTest.Endpoints/0
> I0529 21:04:38.781232 28418 openssl.cpp:419] CA file path is unspecified! 
> NOTE: Set CA file path with LIBPROCESS_SSL_CA_FILE=
> I0529 21:04:38.781262 28418 openssl.cpp:424] CA directory path unspecified! 
> NOTE: Set CA directory path with LIBPROCESS_SSL_CA_DIR=
> I0529 21:04:38.781270 28418 openssl.cpp:429] Will not verify peer certificate!
> NOTE: Set LIBPROCESS_SSL_VERIFY_CERT=1 to enable peer certificate verification
> I0529 21:04:38.781277 28418 openssl.cpp:435] Will only verify peer 
> certificate if presented!
> NOTE: Set LIBPROCESS_SSL_REQUIRE_CERT=1 to require peer certificate 
> verification
> E0529 21:04:38.781814 28435 process.cpp:956] Failed to accept socket: future 
> discarded
> *** Aborted at 1527627878 (unix time) try "date -d @1527627878" if you are 
> using GNU date ***
> PC: @ 0x7fcbd5615dd6 __memcpy_ssse3_back
> *** SIGSEGV (@0x5cabd78) received by PID 28418 (TID 0x7fcbcc6dd700) from PID 
> 97172856; stack trace: ***
> I0529 21:04:38.797348 28418 process.cpp:1272] libprocess is initialized on 
> 172.17.0.3:47350 with 16 worker threads
> @ 0x7fcbd66dd6d0 (unknown)
> @ 0x7fcbd5615dd6 __memcpy_ssse3_back
> @ 0x7fcbd5e636f0 (unknown)
> @ 0x7fcbd5e63d9c (unknown)
> @   0x42af09 process::UPID::UPID()
> I0529 21:04:38.803799 29172 process.cpp:3741] Handling HTTP event for process 
> '(77)' with path: '/(77)/body'
> @   0x8edfaa process::DispatchEvent::DispatchEvent()
> @   0x8e6560 process::internal::dispatch()
> I0529 21:04:38.809983 29176 process.cpp:3741] Handling HTTP event for process 
> '(77)' with path: '/(77)/pipe'
> @   0x900ad8 process::dispatch<>()
> @   0x8e548c process::ProcessBase::route()
> I0529 21:04:38.821267 29181 process.cpp:3741] Handling HTTP event for process 
> '(77)' with path: '/(77)/body'
> I0529 21:04:38.821970 29182 process.cpp:3798] Failed to process request for 
> '/(77)/body': failure
> I0529 21:04:38.821995 29172 process.cpp:1482] Returning '500 Internal Server 
> Error' for '/(77)/body' (failure)
> [   OK ] Scheme/HTTPTest.Endpoints/0 (227 ms)
> [ RUN  ] Scheme/HTTPTest.Endpoints/1
> @   0x9d823d process::ProcessBase::route<>()
> @   0x9d4480 process::Help::initialize()
> @   0x8de9e8 process::ProcessManager::resume()
> @   0x8db3be 
> _ZZN7process14ProcessManager12init_threadsEvENKUt_clEv
> @   0x8ed63e 
> _ZNSt12_Bind_simpleIFZN7process14ProcessManager12init_threadsEvEUt_vEE9_M_invokeIIEEEvSt12_Index_tupleIIXspT_EEE
> @   0x8ed582 
> _ZNSt12_Bind_simpleIFZN7process14ProcessManager12init_threadsEvEUt_vEEclEv
> @   0x8ed50c 
> _ZNSt6thread5_ImplISt12_Bind_simpleIFZN7process14ProcessManager12init_threadsEvEUt_vEEE6_M_runEv
> @ 0x7fcbd5e5a070 (unknown)
> @ 0x7fcbd66d5e25 start_thread
> @ 0x7fcbd55bebad __clone
> make[7]: *** [check-local] Segmentation fault
>
>
>
>
>
> On Tue, May 29, 2018 at 12:28 PM, Benjamin Mahler 
> wrote:
>
>> +1 (binding)
>>
>> Make check passes on macOS 10.13.4 with Apple LLVM version 9.1.0
>> (clang-902.0.39.1).
>>
>> On Wed, May 23, 2018 at 10:00 PM, Michael Park  wrote:
>>
>> > The tarball has been fixed, please vote now!
>> >
>> > 'twas BSD `tar` issues... :(
>> >
>> > Thanks,
>> >
>> > MPark
>> >
>> > On Wed, May 23, 2018 at 11:39 AM, Michael Park 
>> wrote:
>> >
>> >> Huh... 樂 Super weird. I'll look into it.
>> >>
>> >> Thanks for checking!
>> >>
>> >> MPark
>> >>
>> >> On Wed, May 23, 2018 at 11:34 AM Vinod Kone 
>> wrote:
>> >>
>> >>> It's empty for me too!
>> >>>
>> >>> On Wed, May 23, 2018 at 11:32 AM, Benjamin Mahler > >
>> >>> wrote:
>> >>>
>> >>>> Thanks Michael!
>> >>>>
>> >>>> Looks like the tar.gz is empty, is it just me?
>> >>>>
>> >>>> On Tue,

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

[Michael Park]

The tarball has been fixed, please vote now!

'twas BSD `tar` issues... :(

Thanks,

MPark

On Wed, May 23, 2018 at 11:39 AM, Michael Park <mp...@apache.org> wrote:

> Huh... 樂 Super weird. I'll look into it.
>
> Thanks for checking!
>
> MPark
>
> On Wed, May 23, 2018 at 11:34 AM Vinod Kone <vinodk...@apache.org> wrote:
>
>> It's empty for me too!
>>
>> On Wed, May 23, 2018 at 11:32 AM, Benjamin Mahler <bmah...@apache.org>
>> wrote:
>>
>>> Thanks Michael!
>>>
>>> Looks like the tar.gz is empty, is it just me?
>>>
>>> On Tue, May 22, 2018 at 10:09 PM, Michael Park <mp...@apache.org> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Please vote on releasing the following candidate as Apache Mesos 1.3.3.
>>>>
>>>> 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.3.3-rc1
>>>> 
>>>> 
>>>>
>>>> The candidate for Mesos 1.3.3 release is available at:
>>>> https://dist.apache.org/repos/dist/dev/mesos/1.3.3-rc1/
>>>> mesos-1.3.3.tar.gz
>>>>
>>>> The tag to be voted on is 1.3.3-rc1:
>>>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=
>>>> commit;h=1.3.3-rc1
>>>>
>>>> The SHA512 checksum of the tarball can be found at:
>>>> https://dist.apache.org/repos/dist/dev/mesos/1.3.3-rc1/
>>>> mesos-1.3.3.tar.gz.sha512
>>>>
>>>> The signature of the tarball can be found at:
>>>> https://dist.apache.org/repos/dist/dev/mesos/1.3.3-rc1/
>>>> mesos-1.3.3.tar.gz.asc
>>>>
>>>> The PGP key used to sign the release is here:
>>>> https://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-1226
>>>>
>>>> Please vote on releasing this package as Apache Mesos 1.3.3!
>>>>
>>>> The vote is open until Fri May 25 22:07:39 PDT 2018 and passes if a
>>>> majority of at least 3 +1 PMC votes are cast.
>>>>
>>>> [ ] +1 Release this package as Apache Mesos 1.3.3
>>>> [ ] -1 Do not release this package because ...
>>>>
>>>> Thanks,
>>>>
>>>> MPark
>>>>
>>>
>>>
>>

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

[Michael Park]

Huh... 樂 Super weird. I'll look into it.

Thanks for checking!

MPark

On Wed, May 23, 2018 at 11:34 AM Vinod Kone <vinodk...@apache.org> wrote:

> It's empty for me too!
>
> On Wed, May 23, 2018 at 11:32 AM, Benjamin Mahler <bmah...@apache.org>
> wrote:
>
>> Thanks Michael!
>>
>> Looks like the tar.gz is empty, is it just me?
>>
>> On Tue, May 22, 2018 at 10:09 PM, Michael Park <mp...@apache.org> wrote:
>>
>>> Hi all,
>>>
>>> Please vote on releasing the following candidate as Apache Mesos 1.3.3.
>>>
>>> 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.3.3-rc1
>>>
>>> 
>>>
>>> The candidate for Mesos 1.3.3 release is available at:
>>> https://dist.apache.org/repos/dist/dev/mesos/1.3.3-rc1/mesos-1.3.3.tar.gz
>>>
>>> The tag to be voted on is 1.3.3-rc1:
>>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.3-rc1
>>>
>>> The SHA512 checksum of the tarball can be found at:
>>>
>>> https://dist.apache.org/repos/dist/dev/mesos/1.3.3-rc1/mesos-1.3.3.tar.gz.sha512
>>>
>>> The signature of the tarball can be found at:
>>>
>>> https://dist.apache.org/repos/dist/dev/mesos/1.3.3-rc1/mesos-1.3.3.tar.gz.asc
>>>
>>> The PGP key used to sign the release is here:
>>> https://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-1226
>>>
>>> Please vote on releasing this package as Apache Mesos 1.3.3!
>>>
>>> The vote is open until Fri May 25 22:07:39 PDT 2018 and passes if a
>>> majority of at least 3 +1 PMC votes are cast.
>>>
>>> [ ] +1 Release this package as Apache Mesos 1.3.3
>>> [ ] -1 Do not release this package because ...
>>>
>>> Thanks,
>>>
>>> MPark
>>>
>>
>>
>

[VOTE] Release Apache Mesos 1.3.3 (rc1)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 1.3.3.

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.3.3-rc1


The candidate for Mesos 1.3.3 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.3-rc1/mesos-1.3.3.tar.gz

The tag to be voted on is 1.3.3-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.3-rc1

The SHA512 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.3-rc1/mesos-1.3.3.tar.gz.sha512

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.3-rc1/mesos-1.3.3.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1226

Please vote on releasing this package as Apache Mesos 1.3.3!

The vote is open until Fri May 25 22:07:39 PDT 2018 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.3.3
[ ] -1 Do not release this package because ...

Thanks,

MPark

Anyone using a custom Sorter?

[Michael Park]

I'm not even sure if anyone's using a custom Allocator, but
is anyone using a custom Sorter? It doesn't seem like there's
even a module for it so it wouldn't be dynamically loaded.

Perhaps you have a fork with a custom Sorter?

Please let me know,

Thanks!

MPark

Re: http://mesos.apache.org/downloads/ is not up to date

[Michael Park]

Ack, I'll take care of this tomorrow!

On Mon, Feb 12, 2018 at 3:17 PM, Benjamin Mahler  wrote:

> Thanks for pointing this out Adam, I've added mpark who is the release
> manager for 1.3.2.
>
> On Tue, Feb 6, 2018 at 6:12 AM, Adam Cecile  wrote:
>
>> Hi guys,
>>
>>
>> Did you notice Mesos 1.3.2 is missing from the official download page ?
>>
>> http://mesos.apache.org/downloads/
>>
>>
>> Regards, Adam.
>>
>>
>

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

[Michael Park]

Hi all,

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

+1 (Binding)
--
Benjamin Mahler
Vinod Kone
Michael Park

There were no 0 or -1 votes.

Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/1.3.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.3.2

The mesos-1.3.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,

MPark

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

[Michael Park]

+1 (binding)

Successfully ran:
```
CC=clang CXX=clang++ ../configure --enable-optimize
--enable-lock-free-run-queue --enable-lock-free-event-queue
--enable-last-in-first-out-fixed-size-semaphore
make check
```

CentOS Linux release 7.4.1708 (Core)
Clang 5.0.1

MPark

On Fri, Dec 15, 2017 at 3:48 PM Vinod Kone <vinodk...@apache.org> wrote:

> +1 (binding)
>
> Tested on ASF CI. Red builds are flaky tests due to the known perf core
> dump issue that has been fixed since.
> *Revision*: 17ab9ff8b35f5ec877f08698e28301bec030d010
>
>- refs/tags/1.3.2-rc1
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl autotools
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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: Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/45/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 Thu, Dec 14, 2017 at 5:38 PM, Benjamin Mahler <bmah...@apache.org>
> wrote:
>
> > +1 (binding)
> >
> > make check passes on macOS 10.13.2 with Apple LLVM version 9.0.

[VOTE] Release Apache Mesos 1.3.2 (rc1)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 1.3.2.

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.3.2-rc1


The candidate for Mesos 1.3.2 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.2-rc1/mesos-1.3.2.tar.gz

The tag to be voted on is 1.3.2-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.2-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.2-rc1/mesos-1.3.2.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.2-rc1/mesos-1.3.2.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1220

Please vote on releasing this package as Apache Mesos 1.3.2!

The vote is open until Wed, Dec 13 and passes if a majority of at least 3
+1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.3.2
[ ] -1 Do not release this package because ...

Thanks,

MPark

1.3.2 Release

[Michael Park]

Please reply to this email if you have pending patches to be backported to
1.3.x, I'm aiming to cut a 1.3.2 on Friday.

Thanks,

MPark

Re: [VOTE] Release Apache Mesos 1.4.0 (rc5)

[Michael Park]

Vinod, regarding MESOS-7729
:

I found MESOS-6345  related
to persistent volume framework, which leads me to believe that this is not
new.

Thanks,

MPark

On Tue, Sep 12, 2017 at 12:01 PM Vinod Kone  wrote:

> Tested this on ASF CI.
>
> Saw 3 flaky tests.
>
> https://issues.apache.org/jira/browse/MESOS-7729
> 
>
> https://issues.apache.org/jira/browse/MESOS-7971
> https://issues.apache.org/jira/browse/MESOS-7972
>
> The first one was a known (since 1.4.0) flaky test with a double free
> corruption. @Kapil and @MPark can you verify that this is an issue with the
> test and not the source code? Once verified, I'll give a +1.
>
> *Revision*: b3fd2e7ab26e118222fe18af4b92c53a3c01e6cc
>
>- refs/tags/1.4.0-rc5
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl autotools
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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: Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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: Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/42/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 Sat, Sep 9, 2017 at 6:49 AM, Kapil Arya  wrote:
>
> > Hi all,
> >
> > [NOTE: Starting with this RC candidate, we will not be "releasing" RC jar
> > files in the Maven release channel. This prevents polluting of the Maven
> > repositories with numerous RC tags. As before, you can continue to test
> the
> > release 

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

[Michael Park]

-1

I found MESOS-7922 ,
which is an issue around the communication between
old masters and new agents. Currently, the new agent re-registers with
the tasks and executors in the new format. The new master conditionally
upgrades the resources depending on whether the agent has the
RESERVATION_REFINEMENT capability, but the old master does not know
to this. The old master would incorrectly interpret any reserved resources
in the tasks / executors as unreserved.

On Mon, Aug 28, 2017 at 10:32 AM Kapil Arya  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.4.0.
>
> 1.4.0 includes the following:
>
> 
>   * Ability to recover the agent ID after a host reboot.
>   * File-based and image-pull secrets.
>   * Linux ambient and bounding capabilities support.
>   * Ability to efficiently measure disk usage without enforcing usage
> constraints.
>   * Hierarchical resource allocation roles. [EXPERIMENTAL]
>
> 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.4.0-rc3
> 
>
>
> The candidate for Mesos 1.4.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos-1.4.0.tar.gz
>
> The tag to be voted on is 1.4.0-rc3:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.4.0-rc3
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos-1.4.0.tar.gz.md5
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc3/mesos-1.4.0.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://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-1212
>
> Please vote on releasing this package as Apache Mesos 1.4.0!
>
> The vote is open until Thursday, Aug 31 11:59 PM PDT 2017 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.4.0
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Anand and Kapil
>

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

[Michael Park]

Hi all,

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

+1 (Binding)
--
Vinod Kone
Benjamin Mahler
Michael Park

There were no 0 or -1 votes.

Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/1.3.1

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.3.1

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

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

Thanks,

MPark

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

[Michael Park]

+1 (binding)

Successfully ran `make check`:

CentOS Linux release 7.3.1611 (Core)
g++ (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6)

./configure --enable-libevent --enable-ssl --enable-optimize
--disable-python && make check

On Wed, Aug 2, 2017 at 1:36 PM Benjamin Mahler <bmah...@apache.org> wrote:

> +1 (binding)
>
> ./configure CC=clang CXX=clang++ CXXFLAGS=-Wno-deprecated-declarations
> --disable-python --disable-java --with-apr=/usr/local/opt/apr/libexec
> --with-svn=/usr/local/opt/subversion && make check -j8
>
> Ran into a known flaky test:
> https://issues.apache.org/jira/browse/MESOS-7739
>
> On Tue, Aug 1, 2017 at 8:26 PM, Vinod Kone <vinodk...@apache.org> wrote:
>
>> +1 (binding)
>>
>> Tested on ASF CI. The 2 red builds are known flaky tests (health checks)
>> and a perf core dump issue that's fixed on HEAD.
>>
>> *Revision*: 1beaede8c13f0832d4921121da34f924deec8950
>>
>>- refs/tags/1.3.1-rc1
>>
>> Configuration Matrix gcc clang
>> centos:7 --verbose --enable-libevent --enable-ssl autotools
>> [image: Failed]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/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]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/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]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/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]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/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]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/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: Success]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/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]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/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]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/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: Success]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/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]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/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]
>> <
>> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/37/BUILDTOOL=cmake,COMPILER=gcc,C

[VOTE] Release Apache Mesos 1.3.1 (rc1)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 1.3.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.3.1-rc1


The candidate for Mesos 1.3.1 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.1-rc1/mesos-1.3.1.tar.gz

The tag to be voted on is 1.3.1-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.1-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.1-rc1/mesos-1.3.1.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.1-rc1/mesos-1.3.1.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1200

Please vote on releasing this package as Apache Mesos 1.3.1!

The vote is open until *Aug 2, 2017* and passes if a majority of at least 3
+1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.3.1
[ ] -1 Do not release this package because ...

Thanks,

MPark

Mesos 1.3.1 Release

[Michael Park]

I'm planning to cut the 1.3.1 release on Friday July 28, 2017 and have
voting start on the following Monday.

Please let me know if you have any patches that you're working on, targeted
for 1.3.1.

If you have, or are planning to backport patches for 1.3.1, please make
sure to update
the CHANGELOG as well. (From what I've seen so far, it seemed to be being
updated accordingly. Thanks!)

MPark

Re: Framework change role

[Michael Park]

What is it that you need help with?

On Tue, Jul 4, 2017 at 11:12 AM Thodoris Zois  wrote:

> Hello list,
>
> Is anybody available to help me with the new feature of 1.3.0 version,
> that a framework can modify its role?
>
> Thank you

Mesos Kanban board

[Michael Park]

The following is the filter for our Community Kanban Board on JIRA
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=1=MESOS-7403=286=289
for
*assigned* and *missing shepherd*.

If you're working on a ticket (*in progress* or *reviewable*) and you don't
have a shepherd, please either find one or add the shepherd to the ticket!

We'll review this board again at the next community meeting.

Thanks,

MPark

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

[Michael Park]

Hi all,

The vote for Mesos 1.3.0 (rc3) has passed with the
following votes.

+1 (Binding)
--
Vinod Kone
Benjamin Mahler
Yan Xu

+1 (Non-binding)
--
N/A

There were no 0 or -1 votes.

Please find the release at:
/1.3.0

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.3.0

The mesos-1.3.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,

MPark & Neil

Re: Plan for upgrading protobuf==3.2.0 in Mesos

[Michael Park]

Thanks Anand and Zhitao!

On Fri, May 26, 2017 at 3:40 PM Anand Mazumdar  wrote:

> We recently committed this [1] and it would be part of the *next major
> release* (1.4.0). Also, we upgraded to the newer protobuf release 3.3.0.
>
> For Mesos developers, this means that we can use proto3 features like arena
> allocation [2], maps [3] etc. Note that we still need to use the proto2
> syntax version for backward compatibility.
>
> Thanks Zhitao for the contributions!
>
> [1] https://issues.apache.org/jira/browse/MESOS-7228
> [2] https://issues.apache.org/jira/browse/MESOS-5783
> [3] https://developers.google.com/protocol-buffers/docs/proto#maps
>
> -anand
>
>
> On Thu, Apr 27, 2017 at 10:28 AM, Anand Mazumdar  wrote:
>
> > + dev
> >
> > Bumping up the thread to ensure it's not missed.
> >
> > -anand
> >
> > On Tue, Apr 25, 2017 at 11:01 AM, Zhitao Li 
> wrote:
> > > Dear framework owners and users,
> > >
> > > We are working on upgrading the protobuf library in Mesos to 3.2.0 in
> > > https://issues.apache.org/jira/browse/MESOS-7228, to overcome some
> > protobuf
> > > limitation on message size as well as preparing for further
> improvement.
> > We
> > > aim to release this with the upcoming Mesos 1.3.0.
> > >
> > > Because we upgraded the protoc compiler in this process, all generated
> > java
> > > and python code may not be compatible with protobuf 2.6.1 (the previous
> > > dependency), and we ask you to upgrade the protobuf dependency to 3.2.0
> > when
> > > you upgrade your framework dependency to 1.3.0.
> > >
> > > For java, a snapshot maven artifact has been prepared (by Anand
> > Mazumdar's
> > > courtesy) at
> > > https://repository.apache.org/content/repositories/
> > snapshots/org/apache/mesos/mesos/1.3.0-SNAPSHOT/
> > > . Please feel free to play out with it and let us know if you run into
> > any
> > > issues.
> > >
> > > Note that the binary upgrade process should still be compatible: any
> > java or
> > > based framework (scheduler or executor) should still work out of box
> with
> > > Mesos 1.3.0 once released. It is suggested to get your cluster upgraded
> > to
> > > 1.3.0 first, then come back and upgrade your executors and schedulers.
> > >
> > > We understand this may expose inconvenience around updating the
> protobuf
> > > dependency, so please let us know if you have any concern or further
> > > questions.
> > >
> > > --
> > >
> > > Cheers,
> > >
> > > Zhitao Li and Anand Mazumdar,
> >
>

[VOTE] Release Apache Mesos 1.3.0 (rc3)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 1.3.0.


1.3.0 includes the following:

  - Multi-role framework support
  - Executor authentication support
  - Allow frameworks to modify their roles.

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.3.0-rc3


The candidate for Mesos 1.3.0 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz

The tag to be voted on is 1.3.0-rc3:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.0-rc3

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc3/mesos-1.3.0.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1198

Please vote on releasing this package as Apache Mesos 1.3.0!

The vote is open until Tue May 30 11:59:59 PDT 2017 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.3.0
[ ] -1 Do not release this package because ...

Thanks,

MPark & Neil

[VOTE] Release Apache Mesos 1.3.0 (rc2)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 1.3.0.


1.3.0 includes the following:

  - Multi-role framework support
  - Executor authentication support
  - Allow frameworks to modify their roles.

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.3.0-rc2


The candidate for Mesos 1.3.0 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc2/mesos-1.3.0.tar.gz

The tag to be voted on is 1.3.0-rc2:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.0-rc2

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc2/mesos-1.3.0.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc2/mesos-1.3.0.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1196

Please vote on releasing this package as Apache Mesos 1.3.0!

The vote is open until Mon May 22 11:59:59 PDT 2017 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.3.0
[ ] -1 Do not release this package because ...

Thanks,

MPark & Neil

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

[Michael Park]

This vote has failed, we'll cut an rc2 shortly.

MESOS-7378, MESOS-7471, MESOS-7478 have been fixed, and MESOS-7460 is not
an issue.

MESOS-7431 <https://issues.apache.org/jira/browse/MESOS-7431> is our only
blocker currently. Will this be committed today? CC Gilbert

Thanks,

MPark


On Tue, May 9, 2017 at 2:01 PM, Benjamin Mahler <bmah...@apache.org> wrote:

> -1 (binding)
>
> Two upgrade blockers, these need to be backported to 1.2.x as well:
>
> https://issues.apache.org/jira/browse/MESOS-7478 (I have a patch already)
> https://issues.apache.org/jira/browse/MESOS-7460 (mpark is working on
> this)
>
> Re: MESOS-7378
> Any updates on whether this will be fixed?
>
> On Tue, May 9, 2017 at 1:02 AM, Jie Yu <yujie@gmail.com> wrote:
>
>> -1
>>
>> I want to get this fix into 1.3.0
>> https://issues.apache.org/jira/browse/MESOS-7471
>>
>> - Jie
>>
>> On Tue, May 9, 2017 at 1:14 AM, Yan Xu <y...@jxu.me> wrote:
>>
>>> We work around autotools and protobuf bugs and glibc is only harder for
>>> users and developers to upgrade. :)
>>>
>>> I agree that we can establish the minimum glibc version/linux distro
>>> releases etc we support but currently we don't and there are folks who use
>>> Mesos that depend on this version.
>>>
>>> We should follow http://mesos.apache.org/documentation/latest/versioni
>>> ng/ and when answers are not in there, we should seek consensus to
>>> improve the process and update the doc and give folks adequate time to
>>> adjust to the new or better defined) process. In the meantime, I think we
>>> shouldn't break the current users.
>>>
>>> ---
>>> Jiang Yan Xu <y...@jxu.me> | @xujyan <https://twitter.com/xujyan>
>>>
>>> On Mon, May 8, 2017 at 3:59 PM, Neil Conway <neil.con...@gmail.com>
>>> wrote:
>>>
>>>> Personally, I'm not convinced that we need to fix MESOS-7378. The
>>>> problem is essentially a bug in glibc that was fixed 6 years ago. (As
>>>> a point of reference, the oldest version of g++ we support was
>>>> released 2 years ago... :) )
>>>>
>>>> Neil
>>>>
>>>> On Mon, May 8, 2017 at 3:45 PM, Yan Xu <y...@jxu.me> wrote:
>>>> > I am still hoping that we get
>>>> > https://issues.apache.org/jira/browse/MESOS-7378 fixed before
>>>> shipping
>>>> > 0.13.0. :)
>>>> >
>>>> > ---
>>>> > Jiang Yan Xu <y...@jxu.me> | @xujyan
>>>> >
>>>> > On Fri, May 5, 2017 at 6:31 PM, Michael Park <mp...@apache.org>
>>>> wrote:
>>>> >>
>>>> >> Hi all,
>>>> >>
>>>> >> Please vote on releasing the following candidate as Apache Mesos
>>>> 1.3.0.
>>>> >>
>>>> >>
>>>> >> 1.3.0 includes the following:
>>>> >>
>>>> >> 
>>>> 
>>>> >>   - Multi-role framework support
>>>> >>   - Executor authentication support
>>>> >>   - Allow frameworks to modify their roles.
>>>> >>   - Hierarchical roles (*EXPERIMENTAL*)
>>>> >>
>>>> >> The CHANGELOG for the release is available at:
>>>> >>
>>>> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
>>>> lain;f=CHANGELOG;hb=1.3.0-rc1
>>>> >>
>>>> >> 
>>>> 
>>>> >>
>>>> >> The candidate for Mesos 1.3.0 release is available at:
>>>> >> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos
>>>> -1.3.0.tar.gz
>>>> >>
>>>> >> The tag to be voted on is 1.3.0-rc1:
>>>> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit
>>>> ;h=1.3.0-rc1
>>>> >>
>>>> >> The MD5 checksum of the tarball can be found at:
>>>> >>
>>>> >> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos
>>>> -1.3.0.tar.gz.md5
>>>> >>
>>>> >> The signature of the tarball can be found at:
>>>> >>
>>>> >> https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos
>>>> -1.3.0.tar.gz.asc
>>>> >>
>>>> >> The PGP key used to sign the release is here:
>>>> >> https://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/orgapache
>>>> mesos-1190
>>>> >>
>>>> >> Please vote on releasing this package as Apache Mesos 1.3.0!
>>>> >>
>>>> >> The vote is open until Wed May 10 11:59:59 PDT 2017 and passes if a
>>>> >> majority of at least 3 +1 PMC votes are cast.
>>>> >>
>>>> >> [ ] +1 Release this package as Apache Mesos 1.3.0
>>>> >> [ ] -1 Do not release this package because ...
>>>> >>
>>>> >> Thanks,
>>>> >>
>>>> >> MPark & Neil
>>>> >
>>>> >
>>>>
>>>
>>>
>>
>

[VOTE] Release Apache Mesos 1.3.0 (rc1)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 1.3.0.


1.3.0 includes the following:

  - Multi-role framework support
  - Executor authentication support
  - Allow frameworks to modify their roles.
  - Hierarchical roles (*EXPERIMENTAL*)

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.3.0-rc1


The candidate for Mesos 1.3.0 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos-1.3.0.tar.gz

The tag to be voted on is 1.3.0-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.0-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos-1.3.0.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.3.0-rc1/mesos-1.3.0.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1190

Please vote on releasing this package as Apache Mesos 1.3.0!

The vote is open until Wed May 10 11:59:59 PDT 2017 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 1.3.0
[ ] -1 Do not release this package because ...

Thanks,

MPark & Neil

Mesos YouTube Channel

[Michael Park]

I've created a brand channel for Mesos on YouTube for community activities:
https://www.youtube.com/channel/UC0wxLxgX8ilUn0m31lCpzAw.

The only community activities currently captured in the channel are:
  - Developer Community Meetings, and
  - MesosCon presentations I've collected as "Saved Playlists".

Going forward, I think we can use this channel for work group meetings as
well
once those are a little more fleshed out.

Thanks,

MPark

Community Engagement at MesosCon

[Michael Park]

Hi everyone,

I look forward to seeing you at #MesosCon
 next
week. I would like to announce a few community engagement events planned
for the conference.

Apache Mesos will have a booth setup in the #MesosCon exhibit area. It will
be a place of gathering for committers, contributors and everyone else
interested. We encourage all of you to spend time at the booth, especially
during breaks so that someone is there to welcome new members and conduct
conversation throughout the conference. There will be stickers and power
available at the booth.

Next Friday, after the MesosCon hackathon, Mesosphere will sponsor the
first Mesos + DC/OS community sync with beers and good conversation.
Mesosphere would like to invite Apache Mesos committers, contributors and
everyone else interested in discussing how these two communities can work
together now and in the future. Come join!

*Mesos + DC/OS Community Sync*

Event date: Friday, June 3

Time: 3:00pm - 4:30pm

Location: Hyatt Regency Tech Center, Denver, Colorado

Room: Wind River


RSVP: Please submit your rsvp here


See you in Denver!

Don't forget to register for #MesosCon
, June 1-3

Thanks,

MPark

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

[Michael Park]

Hi all,

The vote for Mesos 0.25.1 (rc4) has passed with the
following votes.

+1 (Binding)
--
Benjamin Mahler
Vinod Kone
Kapil Arya

+1 (Non-binding)
--
N/A

There were no 0 or -1 votes.

Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/0.25.1

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=0.25.1

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

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

Thanks,

MPark

[RESULT][VOTE] Release Apache Mesos 0.24.2 (rc5)

[Michael Park]

Hi all,

The vote for Mesos 0.24.2 (rc5) has passed with the
following votes.

+1 (Binding)
--
* Benjamin Mahler
* Vinod Kone
* Kapil Arya

+1 (Non-binding)
--
N/A

There were no 0 or -1 votes.

Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/0.24.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=0.24.2

The mesos-0.24.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,

MPark

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

[Michael Park]

+1 (binding)

Internal CI results with the corresponding JIRA tickets for the failed
tests:

CentOS 6 (non-SSL):
CentOS 6 (SSL):
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 ,
MESOS-4053 )

CentOS 7 (non-SSL):
  - HealthCheckTest.ROOT_DOCKER_DockerHealthyTask
(MESOS-4604 )

CentOS 7 (SSL):
  -
LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystemCommandExecutorWithVolumes
(Segfault during test teardown, likely addressed in 0.29.0 by MESOS-4633
 and MESOS-4634
)

Debian 8 (non-SSL):
Debian 8 (SSL):
  - HealthCheckTest.ROOT_DOCKER_DockerHealthyTask
(MESOS-4604 )

Ubuntu 12 (non-SSL): Success!
Ubuntu 12 (SSL):Success!
Ubuntu 14 (non-SSL): Success!
Ubuntu 14 (SSL):Success!
Ubuntu 15 (non-SSL): Success!
Ubuntu 15 (SSL):Success!

On 5 April 2016 at 22:30, Greg Mann  wrote:

> +1 (non-binding)
>
> Ran `sudo make check` on CentOS 7 with libevent and SSL enabled; all tests
> pass.
>
> I was also able to successfully simulate a simple upgrade scenario using
> 'test-upgrade.py'. Note that this initially failed due to some changes made
> to the test framework in this release, but after applying this patch
>  the upgrade script succeeds. While
> ideally this patch for the upgrade script would be included in the release,
> I don't consider it to be a blocker. If we end up cutting another RC, it
> would be great to include.
>
> Cheers,
> Greg
>
>
> On Tue, Apr 5, 2016 at 6:30 PM, Jie Yu  wrote:
>
> > Hi all,
> >
> > Please vote on releasing the following candidate as Apache Mesos 0.28.1.
> >
> >
> > 0.28.1 includes the following bug fixes:
> >
> >
> 
> >
> > [MESOS-4662] - PortMapping network isolator should not assume
> > BIND_MOUNT_ROOT is a realpath.
> > [MESOS-4874] - overlayfs does not work with kernel 4.2.3
> > [MESOS-4877] - Mesos containerizer can't handle top level docker image
> > like "alpine" (must use "library/alpine")
> > [MESOS-4878] - Task stuck in TASK_STAGING when docker fetcher failed to
> > fetch the image
> > [MESOS-4964] - curl based docker fetcher fails to decode chunked encoding
> > [MESOS-4985] - Destroy a container while it's provisioning can lead to
> > leaked provisioned directories.
> > [MESOS-5009] - local docker puller fails to find private registry
> > repositories
> > [MESOS-5018] - FrameworkInfo Capability enum does not support upgrades.
> > [MESOS-5021] - Memory leak in subprocess when 'environment' argument is
> > provided.
> > [MESOS-5023] - MesosContainerizerProvisionerTest.DestroyWhileProvisioning
> > is flaky.
> > [MESOS-5114] - Flags::parse does not handle empty string correctly.
> >
> > 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=0.28.1-rc2
> >
> >
> 
> >
> > The candidate for Mesos 0.28.1 release is available at:
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.28.1-rc2/mesos-0.28.1.tar.gz
> >
> > The tag to be voted on is 0.28.1-rc2:
> >
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.28.1-rc2
> >
> > The MD5 checksum of the tarball can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.28.1-rc2/mesos-0.28.1.tar.gz.md5
> >
> > The signature of the tarball can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.28.1-rc2/mesos-0.28.1.tar.gz.asc
> >
> > The PGP key used to sign the release is here:
> > https://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-1132
> >
> > Please vote on releasing this package as Apache Mesos 0.28.1!
> >
> > The vote is open until Fri Apr  8 18:29:07 PDT 2016 and passes if a
> > majority of at least 3 +1 PMC votes are cast.
> >
> > [ ] +1 Release this package as Apache Mesos 0.28.1
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> > - Jie
> >
>

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

[Michael Park]

s/No changes from rc4/No changes from rc3/
s/New fixes in rc5/New fixes in rc4/

On 5 April 2016 at 23:18, Michael Park <mp...@apache.org> wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 0.25.1.
>
>
> 0.25.1 includes the following:
>
> 
> No changes from rc4:
>
> * Improvements
>   - `/state` endpoint performance
>   - `systemd` integration
>   - GLOG performance
>   - Configurable task/framework history
>   - Offer filter timeout fix for backlogged allocator
>   - JSON-based credential files. (MESOS-3560)
>   - Mesos health check within docker container. (MESOS-3738)
>   - Deletion of special files. (MESOS-4979)
>   - Memory leak in subprocess. (MESOS-5021)
>
> * Bugs
>   - SSL
>   - Libevent
>   - Fixed point resources math
>   - HDFS
>   - Agent upgrade compatibility
>   - Health checks
>
> New fixes in rc5:
>   - Build failure on OS 10.11 using Xcode 7. (MESOS-3030)
>   - ExamplesTest.PersistentVolumeFramework does not work in OS X El
> Capitan. (MESOS-3604)
>
> Thank you to Evan Krall from Yelp for requesting MESOS-3560 and
> MESOS-3738 to be included,
> and Ben Mahler for requesting MESOS-3030, MESOS-3604, MESOS-4979 and
> MESOS-5021.
>
> 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=0.25.1-rc4
>
> 
>
> The candidate for Mesos 0.25.1 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc4/mesos-0.25.1.tar.gz
>
> The tag to be voted on is 0.25.1-rc4:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.25.1-rc4
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc4/mesos-0.25.1.tar.gz.md5
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc4/mesos-0.25.1.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://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-1136
>
> Please vote on releasing this package as Apache Mesos 0.25.1!
>
> The vote is open until Fri Apr 8 23:59:59 PDT 2016 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 0.25.1
> [ ] -1 Do not release this package because ...
>
> Thanks,
>
> MPark
>

[VOTE] Release Apache Mesos 0.26.1 (rc4)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.26.1.


0.26.1 includes the following:

No changes from rc3:

* Improvements
  - `/state` endpoint performance
  - `systemd` integration
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator
  - Deletion of special files. (MESOS-4979)
  - Memory leak in subprocess. (MESOS-5021)

* Bugs
  - SSL
  - Libevent
  - Fixed point resources math
  - HDFS
  - Agent upgrade compatibility

New fixes in rc4:
  - https://reviews.apache.org/r/42704 which was missed in MESOS-920.

Thank you to Ben Mahler for requesting MESOS-4979 and MESOS-5021 to be
included.

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=0.26.1-rc4


The candidate for Mesos 0.26.1 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc4/mesos-0.26.1.tar.gz

The tag to be voted on is 0.26.1-rc4:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.26.1-rc4

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc4/mesos-0.26.1.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc4/mesos-0.26.1.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1138

Please vote on releasing this package as Apache Mesos 0.26.1!

The vote is open until Fri Apr 8 23:59:59 PDT 2016 and passes if a majority
of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.26.1
[ ] -1 Do not release this package because ...

Thanks,

MPark

[VOTE] Release Apache Mesos 0.24.2 (rc5)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.24.2.


0.24.2 includes the following:

No changes from rc4:

* Improvements
- Allocator filter performance
- Port Ranges performance
- UUID performance
- `/state` endpoint performance
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator
  - JSON-based credential files. (MESOS-3560)
  - Mesos health check within docker container. (MESOS-3738)
  - Deletion of special files. (MESOS-4979)
  - Memory leak in subprocess. (MESOS-5021)

* Bugs
  - SSL
  - Libevent
  - Fixed point resources math
  - HDFS
  - Agent upgrade compatibility
  - Health checks

New fixes in rc5:
  - Build failure on OS 10.11 using Xcode 7. (MESOS-3030)
  - ExamplesTest.PersistentVolumeFramework does not work in OS X El
Capitan. (MESOS-3604)

Thank you to Evan Krall from Yelp for requesting MESOS-3560 and MESOS-3738
to be included,
and Ben Mahler for requesting MESOS-3030, MESOS-3604, MESOS-4979 and
MESOS-5021.

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=0.24.2-rc5


The candidate for Mesos 0.24.2 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc5/mesos-0.24.2.tar.gz

The tag to be voted on is 0.24.2-rc5:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.2-rc5

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc5/mesos-0.24.2.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc5/mesos-0.24.2.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1134

Please vote on releasing this package as Apache Mesos 0.24.2!

The vote is open until Fri Apr 8 23:59:59 PDT 2016 and passes if a majority
of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.24.2
[ ] -1 Do not release this package because ...

Thanks,

MPark

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

[Michael Park]

I synced with Ben on this. I'll be cut another RC for 0.24.2, 0.25.1 as
well as 0.26.1 tonight.

On 31 March 2016 at 22:47, Michael Park <mp...@apache.org> wrote:

> Hey Ben,
>
> I was able to observe the error you're pointing out for 0.26.1-rc3.
>
> With 0.24.2-rc4 and 0.25.1-rc3 however, I observed the deprecated SASL
> warning that gets propagated as an error.
>
> For example:
>
> ./../../src/authentication/cram_md5/authenticatee.cpp:75:7: error:
> 'sasl_dispose' is deprecated: first deprecated in OS X 10.11
> [-Werror,-Wdeprecated-declarations]
>   sasl_dispose();
>
> How did you encounter the issues with 0.24.2-rc4 and 0.25.1-rc3? Are you
> still running OS X Yosemite?
>
> Also, I think I was under the impression that we don't officially support
> OS X aside from convenience for developers.
> I ask because rc2s for 0.24.2 and 0.25.1 had the same SASL issues which
> made them not compile on OS X El Capitan.
>
> If it is, I'll cut a new rc with the SASL warning patches as well as the
> glog patch. Just wanted to confirm.
>
> Thanks,
>
> MPark
>
> On 31 March 2016 at 21:30, Benjamin Mahler <bmah...@apache.org> wrote:
>
>> I'm seeing the following on OS X for the three RCs that were sent out:
>>
>> $ ./configure CC=clang CXX=clang++ --disable-python --disable-java
>> ...
>> $ make check -j7
>> ...
>> ./mesos-tests
>> dyld: Symbol not found: __ZN3fLB21FLAGS_drop_log_memoryE
>>   Referenced from:
>> /Users/bmahler/tmp/testing/mesos-0.24.2/src/.libs/libmesos-0.24.2.dylib
>>   Expected in: flat namespace
>>  in
>> /Users/bmahler/tmp/testing/mesos-0.24.2/src/.libs/libmesos-0.24.2.dylib
>>
>> I think we need the following patch as well from the glog change:
>>
>> commit 363b0b059bdc7742b2258a33ebfe430fd03f4311
>> Author: Kapil Arya <ka...@mesosphere.io>
>> Date:   Mon Jan 25 00:41:17 2016 -0500
>>
>> Fixed non-linux build involving glog drop_log_meory flag.
>>
>> The variable "FLAGS_drop_log_memory" is available only on Linux.
>>
>> Review: https://reviews.apache.org/r/42704
>>
>> On Thu, Mar 31, 2016 at 3:28 PM, Michael Park <mp...@apache.org> wrote:
>>
>>> Hi all,
>>>
>>> Please vote on releasing the following candidate as Apache Mesos 0.24.2.
>>>
>>> NOTE: I made a mistake of not updating the CHANGELOG for rc3, which is
>>> why this is an rc4.
>>>
>>> 0.24.2 includes the following:
>>>
>>> 
>>> No changes from rc2:
>>>
>>> * Improvements
>>> - Allocator filter performance
>>> - Port Ranges performance
>>> - UUID performance
>>> - `/state` endpoint performance
>>>   - GLOG performance
>>>   - Configurable task/framework history
>>>   - Offer filter timeout fix for backlogged allocator
>>>
>>> * Bugs
>>>   - SSL
>>>   - Libevent
>>>   - Fixed point resources math
>>>   - HDFS
>>>   - Agent upgrade compatibility
>>>   - Health checks
>>>
>>> New fixes in rc4:
>>>
>>>   - JSON-based credential files. (MESOS-3560)
>>>   - Mesos health check within docker container. (MESOS-3738)
>>>   - Deletion of special files. (MESOS-4979)
>>>   - Memory leak in subprocess. (MESOS-5021)
>>>
>>> Thank you to Evan Krall from Yelp for requesting MESOS-3560 and
>>> MESOS-3738 to be included,
>>> and Ben Mahler for requesting MESOS-4979 and MESOS-5021.
>>>
>>> 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=0.24.2-rc4
>>>
>>> 
>>>
>>> The candidate for Mesos 0.24.2 release is available at:
>>>
>>> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc4/mesos-0.24.2.tar.gz
>>>
>>> The tag to be voted on is 0.24.2-rc4:
>>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.2-rc4
>>>
>>> The MD5 checksum of the tarball can be found at:
>>>
>>> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc4/mesos-0.24.2.tar.gz.md5
>>>
>>> The signature of the tarball can be found at:
>>>
>>> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc4/mesos-0.24.2.tar.gz.asc
>>>
>>> The PGP key used to sign the release is here:
>>> https://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-1124
>>>
>>> Please vote on releasing this package as Apache Mesos 0.24.2!
>>>
>>> The vote is open until Mon Apr 4 23:59:59 EDT 2016 and passes if a
>>> majority of at least 3 +1 PMC votes are cast.
>>>
>>> [ ] +1 Release this package as Apache Mesos 0.24.2
>>> [ ] -1 Do not release this package because ...
>>>
>>> Thanks,
>>>
>>> MPark
>>>
>>
>>
>

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

[Michael Park]

Hey Ben,

I was able to observe the error you're pointing out for 0.26.1-rc3.

With 0.24.2-rc4 and 0.25.1-rc3 however, I observed the deprecated SASL
warning that gets propagated as an error.

For example:

./../../src/authentication/cram_md5/authenticatee.cpp:75:7: error:
'sasl_dispose' is deprecated: first deprecated in OS X 10.11
[-Werror,-Wdeprecated-declarations]
  sasl_dispose();

How did you encounter the issues with 0.24.2-rc4 and 0.25.1-rc3? Are you
still running OS X Yosemite?

Also, I think I was under the impression that we don't officially support
OS X aside from convenience for developers.
I ask because rc2s for 0.24.2 and 0.25.1 had the same SASL issues which
made them not compile on OS X El Capitan.

If it is, I'll cut a new rc with the SASL warning patches as well as the
glog patch. Just wanted to confirm.

Thanks,

MPark

On 31 March 2016 at 21:30, Benjamin Mahler <bmah...@apache.org> wrote:

> I'm seeing the following on OS X for the three RCs that were sent out:
>
> $ ./configure CC=clang CXX=clang++ --disable-python --disable-java
> ...
> $ make check -j7
> ...
> ./mesos-tests
> dyld: Symbol not found: __ZN3fLB21FLAGS_drop_log_memoryE
>   Referenced from:
> /Users/bmahler/tmp/testing/mesos-0.24.2/src/.libs/libmesos-0.24.2.dylib
>   Expected in: flat namespace
>  in /Users/bmahler/tmp/testing/mesos-0.24.2/src/.libs/libmesos-0.24.2.dylib
>
> I think we need the following patch as well from the glog change:
>
> commit 363b0b059bdc7742b2258a33ebfe430fd03f4311
> Author: Kapil Arya <ka...@mesosphere.io>
> Date:   Mon Jan 25 00:41:17 2016 -0500
>
> Fixed non-linux build involving glog drop_log_meory flag.
>
> The variable "FLAGS_drop_log_memory" is available only on Linux.
>
>     Review: https://reviews.apache.org/r/42704
>
> On Thu, Mar 31, 2016 at 3:28 PM, Michael Park <mp...@apache.org> wrote:
>
>> Hi all,
>>
>> Please vote on releasing the following candidate as Apache Mesos 0.24.2.
>>
>> NOTE: I made a mistake of not updating the CHANGELOG for rc3, which is
>> why this is an rc4.
>>
>> 0.24.2 includes the following:
>>
>> 
>> No changes from rc2:
>>
>> * Improvements
>> - Allocator filter performance
>> - Port Ranges performance
>> - UUID performance
>> - `/state` endpoint performance
>>   - GLOG performance
>>   - Configurable task/framework history
>>   - Offer filter timeout fix for backlogged allocator
>>
>> * Bugs
>>   - SSL
>>   - Libevent
>>   - Fixed point resources math
>>   - HDFS
>>   - Agent upgrade compatibility
>>   - Health checks
>>
>> New fixes in rc4:
>>
>>   - JSON-based credential files. (MESOS-3560)
>>   - Mesos health check within docker container. (MESOS-3738)
>>   - Deletion of special files. (MESOS-4979)
>>   - Memory leak in subprocess. (MESOS-5021)
>>
>> Thank you to Evan Krall from Yelp for requesting MESOS-3560 and
>> MESOS-3738 to be included,
>> and Ben Mahler for requesting MESOS-4979 and MESOS-5021.
>>
>> 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=0.24.2-rc4
>>
>> 
>>
>> The candidate for Mesos 0.24.2 release is available at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc4/mesos-0.24.2.tar.gz
>>
>> The tag to be voted on is 0.24.2-rc4:
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.2-rc4
>>
>> The MD5 checksum of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc4/mesos-0.24.2.tar.gz.md5
>>
>> The signature of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc4/mesos-0.24.2.tar.gz.asc
>>
>> The PGP key used to sign the release is here:
>> https://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-1124
>>
>> Please vote on releasing this package as Apache Mesos 0.24.2!
>>
>> The vote is open until Mon Apr 4 23:59:59 EDT 2016 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Mesos 0.24.2
>> [ ] -1 Do not release this package because ...
>>
>> Thanks,
>>
>> MPark
>>
>
>

[VOTE] Release Apache Mesos 0.26.1 (rc3)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.26.1.


0.26.1 includes the following:

No changes from rc2:

* Improvements
  - `/state` endpoint performance
  - `systemd` integration
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator

* Bugs
  - SSL
  - Libevent
  - Fixed point resources math
  - HDFS
  - Agent upgrade compatibility

New fixes in rc4:

  - Deletion of special files. (MESOS-4979)
  - Memory leak in subprocess. (MESOS-5021)

Thank you to Ben Mahler for requesting MESOS-4979 and MESOS-5021 to be
included.

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=0.26.1-rc3


The candidate for Mesos 0.26.1 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc3/mesos-0.26.1.tar.gz

The tag to be voted on is 0.26.1-rc3:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.26.1-rc3

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc3/mesos-0.26.1.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc3/mesos-0.26.1.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1128

Please vote on releasing this package as Apache Mesos 0.26.1!

The vote is open until Mon Apr 4 23:59:59 EDT 2016 and passes if a majority
of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.26.1
[ ] -1 Do not release this package because ...

Thanks,

MPark

[VOTE] Release Apache Mesos 0.25.1 (rc3)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.25.1.


0.25.1 includes the following:

No changes from rc2:

* Improvements
  - `/state` endpoint performance
  - `systemd` integration
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator

* Bugs
  - SSL
  - Libevent
  - Fixed point resources math
  - HDFS
  - Agent upgrade compatibility
  - Health checks

New fixes in rc4:

  - JSON-based credential files. (MESOS-3560)
  - Mesos health check within docker container. (MESOS-3738)
  - Deletion of special files. (MESOS-4979)
  - Memory leak in subprocess. (MESOS-5021)

Thank you to Evan Krall from Yelp for requesting MESOS-3560 and MESOS-3738
to be included,
and Ben Mahler for requesting MESOS-4979 and MESOS-5021.

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=0.25.1-rc3


The candidate for Mesos 0.25.1 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc3/mesos-0.25.1.tar.gz

The tag to be voted on is 0.25.1-rc3:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.25.1-rc3

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc3/mesos-0.25.1.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc3/mesos-0.25.1.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1126

Please vote on releasing this package as Apache Mesos 0.25.1!

The vote is open until Mon Apr 4 23:59:59 EDT 2016 and passes if a majority
of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.25.1
[ ] -1 Do not release this package because ...

Thanks,

MPark

[VOTE] Release Apache Mesos 0.24.2 (rc4)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.24.2.

NOTE: I made a mistake of not updating the CHANGELOG for rc3, which is why
this is an rc4.

0.24.2 includes the following:

No changes from rc2:

* Improvements
- Allocator filter performance
- Port Ranges performance
- UUID performance
- `/state` endpoint performance
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator

* Bugs
  - SSL
  - Libevent
  - Fixed point resources math
  - HDFS
  - Agent upgrade compatibility
  - Health checks

New fixes in rc4:

  - JSON-based credential files. (MESOS-3560)
  - Mesos health check within docker container. (MESOS-3738)
  - Deletion of special files. (MESOS-4979)
  - Memory leak in subprocess. (MESOS-5021)

Thank you to Evan Krall from Yelp for requesting MESOS-3560 and MESOS-3738
to be included,
and Ben Mahler for requesting MESOS-4979 and MESOS-5021.

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=0.24.2-rc4


The candidate for Mesos 0.24.2 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc4/mesos-0.24.2.tar.gz

The tag to be voted on is 0.24.2-rc4:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.2-rc4

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc4/mesos-0.24.2.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc4/mesos-0.24.2.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1124

Please vote on releasing this package as Apache Mesos 0.24.2!

The vote is open until Mon Apr 4 23:59:59 EDT 2016 and passes if a majority
of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.24.2
[ ] -1 Do not release this package because ...

Thanks,

MPark

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

[Michael Park]

Will do. Thanks!

On 23 March 2016 at 23:43, Benjamin Mahler <benjamin.mah...@gmail.com>
wrote:

> Also, I tagged https://issues.apache.org/jira/browse/MESOS-5021 with a
> fix version of 0.25.1. Can you include it?
>
> On Sat, Mar 19, 2016 at 6:33 AM, Michael Park <mcyp...@gmail.com> wrote:
>
>> 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/msg06204.html
>> <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 19:55, Michael Park <mp...@apache.org> wrote:
>>
>>> +1 (binding)
>>>
>>> Internal CI results with the corresponding JIRA tickets for the failed
>>> tests:
>>>
>>> CentOS 6 (non-SSL):
>>> CentOS 6 (SSL):
>>>   - Failed with MESOS-2017
>>> <https://issues.apache.org/jira/browse/MESOS-2017>
>>>
>>> CentOS 7 (non-SSL):
>>>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>>> (MESOS-4039 <https://issues.apache.org/jira/browse/MESOS-4039>)
>>>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>>> (MESOS-3215 <https://issues.apache.org/jira/browse/MESOS-3215>)
>>>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>>>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>>>   - LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
>>> (MESOS-3296 <https://issues.apache.org/jira/browse/MESOS-3296>)
>>>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
>>> (MESOS-3410 <https://issues.apache.org/jira/browse/MESOS-3410>)
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>>> (MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
>>> MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)
>>>
>>> CentOS 7 (SSL):
>>>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>>> (MESOS-4039 <https://issues.apache.org/jira/browse/MESOS-4039>)
>>>   - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
>>> (MESOS-2672 <https://issues.apache.org/jira/browse/MESOS-2672>)
>>>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>>> (MESOS-3215 <https://issues.apache.org/jira/browse/MESOS-3215>)
>>>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>>>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>>>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem
>>>   - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>>>   - LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
>>> (MESOS-3296 <https://issues.apache.org/jira/browse/MESOS-3296>)
>>>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
>>> (MESOS-3410 <https://issues.apache.org/jira/browse/MESOS-3410>)
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>>>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>>> (MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
>>> MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)
>>>
>>> Debian 8 (non-SSL):
>>> Debian 8 (SSL):
>>>   - Failed with MESOS-3964
>>> <https://issues.apache.org/jira/browse/MESOS-3964>
>>>
>>> Ubuntu 12 (non-SSL):
>>>   - DockerContainerizerTest.ROOT_DOCKER_Logs
>>> (MESOS-4676 <https://issues.apache.org/jira/browse/MESOS-4676>)
>>>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>>>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
>>> (MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)
>>>
>>> Ubuntu 12 (SSL):
>>>   - UserCgroupIsolatorTest/0.

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

[Michael Park]

Will do. Thanks!

On 23 March 2016 at 23:43, Benjamin Mahler <bmah...@apache.org> wrote:

> Also, I tagged https://issues.apache.org/jira/browse/MESOS-5021 with a
> fix version of 0.26.1. Can you include it?
>
> On Mon, Mar 21, 2016 at 1:59 PM, Benjamin Mahler <bmah...@apache.org>
> wrote:
>
>> Yes it has existed for a long time but has only been discovered recently.
>>
>> The way this was discovered was that garbage collection of user sandboxes
>> fails, which can result in the disk eventually filling up. This occurs when
>> there are special files in the sandbox (e.g. socket file).
>>
>> IMO it's a critical issue to fix.
>>
>> On Sat, Mar 19, 2016 at 6:39 AM, Michael Park <mp...@apache.org> wrote:
>>
>>> 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 <bmah...@apache.org> wrote:
>>>
>>>> These are be captured under:
>>>> https://issues.apache.org/jira/browse/MESOS-4979
>>>>
>>>> On Thu, Mar 17, 2016 at 5:04 PM, Benjamin Mahler <bmah...@apache.org>
>>>> wrote:
>>>>
>>>>> Thanks for the hard work! Do we need to backport the rmdir fixes on
>>>>> the outstanding release candidates?
>>>>>
>>>>> commit 5278e5cc50544ed7af28b15a1acd2b2e96a15a47
>>>>> Author: Jojy Varghese <j...@mesosphere.io>
>>>>> Date:   Tue Mar 15 17:12:01 2016 -0700
>>>>>
>>>>> Added support for FTS_SLNONE in rmdir.
>>>>>
>>>>> Review: https://reviews.apache.org/r/44874/
>>>>>
>>>>> commit fbe1f37f65fd9f1d4f2c30a3cfd7a50df92ccc2c
>>>>> Author: Alex Clemmer <clemmer.alexan...@gmail.com>
>>>>> Date:   Tue Mar 1 23:29:21 2016 -0800
>>>>>
>>>>> Stout:[1/2] Fixed error reporting bug in `os::rmdir`.
>>>>>
>>>>> Review: https://reviews.apache.org/r/43907/
>>>>>
>>>>> commit f8b7ac28b1a918864a06b3f99f45b0257c7b6f68
>>>>> Author: Jojy Varghese <j...@mesosphere.io>
>>>>> Date:   Tue Mar 1 14:32:13 2016 -0800
>>>>>
>>>>> Added FS_DEFAULT case in rmdir.
>>>>>
>>>>> We currently dont handle special files like device files in rmdir.
>>>>> This
>>>>> change adds FS_DEFAULT as one of the cases where we try to unlink a
>>>>> file. Reference: http://man7.org/linux/man-pages/man3/fts.3.html
>>>>>
>>>>> Review: https://reviews.apache.org/r/44230/
>>>>>
>>>>> On Wed, Mar 16, 2016 at 8:21 PM, Vinod Kone <vinodk...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> +1 (binding)
>>>>>>
>>>>>> Tested on ASF CI.
>>>>>>
>>>>>> On Sun, Mar 13, 2016 at 4:33 PM, Michael Park <mp...@apache.org>
>>>>>> wrote:
>>>>>>
>>>>>> > +1 (binding)
>>>>>> >
>>>>>> > Internal CI results with the corresponding JIRA tickets for the
>>>>>> failed
>>>>>> > tests:
>>>>>> >
>>>>>> > CentOS 6 (non-SSL):
>>>>>> >   - MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward
>>>>>> > (MESOS-3049 <https://issues.apache.org/jira/browse/MESOS-3049>)
>>>>>> >   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>>>>>> > (MESOS-4039 <https://issues.apache.org/jira/browse/MESOS-4039>)
>>>>>> >   - UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup
>>>>>> > (MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)
>>>>>> >   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>>>>>> > (MESOS-3215 <https://issues.apache.org/jira/browse/MESOS-3215>)
>>>>>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>>>>>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>>>>>> > (MESOS-4047 <https://issues.apache.org/jira/

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

[Michael Park]

+1 (binding)

Internal CI results with the corresponding JIRA tickets for the failed
tests:

CentOS 6 (non-SSL):
CentOS 6 (SSL):
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 )

CentOS 7 (non-SSL):
  - ProvisionerDockerRegistryPullerTest.ROOT_INTERNET_CURL_ShellCommand
(MESOS-4810)

CentOS 7 (SSL):
  - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers (Fixed in master)
(MESOS-4912 )
  - ProvisionerDockerRegistryPullerTest.ROOT_INTERNET_CURL_ShellCommand
(MESOS-4810 )

Debian 8 (non-SSL):
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 )

Debian 8 (SSL):
  - NsTest.ROOT_setns
(MESOS-3000 )
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 )

Ubuntu 12 (non-SSL):
  - HealthCheckTest.ROOT_DOCKER_DockerHealthStatusChange
Failed with MESOS-2017


Ubuntu 12 (SSL): Success!
Ubuntu 14 (non-SSL): Success!
Ubuntu 14 (SSL): Success!
Ubuntu 15 (non-SSL): Success!
Ubuntu 15 (SSL): Success!

On 11 March 2016 at 15:46, Vinod Kone  wrote:

> Hi all,
>
>
> Please vote on releasing the following candidate as Apache Mesos 0.28.0.
>
>
> 0.28.0 includes the following:
>
>
> 
>
> Release Notes - Mesos - Version 0.28.0
>
> 
>
> This release contains the following new features:
>
>   * [MESOS-4343] - A new cgroups isolator for enabling the net_cls
> subsystem in
>
> Linux. The cgroups/net_cls isolator allows operators to provide network
>
> performance isolation and network segmentation for containers within a
> Mesos
>
> cluster. To enable the cgroups/net_cls isolator, append
> `cgroups/net_cls` to
>
> the `--isolation` flag when starting the slave. Please refer to
>
> docs/mesos-containerizer.md for more details.
>
>
>   * [MESOS-4687] - The implementation of scalar resource values (e.g., "2.5
>
> CPUs") has changed. Mesos now reliably supports resources with up to
> three
>
> decimal digits of precision (e.g., "2.501 CPUs"); resources with more
> than
>
> three decimal digits of precision will be rounded. Internally, resource
> math
>
> is now done using a fixed-point format that supports three decimal
> digits of
>
> precision, and then converted to/from floating point for input and
> output,
>
> respectively. Frameworks that do their own resource math and manipulate
>
> fractional resources may observe differences in roundoff error and
> numerical
>
> precision.
>
>
>   * [MESOS-4479] - Reserved resources can now optionally include "labels".
>
> Labels are a set of key-value pairs that can be used to associate
> metadata
>
> with a reserved resource. For example, frameworks can use this feature
> to
>
> distinguish between two reservations for the same role at the same
> agent
>
> that are intended for different purposes.
>
>
>   * [MESOS-2840] - **Experimental** support for container images in Mesos
>
> containerizer (a.k.a. Unified Containerizer). This allows frameworks to
>
> launch Docker/Appc containers using Mesos containerizer without relying
> on
>
> docker daemon (engine) or rkt. The isolation of the containers is done
> using
>
> isolators. Please refer to docs/container-image.md for currently
> supported
>
> features and limitations.
>
>
>   * [MESOS-4793] - **Experimental** support for v1 Executor HTTP API. This
>
> allows executors to send HTTP requests to the /api/v1/executor agent
>
> endpoint without the need for an executor driver. Please refer to
>
> docs/executor-http-api.md for more details.
>
>
>   * [MESOS-4370] Added support for service discovery of Docker containers
> that
>
> use Docker Remote API v1.21.
>
>
> Additional API Changes:
>
>   * [MESOS-4066] - Agent should not return partial state when a request is
> made to /state endpoint during recovery.
>
>   * [MESOS-4547] - Introduce TASK_KILLING state.
>
>   * [MESOS-4712] - Remove 'force' field from the Subscribe Call in v1
> Scheduler API.
>
>   * [MESOS-4591] - Change the object of ReserveResources and CreateVolume
> ACLs to `roles`.
>
>   * [MESOS-3583] - Add stream IDs for HTTP schedulers.
>
>   * [MESOS-4427] - Ensure ip_address in state.json (from NetworkInfo) is
> valid
>
>
> 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=0.28.0-rc2
>
>
> 
>
>
> The candidate for Mesos 0.28.0 release is available at:
>
> 

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

[Michael Park]

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/msg06204.html
<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 19:55, Michael Park <mp...@apache.org> wrote:

> +1 (binding)
>
> Internal CI results with the corresponding JIRA tickets for the failed
> tests:
>
> CentOS 6 (non-SSL):
> CentOS 6 (SSL):
>   - Failed with MESOS-2017
> <https://issues.apache.org/jira/browse/MESOS-2017>
>
> CentOS 7 (non-SSL):
>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> (MESOS-4039 <https://issues.apache.org/jira/browse/MESOS-4039>)
>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
> (MESOS-3215 <https://issues.apache.org/jira/browse/MESOS-3215>)
>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>   - LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
> (MESOS-3296 <https://issues.apache.org/jira/browse/MESOS-3296>)
>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
> (MESOS-3410 <https://issues.apache.org/jira/browse/MESOS-3410>)
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
> MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)
>
> CentOS 7 (SSL):
>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> (MESOS-4039 <https://issues.apache.org/jira/browse/MESOS-4039>)
>   - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
> (MESOS-2672 <https://issues.apache.org/jira/browse/MESOS-2672>)
>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
> (MESOS-3215 <https://issues.apache.org/jira/browse/MESOS-3215>)
>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>   - LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
> (MESOS-3296 <https://issues.apache.org/jira/browse/MESOS-3296>)
>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
> (MESOS-3410 <https://issues.apache.org/jira/browse/MESOS-3410>)
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
> MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)
>
> Debian 8 (non-SSL):
> Debian 8 (SSL):
>   - Failed with MESOS-3964
> <https://issues.apache.org/jira/browse/MESOS-3964>
>
> Ubuntu 12 (non-SSL):
>   - DockerContainerizerTest.ROOT_DOCKER_Logs
> (MESOS-4676 <https://issues.apache.org/jira/browse/MESOS-4676>)
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)
>
> Ubuntu 12 (SSL):
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)
>   - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
> (MESOS-2672 <https://issues.apache.org/jira/browse/MESOS-2672>)
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
> MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)
>
> Ubuntu 14 (non-SSL):
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)
>
> Ubuntu 14 (SSL):
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 <https://issues.apache.org/

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

[Michael Park]

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, Michael Park <mp...@apache.org> wrote:

> +1 (binding)
>
> Internal CI results with the corresponding JIRA tickets for the failed
> tests:
>
> CentOS 6 (non-SSL):
> CentOS 6 (SSL):
>   - Failed with MESOS-2017
> <https://issues.apache.org/jira/browse/MESOS-2017>
>
> CentOS 7 (non-SSL):
> CentOS 7 (SSL):
>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> (MESOS-4039 <https://issues.apache.org/jira/browse/MESOS-4039>)
>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
> (MESOS-3215 <https://issues.apache.org/jira/browse/MESOS-3215>)
>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
> (MESOS-3296 <https://issues.apache.org/jira/browse/MESOS-3296>)
>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
> (MESOS-3410 <https://issues.apache.org/jira/browse/MESOS-3410>)
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
> MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)
>   - PerfTest.ROOT_SamplePid
> (MESOS-3079 <https://issues.apache.org/jira/browse/MESOS-3079>)
>
> Debian 8 (non-SSL):
> Debian 8 (SSL):
>   - Failed with MESOS-3964
> <https://issues.apache.org/jira/browse/MESOS-3964>
>
> Ubuntu 12 (non-SSL):
> Ubuntu 12 (SSL):
> Ubuntu 14 (non-SSL):
> Ubuntu 14 (SSL):
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)
>
> Ubuntu 15 (non-SSL):
>   - DockerContainerizerTest.ROOT_DOCKER_Logs
> (MESOS-4676 <https://issues.apache.org/jira/browse/MESOS-4676>)
>   - LimitedCpuIsolatorTest.ROOT_CGROUPS_Pids_and_Tids
> (MESOS-4677 <https://issues.apache.org/jira/browse/MESOS-4677>)
>
> Ubuntu 15 (SSL): Success!
>
> On 13 March 2016 at 18:42, Michael Park <mp...@apache.org> wrote:
>
>> While the vote for this release was open until Fri Mar 11 23:59:59 EST
>> 2016,
>> I'm going to give it another 3 days since there has not been any -1 votes.
>>
>> The vote is extended until Wed Mar 16 23:59:59 EST 2016.
>>
>> On 10 March 2016 at 12:49, Greg Mann <g...@mesosphere.io> wrote:
>>
>>> +1 (non-binding)
>>>
>>> Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL
>>> enabled. All tests pass.
>>>
>>> I was also able to successfully test a simple upgrade scenario from
>>> 0.23.1 to 0.24.2-rc2 using the script found here:
>>> https://reviews.apache.org/r/44229/
>>>
>>> Cheers,
>>> Greg
>>>
>>>
>>> On Tue, Mar 8, 2016 at 6:50 PM, Michael Park <mp...@apache.org> wrote:
>>>
>>>> The link to the commit above points to the one on the master branch.
>>>> The following is the one on the `0.24.2-rc2` branch: Fixed compiler
>>>> warning
>>>> in values tests.
>>>> <
>>>> https://github.com/apache/mesos/commit/afb8a0cffaf8bc235ce45087c80bafe87488dcd0
>>>> >
>>>>
>>>> On 8 March 2016 at 21:21, Michael Park <mp...@apache.org> wrote:
>>>>
>>>> > Hi all,
>>>> >
>>>> > Please vote on releasing the following candidate as Apache Mesos
>>>> 0.24.2.
>>>> >
>>>> >
>>>> > 0.24.2 includes the following:
>>>> >
>>>> >
>>>> 
>>>> >
>>>> > The only diff with RC1 is the following: Fixed compiler warning in
>>>> values
>>>> > tests.
>>>> > <
>>>> https://github.com/apache/mesos/commit/bfeb070a2aef52f445eb057076d344fd184eb461
>>>> >
>>>>
>>>> > As I described in the RC1 [VOTE] thread, even though this is a trivial
>>>> > compile fix,
>>>> > I decid

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

[Michael Park]

Hi Evan,

As I mentioned in the 0.25.1 rc2 thread,

I will be cutting an rc3 for 0.24.2 and 0.25.1 to include those patches.

Thanks again!

MPark

On 18 March 2016 at 17:09, Benjamin Mahler  wrote:

> +michael who is managing the release, he'll get back to you shortly,
> apologies for the delay!
>
> On Fri, Mar 11, 2016 at 11:35 AM, Evan Krall  wrote:
>
>> I humbly request that the fixes for these issues are also included in
>> 0.24.2:
>>
>> https://issues.apache.org/jira/browse/MESOS-3738
>> https://issues.apache.org/jira/browse/MESOS-3560
>>
>> Both of these issues caused trouble for us trying to keep up with Mesos
>> upgrades.
>>
>
>

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

[Michael Park]

Hi Evan,

Thank you for letting us know of the issues and your explanation!

I will cut an RC3 for 0.24.2 and 0.25.1 to include those patches.

MPark

On 14 March 2016 at 20:25, Evan Krall <kr...@yelp.com> wrote:

> On Sun, Mar 13, 2016 at 3:46 PM, Michael Park <mp...@apache.org> wrote:
>
>> Hi Evan,
>>
>> If we wanted to backport those patches as well, we should cut a 0.25.2.
>> I would first like to understand what kind of issues you're running into.
>> Do you mind elaborating a little?
>>
>
>
> For MESOS-3738, we ran into the issue pretty much directly. We run Mesos
> with the Docker executor, and mesos healthchecks stopped reporting
> correctly. Our automation (built on Marathon) waits for healthcheck results
> to be available before considering a task "healthy" and killing old tasks,
> so this bug manifested as deploys getting stuck and never killing old tasks.
>
> There is a patch available in the ticket, and we've built our own copies
> of Mesos, including that patch. However, it took us some time to figure out
> that this was the issue, and we had to set up an internal build pipeline
> for Mesos that includes that patch.
>
>
> For MESOS-3560, we attempted to upgrade a cluster from 0.23.1 to 0.24.1
> and saw that our Mesos slaves were unable to connect to the master due to
> authentication issues. We eventually figured out that we were hitting the
> bug in MESOS-3560, and switched to the older newline-delimited credential
> files.
>
>
> Because the Mesos upgrade process dictates that you should never skip a
> minor version, anybody using Docker, command healthchecks, and
> authentication on <=0.23 will hit both of these bugs and need to patch and
> work around them if they want to upgrade to anything above 0.24.
>
> While we've worked around both of these issues, it's really frustrating
> that these issues have both been fixed for several months, but neither fix
> was released for 0.24 or 0.25. I'm pushing for these patches to be released
> (along with any other unreleased bugfixes that might be scattered around
> JIRA) so that anybody else doing this upgrade doesn't need to feel the same
> pain that we did.
>
>
>> Thanks,
>>
>> MPark
>>
>
>

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

[Michael Park]

The Mesosphere deb/rpm packages are available here:
http://open.mesosphere.com/downloads/mesos/

On 7 March 2016 at 23:29, Michael Park <mp...@apache.org> wrote:

> Hi all,
>
> The vote for Mesos 0.27.2 (rc1) has passed with the
> following votes.
>
> +1 (Binding)
> --
> Kapil Arya
> Vinod Kone
> Joris Van Remoortere
>
> +1 (Non-binding)
> --
> Greg Mann
> Michael Browning
>
> There was one -1 non-binding vote from Kevin Klues. I followed up with
> Kevin on
> the [VOTE] thread, and confirmed that it was ok for us to proceed, since
> it's a
> flaky test fix that does not affect the resulting binary.
>
> 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 available at:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.27.2
>
> The mesos-0.27.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,
>
> MPark, Joris, Kapil
>

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

[Michael Park]

+1 (binding)

Internal CI results with the corresponding JIRA tickets for the failed
tests:

CentOS 6 (non-SSL):
CentOS 6 (SSL):
  - Failed with MESOS-2017
<https://issues.apache.org/jira/browse/MESOS-2017>

CentOS 7 (non-SSL):
CentOS 7 (SSL):
  - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
(MESOS-4039 <https://issues.apache.org/jira/browse/MESOS-4039>)
  - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
(MESOS-3215 <https://issues.apache.org/jira/browse/MESOS-3215>)
  - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
  - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
  - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
  - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
  - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
(MESOS-3296 <https://issues.apache.org/jira/browse/MESOS-3296>)
  - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
(MESOS-3410 <https://issues.apache.org/jira/browse/MESOS-3410>)
  - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)
  - PerfTest.ROOT_SamplePid
(MESOS-3079 <https://issues.apache.org/jira/browse/MESOS-3079>)

Debian 8 (non-SSL):
Debian 8 (SSL):
  - Failed with MESOS-3964
<https://issues.apache.org/jira/browse/MESOS-3964>

Ubuntu 12 (non-SSL):
Ubuntu 12 (SSL):
Ubuntu 14 (non-SSL):
Ubuntu 14 (SSL):
  - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
  - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
(MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)

Ubuntu 15 (non-SSL):
  - DockerContainerizerTest.ROOT_DOCKER_Logs
(MESOS-4676 <https://issues.apache.org/jira/browse/MESOS-4676>)
  - LimitedCpuIsolatorTest.ROOT_CGROUPS_Pids_and_Tids
(MESOS-4677 <https://issues.apache.org/jira/browse/MESOS-4677>)

Ubuntu 15 (SSL): Success!

On 13 March 2016 at 18:42, Michael Park <mp...@apache.org> wrote:

> While the vote for this release was open until Fri Mar 11 23:59:59 EST
> 2016,
> I'm going to give it another 3 days since there has not been any -1 votes.
>
> The vote is extended until Wed Mar 16 23:59:59 EST 2016.
>
> On 10 March 2016 at 12:49, Greg Mann <g...@mesosphere.io> wrote:
>
>> +1 (non-binding)
>>
>> Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL
>> enabled. All tests pass.
>>
>> I was also able to successfully test a simple upgrade scenario from
>> 0.23.1 to 0.24.2-rc2 using the script found here:
>> https://reviews.apache.org/r/44229/
>>
>> Cheers,
>> Greg
>>
>>
>> On Tue, Mar 8, 2016 at 6:50 PM, Michael Park <mp...@apache.org> wrote:
>>
>>> The link to the commit above points to the one on the master branch.
>>> The following is the one on the `0.24.2-rc2` branch: Fixed compiler
>>> warning
>>> in values tests.
>>> <
>>> https://github.com/apache/mesos/commit/afb8a0cffaf8bc235ce45087c80bafe87488dcd0
>>> >
>>>
>>> On 8 March 2016 at 21:21, Michael Park <mp...@apache.org> wrote:
>>>
>>> > Hi all,
>>> >
>>> > Please vote on releasing the following candidate as Apache Mesos
>>> 0.24.2.
>>> >
>>> >
>>> > 0.24.2 includes the following:
>>> >
>>> >
>>> 
>>> >
>>> > The only diff with RC1 is the following: Fixed compiler warning in
>>> values
>>> > tests.
>>> > <
>>> https://github.com/apache/mesos/commit/bfeb070a2aef52f445eb057076d344fd184eb461
>>> >
>>>
>>> > As I described in the RC1 [VOTE] thread, even though this is a trivial
>>> > compile fix,
>>> > I decided to cut an RC2 in order to avoid breaking those who compile
>>> Mesos
>>> > from source.
>>> >
>>> > * Improvements
>>> > - Allocator filter performance
>>> > - Port Ranges performance
>>> > - UUID performance
>>> > - `/state` endpoint performance
>>> >   - GLOG performance
>>> >   - Configurable task/framework history
>>> >   - Offer filter timeout fix for backlogged allocator
>>> >
>>> > * Bugs
>>> >   - SSL
>>> >   - Libevent
>>> >   - Fixed point resources math
>>> >   - HDFS
>>> >   - Agent upgrade compatibility
>>> >   - Health checks
>>> >
>>> > The CHANGELOG

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

[Michael Park]

+1 (binding)

Internal CI results with the corresponding JIRA tickets for the failed
tests:

CentOS 6 (non-SSL):
CentOS 6 (SSL):
  - Failed with MESOS-2017
<https://issues.apache.org/jira/browse/MESOS-2017>

CentOS 7 (non-SSL):
  - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
(MESOS-4039 <https://issues.apache.org/jira/browse/MESOS-4039>)
  - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
(MESOS-3215 <https://issues.apache.org/jira/browse/MESOS-3215>)
  - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
  - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
  - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
  - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
  - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
  - LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem
  - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
  - LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
(MESOS-3296 <https://issues.apache.org/jira/browse/MESOS-3296>)
  - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
(MESOS-3410 <https://issues.apache.org/jira/browse/MESOS-3410>)
  - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)

CentOS 7 (SSL):
  - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
(MESOS-4039 <https://issues.apache.org/jira/browse/MESOS-4039>)
  - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
(MESOS-2672 <https://issues.apache.org/jira/browse/MESOS-2672>)
  - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
(MESOS-3215 <https://issues.apache.org/jira/browse/MESOS-3215>)
  - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
  - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
  - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
  - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
  - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
  - LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem
  - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
  - LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
(MESOS-3296 <https://issues.apache.org/jira/browse/MESOS-3296>)
  - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
(MESOS-3410 <https://issues.apache.org/jira/browse/MESOS-3410>)
  - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)

Debian 8 (non-SSL):
Debian 8 (SSL):
  - Failed with MESOS-3964
<https://issues.apache.org/jira/browse/MESOS-3964>

Ubuntu 12 (non-SSL):
  - DockerContainerizerTest.ROOT_DOCKER_Logs
(MESOS-4676 <https://issues.apache.org/jira/browse/MESOS-4676>)
  - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
  - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
(MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)

Ubuntu 12 (SSL):
  - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
  - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
(MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)
  - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
(MESOS-2672 <https://issues.apache.org/jira/browse/MESOS-2672>)
  - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)

Ubuntu 14 (non-SSL):
  - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
  - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
(MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)

Ubuntu 14 (SSL):
  - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
  - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
(MESOS-4035 <https://issues.apache.org/jira/browse/MESOS-4035>)
  - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
(MESOS-2672 <https://issues.apache.org/jira/browse/MESOS-2672>)
  - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)

Ubuntu 15 (non-SSL): Success!
Ubuntu 15 (SSL):
  - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
(MESOS-2672 <https://issues.apache.org/jira/browse/MESOS-2672>)
  - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 <https://issues.apache.org/jira/browse/MESOS-4047>,
MESOS-4053 <https://issues.apache.org/jira/browse/MESOS-4053>)

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

[Michael Park]

Hi Evan,

If we wanted to backport those patches as well, we should cut a 0.25.2.
I would first like to understand what kind of issues you're running into.
Do you mind elaborating a little?

Thanks,

MPark

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

[Michael Park]

While the vote for this release was open until Fri Mar 11 23:59:59 EST 2016,
I'm going to give it another 3 days since there has not been any -1 votes.

The vote is extended until Wed Mar 16 23:59:59 EST 2016.

On 10 March 2016 at 12:40, Michael Park <mp...@apache.org> wrote:

> Thanks Greg!
>
> On 10 March 2016 at 12:34, Greg Mann <g...@mesosphere.io> wrote:
>
>> +1 (non-binding)
>>
>> Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL
>> enabled.
>>
>> The following tests failed during the first test run:
>> ContainerizerTest.ROOT_CGROUPS_BalloonFramework
>> MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>> MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>>
>> but these all passed when re-run in isolation using the gtest filter.
>>
>> I was also able to successfully test a simple upgrade scenario from
>> 0.24.2-rc2 to 0.25.1-rc2 using the script found here:
>> https://reviews.apache.org/r/44229/
>>
>> Cheers,
>> Greg
>>
>>
>> On Tue, Mar 8, 2016 at 7:29 PM, Michael Park <mp...@apache.org> wrote:
>>
>> > Hi all,
>> >
>> > Please vote on releasing the following candidate as Apache Mesos 0.25.1.
>> >
>> >
>> > 0.25.1 includes the following:
>> >
>> >
>> 
>> >
>> > The only diff with RC1 is the following: Fix CGROUPS_ROOT_* tests on
>> > systemd platforms.
>> > <
>> >
>> https://github.com/apache/mesos/commit/253223b3288df85cb3b12fe3af5c7b0a7a262f1a
>> > >
>> > This patch is necessary in order to make the `systemd` integration work
>> > correctly.
>> > It was part of MESOS-4636
>> > <https://issues.apache.org/jira/browse/MESOS-4636> but
>> > was accidentally left out during the cherry-pick process.
>> >
>> > * Improvements
>> >   - `/state` endpoint performance
>> >   - `systemd` integration
>> >   - GLOG performance
>> >   - Configurable task/framework history
>> >   - Offer filter timeout fix for backlogged allocator
>> >
>> > * Bugs
>> >   - SSL
>> >   - Libevent
>> >   - Fixed point resources math
>> >   - HDFS
>> >   - Agent upgrade compatibility
>> >   - Health checks
>> >
>> > 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=0.25.1-rc2
>> >
>> >
>> 
>> >
>> > The candidate for Mesos 0.25.1 release is available at:
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc2/mesos-0.25.1.tar.gz
>> >
>> > The tag to be voted on is 0.25.1-rc2:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.25.1-rc2
>> >
>> > The MD5 checksum of the tarball can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc2/mesos-0.25.1.tar.gz.md5
>> >
>> > The signature of the tarball can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc2/mesos-0.25.1.tar.gz.asc
>> >
>> > The PGP key used to sign the release is here:
>> > https://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-1116
>> >
>> > Please vote on releasing this package as Apache Mesos 0.25.1!
>> >
>> > The vote is open until Fri Mar 11 23:59:59 EST 2016 and passes if a
>> > majority of at least 3 +1 PMC votes are cast.
>> >
>> > [ ] +1 Release this package as Apache Mesos 0.25.1
>> > [ ] -1 Do not release this package because ...
>> >
>> > Thanks,
>> >
>> > MPark
>> >
>>
>
>

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

[Michael Park]

While the vote for this release was open until Fri Mar 11 23:59:59 EST 2016,
I'm going to give it another 3 days since there has not been any -1 votes.

The vote is extended until Wed Mar 16 23:59:59 EST 2016.

On 10 March 2016 at 12:49, Greg Mann <g...@mesosphere.io> wrote:

> +1 (non-binding)
>
> Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL
> enabled. All tests pass.
>
> I was also able to successfully test a simple upgrade scenario from 0.23.1
> to 0.24.2-rc2 using the script found here:
> https://reviews.apache.org/r/44229/
>
> Cheers,
> Greg
>
>
> On Tue, Mar 8, 2016 at 6:50 PM, Michael Park <mp...@apache.org> wrote:
>
>> The link to the commit above points to the one on the master branch.
>> The following is the one on the `0.24.2-rc2` branch: Fixed compiler
>> warning
>> in values tests.
>> <
>> https://github.com/apache/mesos/commit/afb8a0cffaf8bc235ce45087c80bafe87488dcd0
>> >
>>
>> On 8 March 2016 at 21:21, Michael Park <mp...@apache.org> wrote:
>>
>> > Hi all,
>> >
>> > Please vote on releasing the following candidate as Apache Mesos 0.24.2.
>> >
>> >
>> > 0.24.2 includes the following:
>> >
>> >
>> 
>> >
>> > The only diff with RC1 is the following: Fixed compiler warning in
>> values
>> > tests.
>> > <
>> https://github.com/apache/mesos/commit/bfeb070a2aef52f445eb057076d344fd184eb461
>> >
>>
>> > As I described in the RC1 [VOTE] thread, even though this is a trivial
>> > compile fix,
>> > I decided to cut an RC2 in order to avoid breaking those who compile
>> Mesos
>> > from source.
>> >
>> > * Improvements
>> > - Allocator filter performance
>> > - Port Ranges performance
>> > - UUID performance
>> > - `/state` endpoint performance
>> >   - GLOG performance
>> >   - Configurable task/framework history
>> >   - Offer filter timeout fix for backlogged allocator
>> >
>> > * Bugs
>> >   - SSL
>> >   - Libevent
>> >   - Fixed point resources math
>> >   - HDFS
>> >   - Agent upgrade compatibility
>> >   - Health checks
>> >
>> > 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=0.24.2-rc2
>> >
>> >
>> 
>> >
>> > The candidate for Mesos 0.24.2 release is available at:
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc2/mesos-0.24.2.tar.gz
>> >
>> > The tag to be voted on is 0.24.2-rc2:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.2-rc2
>> >
>> > The MD5 checksum of the tarball can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc2/mesos-0.24.2.tar.gz.md5
>> >
>> > The signature of the tarball can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc2/mesos-0.24.2.tar.gz.asc
>> >
>> > The PGP key used to sign the release is here:
>> > https://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-1114
>> >
>> > Please vote on releasing this package as Apache Mesos 0.24.2!
>> >
>> > The vote is open until Fri Mar 11 23:59:59 EST 2016 and passes if a
>> > majority of at least 3 +1 PMC votes are cast.
>> >
>> > [ ] +1 Release this package as Apache Mesos 0.24.2
>> > [ ] -1 Do not release this package because ...
>> >
>> > Thanks,
>> >
>> > MPark
>> >
>>
>
>

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

[Michael Park]

Thanks Greg!

On 10 March 2016 at 12:32, Greg Mann <g...@mesosphere.io> wrote:

> +1 (non-binding)
>
> Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL
> enabled. All tests pass.
>
> I was also able to successfully test a simple upgrade scenario from
> 0.25.1-rc2 to 0.26.1-rc2 using the script found here:
> https://reviews.apache.org/r/44229/
>
> Cheers,
> Greg
>
>
> On Tue, Mar 8, 2016 at 7:48 PM, Michael Park <mp...@apache.org> wrote:
>
>> Hi all,
>>
>> Please vote on releasing the following candidate as Apache Mesos 0.26.1.
>>
>>
>> 0.26.1 includes the following:
>>
>> 
>>
>> The only diff with RC1 is the following: Fix CGROUPS_ROOT_* tests on
>> systemd platforms.
>> <https://github.com/apache/mesos/commit/a896cda4aa8bb9c9bbfba20dda4b68df8dbdf569>
>> This patch is necessary in order to make the `systemd` integration work
>> correctly.
>> It was part of MESOS-4636
>> <https://issues.apache.org/jira/browse/MESOS-4636> but was accidentally
>> left out during the cherry-pick process.
>>
>> * Improvements
>>   - `/state` endpoint performance
>>   - `systemd` integration
>>   - GLOG performance
>>   - Configurable task/framework history
>>   - Offer filter timeout fix for backlogged allocator
>>
>> * Bugs
>>   - SSL
>>   - Libevent
>>   - Fixed point resources math
>>   - HDFS
>>   - Agent upgrade compatibility
>>
>> 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=0.26.1-rc2
>>
>> 
>>
>> The candidate for Mesos 0.26.1 release is available at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc2/mesos-0.26.1.tar.gz
>>
>> The tag to be voted on is 0.26.1-rc2:
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.26.1-rc2
>>
>> The MD5 checksum of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc2/mesos-0.26.1.tar.gz.md5
>>
>> The signature of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc2/mesos-0.26.1.tar.gz.asc
>>
>> The PGP key used to sign the release is here:
>> https://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-1118
>>
>> Please vote on releasing this package as Apache Mesos 0.26.1!
>>
>> The vote is open until Fri Mar 11 23:59:59 EST 2016 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Mesos 0.26.1
>> [ ] -1 Do not release this package because ...
>>
>> Thanks,
>>
>> MPark
>>
>
>

[VOTE] Release Apache Mesos 0.26.1 (rc2)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.26.1.


0.26.1 includes the following:


The only diff with RC1 is the following: Fix CGROUPS_ROOT_* tests on
systemd platforms.

This patch is necessary in order to make the `systemd` integration work
correctly.
It was part of MESOS-4636
 but
was accidentally left out during the cherry-pick process.

* Improvements
  - `/state` endpoint performance
  - `systemd` integration
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator

* Bugs
  - SSL
  - Libevent
  - Fixed point resources math
  - HDFS
  - Agent upgrade compatibility

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=0.26.1-rc2


The candidate for Mesos 0.26.1 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc2/mesos-0.26.1.tar.gz

The tag to be voted on is 0.26.1-rc2:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.26.1-rc2

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc2/mesos-0.26.1.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc2/mesos-0.26.1.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1118

Please vote on releasing this package as Apache Mesos 0.26.1!

The vote is open until Fri Mar 11 23:59:59 EST 2016 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.26.1
[ ] -1 Do not release this package because ...

Thanks,

MPark

[VOTE] Release Apache Mesos 0.25.1 (rc2)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.25.1.


0.25.1 includes the following:


The only diff with RC1 is the following: Fix CGROUPS_ROOT_* tests on
systemd platforms.

This patch is necessary in order to make the `systemd` integration work
correctly.
It was part of MESOS-4636
 but
was accidentally left out during the cherry-pick process.

* Improvements
  - `/state` endpoint performance
  - `systemd` integration
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator

* Bugs
  - SSL
  - Libevent
  - Fixed point resources math
  - HDFS
  - Agent upgrade compatibility
  - Health checks

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=0.25.1-rc2


The candidate for Mesos 0.25.1 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc2/mesos-0.25.1.tar.gz

The tag to be voted on is 0.25.1-rc2:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.25.1-rc2

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc2/mesos-0.25.1.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc2/mesos-0.25.1.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1116

Please vote on releasing this package as Apache Mesos 0.25.1!

The vote is open until Fri Mar 11 23:59:59 EST 2016 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.25.1
[ ] -1 Do not release this package because ...

Thanks,

MPark

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

[Michael Park]

The link to the commit above points to the one on the master branch.
The following is the one on the `0.24.2-rc2` branch: Fixed compiler warning
in values tests.
<https://github.com/apache/mesos/commit/afb8a0cffaf8bc235ce45087c80bafe87488dcd0>

On 8 March 2016 at 21:21, Michael Park <mp...@apache.org> wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 0.24.2.
>
>
> 0.24.2 includes the following:
>
> 
>
> The only diff with RC1 is the following: Fixed compiler warning in values
> tests.
> <https://github.com/apache/mesos/commit/bfeb070a2aef52f445eb057076d344fd184eb461>
> As I described in the RC1 [VOTE] thread, even though this is a trivial
> compile fix,
> I decided to cut an RC2 in order to avoid breaking those who compile Mesos
> from source.
>
> * Improvements
> - Allocator filter performance
> - Port Ranges performance
> - UUID performance
> - `/state` endpoint performance
>   - GLOG performance
>   - Configurable task/framework history
>   - Offer filter timeout fix for backlogged allocator
>
> * Bugs
>   - SSL
>   - Libevent
>   - Fixed point resources math
>   - HDFS
>   - Agent upgrade compatibility
>   - Health checks
>
> 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=0.24.2-rc2
>
> 
>
> The candidate for Mesos 0.24.2 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc2/mesos-0.24.2.tar.gz
>
> The tag to be voted on is 0.24.2-rc2:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.2-rc2
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc2/mesos-0.24.2.tar.gz.md5
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc2/mesos-0.24.2.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://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-1114
>
> Please vote on releasing this package as Apache Mesos 0.24.2!
>
> The vote is open until Fri Mar 11 23:59:59 EST 2016 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 0.24.2
> [ ] -1 Do not release this package because ...
>
> Thanks,
>
> MPark
>

[VOTE] Release Apache Mesos 0.24.2 (rc2)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.24.2.


0.24.2 includes the following:


The only diff with RC1 is the following: Fixed compiler warning in values
tests.

As I described in the RC1 [VOTE] thread, even though this is a trivial
compile fix,
I decided to cut an RC2 in order to avoid breaking those who compile Mesos
from source.

* Improvements
- Allocator filter performance
- Port Ranges performance
- UUID performance
- `/state` endpoint performance
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator

* Bugs
  - SSL
  - Libevent
  - Fixed point resources math
  - HDFS
  - Agent upgrade compatibility
  - Health checks

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=0.24.2-rc2


The candidate for Mesos 0.24.2 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc2/mesos-0.24.2.tar.gz

The tag to be voted on is 0.24.2-rc2:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.2-rc2

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc2/mesos-0.24.2.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc2/mesos-0.24.2.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1114

Please vote on releasing this package as Apache Mesos 0.24.2!

The vote is open until Fri Mar 11 23:59:59 EST 2016 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.24.2
[ ] -1 Do not release this package because ...

Thanks,

MPark

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

[Michael Park]

-1 (binding)

TL;DR: Same issue as 0.26.1-rc1.

Observed the following error on CentOS 7 and Debian 8, which requires
https://reviews.apache.org/r/43432 to be pulled in.

[01:16:29][Step 11/11] I0308 01:16:29.082664 21059 systemd.cpp:225] systemd
version `219` detected
[01:16:29][Step 11/11] F0308 01:16:29.082700 21059 systemd.cpp:61] Check
failed: 'systemd_flags' Must be non NULL

While this is only a test failure, I would rather not give off the
impression that `systemd`
integrations don't work properly, since it's an explicitly back-ported
feature.

On 4 March 2016 at 15:49, Joris Van Remoortere <jo...@apache.org> wrote:

> +1 (binding)
> Greg's upgrade scripts & CI results
>
> On Tue, Mar 1, 2016 at 4:37 PM, Greg Mann <g...@mesosphere.io> wrote:
>
>> I was also able to successfully test a simple upgrade scenario between
>> 0.24.2-rc1 and 0.25.1-rc1 using Niklas's upgrade testing script, which
>> I've
>> modified slightly and reposted here: https://reviews.apache.org/r/44229/
>>
>> On Tue, Mar 1, 2016 at 9:29 AM, Greg Mann <g...@mesosphere.io> wrote:
>>
>> > +1 (non-binding)
>> >
>> > `sudo make check` on Ubuntu 14.04 using gcc, with libevent and SSL
>> enabled.
>> >
>> > All tests pass except:
>> >
>> > PerfEventIsolatorTest.ROOT_CGROUPS_Sample, which is covered here:
>> > https://issues.apache.org/jira/browse/MESOS-4655
>> >
>> > CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf,
>> > MemoryPressureMesosTest.CGROUPS_ROOT_Statistics, and
>> > MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery, due to the issue
>> here:
>> > https://issues.apache.org/jira/browse/MESOS-3215
>> >
>> > Cheers,
>> > Greg
>> >
>> >
>> > On Mon, Feb 29, 2016 at 11:21 AM, Kapil Arya <ka...@mesosphere.io>
>> wrote:
>> >
>> >> +1 (binding)
>> >>
>> >> Successful CI builds for the following distros:
>> >>
>> >> amd64/centos/6
>> >> amd64/centos/7
>> >> amd64/debian/jessie
>> >> amd64/ubuntu/precise
>> >> amd64/ubuntu/trusty
>> >> amd64/ubuntu/vivid
>> >>
>> >> Kapil
>> >>
>> >> On Sat, Feb 27, 2016 at 12:53 AM, Michael Park <mp...@apache.org>
>> wrote:
>> >>
>> >> > Hi all,
>> >> >
>> >> > Please vote on releasing the following candidate as Apache Mesos
>> 0.25.1.
>> >> >
>> >> >
>> >> > 0.25.1 includes the following:
>> >> >
>> >> >
>> >>
>> 
>> >> >
>> >> >- Improvements
>> >> >   - `/state` endpoint performance
>> >> >   - systemd integration
>> >> >   - GLOG performance
>> >> >   - Configurable task/framework history
>> >> >   - Offer filter timeout fix for backlogged allocator
>> >> >
>> >> >
>> >> >- Bugs
>> >> >- SSL
>> >> >   - Libevent
>> >> >   - Fixed point resources math
>> >> >- HDFS
>> >> >   - Agent upgrade compatibility
>> >> >   - Health checks
>> >> >
>> >> > 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=0.25.1-rc1
>> >> >
>> >> >
>> >>
>> 
>> >> >
>> >> > The candidate for Mesos 0.25.1 release is available at:
>> >> >
>> >>
>> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz
>> >> >
>> >> > The tag to be voted on is 0.25.1-rc1:
>> >> >
>> >>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.25.1-rc1
>> >> >
>> >> > The MD5 checksum of the tarball can be found at:
>> >> >
>> >> >
>> >>
>> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz.md5
>> >> >
>> >> > The signature of the tarball can be found at:
>> >> >
>> >> >
>> >>
>> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz.asc
>> >> >
>> >> > The PGP key used to sign the release is here:
>> >> > https://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-1108
>> >> >
>> >> > Please vote on releasing this package as Apache Mesos 0.25.1!
>> >> >
>> >> > The vote is open until Wed Mar 2 23:59:59 PST 2016 and passes if a
>> >> majority
>> >> > of at least 3 +1 PMC votes are cast.
>> >> >
>> >> > [ ] +1 Release this package as Apache Mesos 0.25.1
>> >> > [ ] -1 Do not release this package because ...
>> >> >
>> >> > Thanks,
>> >> >
>> >> > Joris, Kapil, MPark
>> >> >
>> >>
>> >
>> >
>>
>
>

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

[Michael Park]

-1 (binding)

On `CentOS 6` and `Debian 8`, with `g++-4.9.2`, I'm seeing compiler errors
that arise from `-Werror=sign-compare`.
A user running into this issue while trying to compile from source would be
bad. I'll cut another RC for this release.

On 4 March 2016 at 15:49, Joris Van Remoortere <jo...@apache.org> wrote:

> +1 (binding)
>
> On Mon, Feb 29, 2016 at 3:24 PM, Greg Mann <g...@mesosphere.io> wrote:
>
> > +1 (non-binding)
> >
> > `sudo make check` on Ubuntu 14.04, using gcc with libevent and SSL
> enabled.
> > All tests pass except MemoryPressureMesosTest.CGROUPS_ROOT_Statistics,
> > which is a known failure in 0.24.
> >
> > Cheers,
> > Greg
> >
> >
> > On Mon, Feb 29, 2016 at 11:20 AM, Kapil Arya <ka...@mesosphere.io>
> wrote:
> >
> > > +1 (binding)
> > >
> > > Successful CI builds for the following distros:
> > >
> > > amd64/centos/6
> > > amd64/centos/7
> > > amd64/debian/jessie
> > > amd64/ubuntu/precise
> > > amd64/ubuntu/trusty
> > > amd64/ubuntu/vivid
> > >
> > > Kapil
> > >
> > > On Sat, Feb 27, 2016 at 1:12 AM, Michael Park <mp...@apache.org>
> wrote:
> > >
> > >> Hi all,
> > >>
> > >> Please vote on releasing the following candidate as Apache Mesos
> 0.24.2.
> > >>
> > >>
> > >> 0.24.2 includes the following:
> > >>
> > >>
> >
> 
> > >>
> > >>- Improvements
> > >>   - Allocator filter performance
> > >>   - Port Ranges performance
> > >>   - UUID performance
> > >>   - `/state` endpoint performance
> > >>   - GLOG performance
> > >>   - Configurable task/framework history
> > >>   - Offer filter timeout fix for backlogged allocator
> > >>
> > >>
> > >>- Bugs
> > >>- SSL
> > >>   - Libevent
> > >>   - Fixed point resources math
> > >>- HDFS
> > >>   - Agent upgrade compatibility
> > >>   - Health checks
> > >>
> > >> 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=0.24.2-rc1
> > >>
> > >>
> >
> 
> > >>
> > >> The candidate for Mesos 0.24.2 release is available at:
> > >>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc1/mesos-0.24.2.tar.gz
> > >>
> > >> The tag to be voted on is 0.24.2-rc1:
> > >>
> >
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.2-rc1
> > >>
> > >> The MD5 checksum of the tarball can be found at:
> > >>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc1/mesos-0.24.2.tar.gz.md5
> > >>
> > >> The signature of the tarball can be found at:
> > >>
> > >>
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc1/mesos-0.24.2.tar.gz.asc
> > >>
> > >> The PGP key used to sign the release is here:
> > >> https://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-1110
> > >>
> > >> Please vote on releasing this package as Apache Mesos 0.24.2!
> > >>
> > >> The vote is open until Wed Mar 2 23:59:59 PST 2016 and passes if a
> > >> majority of at least 3 +1 PMC votes are cast.
> > >>
> > >> [ ] +1 Release this package as Apache Mesos 0.24.2
> > >> [ ] -1 Do not release this package because ...
> > >>
> > >> Thanks,
> > >>
> > >> Joris, Kapil, MPark
> > >>
> > >
> > >
> >
>

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

[Michael Park]

Vinod, we've only committed the CHANGELOGs to the specific tags. I didn't
realize that I should commit those to master as well, but it makes total
sense to do so. I'll do that. Thanks.

On 29 February 2016 at 13:50, Vinod Kone <vinodk...@apache.org> wrote:

> I don't see CHANGELOGs for these versions on the master branch?
>
> On Mon, Feb 29, 2016 at 1:39 PM, Neil Conway <neil.con...@gmail.com>
> wrote:
>
> > As described (briefly) in the release emails, 0.27.2, 0.26.1, 0.25.1,
> > and 0.24.2 contains a new feature: "reliable floating point for scalar
> > resources" (MESOS-4687).
> >
> > To elaborate on that slightly, Mesos now only supports scalar resource
> > values with three decimal digits of precision (e.g., reserving "5.001
> > CPUs" for a task). As a result of this change, frameworks that do
> > their own resource math may see slightly different results;
> > furthermore, if any frameworks were trying to manage extremely
> > fine-grained resource values (> 3 decimal digits of precision), that
> > will no longer be supported.
> >
> > For more information, please see:
> >
> >
> >
> https://mail-archives.apache.org/mod_mbox/mesos-user/201602.mbox/%3CCAOW5sYZJn5caBOwZyPV008JgL1F2FYFxL_bM5CtYA2PF2OG7Bw%40mail.gmail.com%3E
> >
> >
> https://docs.google.com/document/d/14qLxjZsfIpfynbx0USLJR0GELSq8hdZJUWw6kaY_DXc/edit?usp=sharing
> > https://issues.apache.org/jira/browse/MESOS-4687
> >
> > Neil
> >
> >
> > On Fri, Feb 26, 2016 at 8:54 PM, Michael Park <mcyp...@gmail.com> wrote:
> > > Hi all,
> > >
> > > Please vote on releasing the following candidate as Apache Mesos
> 0.27.2.
> > >
> > >
> > > 0.27.2 includes the following:
> > >
> >
> 
> > >
> > > MESOS-4693 - Variable shadowing in
> HookManager::slavePreLaunchDockerHook.
> > > MESOS-4711 - Race condition in libevent poll implementation causes
> crash.
> > > MESOS-4754 - The "executors" field is exposed under a backwards
> > incompatible
> > > schema.
> > > MESOS-4687 - Implement reliable floating point for scalar resources.
> > >
> > >
> > > 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=0.27.2-rc1
> > >
> >
> 
> > >
> > > The candidate for Mesos 0.27.2 release is available at:
> > >
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz
> > >
> > > The tag to be voted on is 0.27.2-rc1:
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.27.2-rc1
> > >
> > > The MD5 checksum of the tarball can be found at:
> > >
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz.md5
> > >
> > > The signature of the tarball can be found at:
> > >
> >
> https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz.asc
> > >
> > > The PGP key used to sign the release is here:
> > > https://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-1104
> > >
> > > Please vote on releasing this package as Apache Mesos 0.27.2!
> > >
> > > The vote is open until Wed Mar 2 23:59:59 PST 2016 and passes if a
> > majority
> > > of at least 3 +1 PMC votes are cast.
> > >
> > > [ ] +1 Release this package as Apache Mesos 0.27.2
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thanks,
> > >
> > > MPark, Joris, Kapil
> >
>

[VOTE] Release Apache Mesos 0.24.2 (rc1)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.24.2.


0.24.2 includes the following:


   - Improvements
  - Allocator filter performance
  - Port Ranges performance
  - UUID performance
  - `/state` endpoint performance
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator


   - Bugs
   - SSL
  - Libevent
  - Fixed point resources math
   - HDFS
  - Agent upgrade compatibility
  - Health checks

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=0.24.2-rc1


The candidate for Mesos 0.24.2 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc1/mesos-0.24.2.tar.gz

The tag to be voted on is 0.24.2-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.2-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc1/mesos-0.24.2.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.2-rc1/mesos-0.24.2.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1110

Please vote on releasing this package as Apache Mesos 0.24.2!

The vote is open until Wed Mar 2 23:59:59 PST 2016 and passes if a majority
of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.24.2
[ ] -1 Do not release this package because ...

Thanks,

Joris, Kapil, MPark

[VOTE] Release Apache Mesos 0.25.1 (rc1)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.25.1.


0.25.1 includes the following:


   - Improvements
  - `/state` endpoint performance
  - systemd integration
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator


   - Bugs
   - SSL
  - Libevent
  - Fixed point resources math
   - HDFS
  - Agent upgrade compatibility
  - Health checks

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=0.25.1-rc1


The candidate for Mesos 0.25.1 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz

The tag to be voted on is 0.25.1-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.25.1-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc1/mesos-0.25.1.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1108

Please vote on releasing this package as Apache Mesos 0.25.1!

The vote is open until Wed Mar 2 23:59:59 PST 2016 and passes if a majority
of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.25.1
[ ] -1 Do not release this package because ...

Thanks,

Joris, Kapil, MPark

[VOTE] Release Apache Mesos 0.26.1 (rc1)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.26.1.


0.26.1 includes the following:


   - Improvements
  - `/state` endpoint performance
  - systemd integration
  - GLOG performance
  - Configurable task/framework history
  - Offer filter timeout fix for backlogged allocator


   - Bugs
   - SSL
  - Libevent
  - Fixed point resources math
   - HDFS
  - Agent upgrade compatibility

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=0.26.1-rc1


The candidate for Mesos 0.26.1 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc1/mesos-0.26.1.tar.gz

The tag to be voted on is 0.26.1-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.26.1-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc1/mesos-0.26.1.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc1/mesos-0.26.1.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1106

Please vote on releasing this package as Apache Mesos 0.26.1!

The vote is open until Wed Mar 2 23:59:59 PST 2016 and passes if a majority
of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.26.1
[ ] -1 Do not release this package because ...

Thanks,

Joris, Kapil, MPark

[VOTE] Release Apache Mesos 0.27.2 (rc1)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.27.2.


0.27.2 includes the following:


   - MESOS-4693  -
   Variable shadowing in HookManager::slavePreLaunchDockerHook.
   - MESOS-4711  - Race
   condition in libevent poll implementation causes crash.
   - MESOS-4754  - The
   "executors" field is exposed under a backwards incompatible schema.
   - MESOS-4687  -
   Implement reliable floating point for scalar resources.


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=0.27.2-rc1


The candidate for Mesos 0.27.2 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz

The tag to be voted on is 0.27.2-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.27.2-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.27.2-rc1/mesos-0.27.2.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1104

Please vote on releasing this package as Apache Mesos 0.27.2!

The vote is open until Wed Mar 2 23:59:59 PST 2016 and passes if a majority
of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.27.2
[ ] -1 Do not release this package because ...

Thanks,

MPark, Joris, Kapil

Re: Apache Mesos Community Sync

[Michael Park]

Our next community sync will be on Thursday, February 25, 2016 at 3pm PST.

To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the
reception on the 2nd floor.
Please add your agenda items to the Google Doc
<https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA>
!

P.S. Subscribe to the Mesos Events Calendar
<https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com>
for
future meetings and events.

Thanks,

MPark

On 9 February 2016 at 01:34, Michael Park <mp...@apache.org> wrote:

> Our next community sync will be on Thursday, February 11, 2016 at 9am PST.
>
> To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the
> reception on the 2nd floor.
>
> Please add your agenda items to the Google Doc
> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA>
> !
>
> P.S. Subscribe to the Mesos Events Calendar
> <https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com>
> for future meetings and events.
>
> Thanks,
>
> MPark.
>
> On 27 January 2016 at 19:01, Michael Park <mp...@apache.org> wrote:
>
>> Our next community sync will be tomorrow January 28, 2016 at 3pm PST.
>>
>> To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the
>> reception on the 2nd floor.
>>
>> Please add your agenda items to the Google Doc
>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>> !
>>
>> P.S. Subscribe to the Mesos events calendar at
>> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
>>  for
>> future meetings and events.
>>
>> Thanks,
>>
>> MPark.
>>
>> On 13 January 2016 at 13:43, Michael Park <mcyp...@gmail.com> wrote:
>>
>>> Our next community sync will be tomorrow Jan 14 at 9pm PST (looks like
>>> I mistakenly said Jan 15 in my last email, sorry!).
>>>
>>> We'll host this one online only, and will send out links to Hangouts and
>>> OnAir tomorrow.
>>>
>>> Please add your agenda items to the Google Doc
>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>,
>>> and subscribe to the Mesos events calendar at
>>> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
>>>  for
>>> future meeting schedules.
>>>
>>> Thanks,
>>>
>>> MPark.
>>>
>>> On Tue, Dec 22, 2015 at 7:12 PM Michael Park <mcyp...@gmail.com> wrote:
>>>
>>>> Our last community sync was supposed to be on Dec 17, unfortunately we
>>>> missed it. Sorry if anyone was looking for where it was happening.
>>>>
>>>> The next one would have been on Dec 31, but given that most people will
>>>> likely be out for holidays I've updated the calendar to cancel it.
>>>>
>>>> Our next meeting is scheduled for Jan 15 at 9pm PST, and we'll send out
>>>> more detailed information as it approaches.
>>>>
>>>> Thanks,
>>>>
>>>> Happy holidays!
>>>>
>>>> MPark.
>>>>
>>>> On Thu, Dec 3, 2015 at 2:46 AM Michael Park <mcyp...@gmail.com> wrote:
>>>>
>>>>> Our next community sync will be tomorrow December 3 at 3pm PST.
>>>>>
>>>>> To join in person, come to Mesosphere HQ at 88 Stevenson St. and see
>>>>> the reception on the 2nd floor.
>>>>>
>>>>> Please add your agenda items to the Google Doc
>>>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>>>>> !
>>>>>
>>>>> Subscribe to our Mesos events calendar at
>>>>> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
>>>>>  for
>>>>> future meeting schedules.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> MPark.
>>>>>
>>>>> We will use Hangouts + YouTube OnAir, the links will be shared on IRC
>>>>> and via email shortly before the meeting.
>>>>>
>>>>> Please add agenda items to the Google Doc
>>>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>>>>> !
>>>>>
>>>>>

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

[Michael Park]

Hi all,

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

+1 (Binding)
--
Bernd Mathiske
Joris Van Remoortere
Vinod Kone

+1 (Non-binding)
--
Zhitao Li
Jörg Schad

There were no 0 or -1 votes.

Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/0.27.1

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=0.27.1

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

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

Thanks,

Joris, MPark

[VOTE] Release Apache Mesos 0.27.1 (rc1)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.27.1.


0.27.1 includes the following:

* Improved `systemd` integration.
* Ability to disable `systemd` integration.

* Additional performance improvements to /state endpoint.
* Removed duplicate "active" keys from the /state endpoint.

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=0.27.1-rc1


The candidate for Mesos 0.27.1 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.27.1-rc1/mesos-0.27.1.tar.gz

The tag to be voted on is 0.27.1-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.27.1-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.27.1-rc1/mesos-0.27.1.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.27.1-rc1/mesos-0.27.1.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1102

Please vote on releasing this package as Apache Mesos 0.27.1!

The vote is open until Fri Feb 19 17:00:00 PST 2016 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.27.1
[ ] -1 Do not release this package because ...

Thanks,

Joris, MPark

Re: Apache Mesos Community Sync

[Michael Park]

Our next community sync will be on Thursday, February 11, 2016 at 9am PST.

To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the
reception on the 2nd floor.

Please add your agenda items to the Google Doc
<https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA>
!

P.S. Subscribe to the Mesos Events Calendar
<https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com>
for future meetings and events.

Thanks,

MPark.

On 27 January 2016 at 19:01, Michael Park <mp...@apache.org> wrote:

> Our next community sync will be tomorrow January 28, 2016 at 3pm PST.
>
> To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the
> reception on the 2nd floor.
>
> Please add your agenda items to the Google Doc
> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
> !
>
> P.S. Subscribe to the Mesos events calendar at
> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
>  for
> future meetings and events.
>
> Thanks,
>
> MPark.
>
> On 13 January 2016 at 13:43, Michael Park <mcyp...@gmail.com> wrote:
>
>> Our next community sync will be tomorrow Jan 14 at 9pm PST (looks like I
>> mistakenly said Jan 15 in my last email, sorry!).
>>
>> We'll host this one online only, and will send out links to Hangouts and
>> OnAir tomorrow.
>>
>> Please add your agenda items to the Google Doc
>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>,
>> and subscribe to the Mesos events calendar at
>> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
>>  for
>> future meeting schedules.
>>
>> Thanks,
>>
>> MPark.
>>
>> On Tue, Dec 22, 2015 at 7:12 PM Michael Park <mcyp...@gmail.com> wrote:
>>
>>> Our last community sync was supposed to be on Dec 17, unfortunately we
>>> missed it. Sorry if anyone was looking for where it was happening.
>>>
>>> The next one would have been on Dec 31, but given that most people will
>>> likely be out for holidays I've updated the calendar to cancel it.
>>>
>>> Our next meeting is scheduled for Jan 15 at 9pm PST, and we'll send out
>>> more detailed information as it approaches.
>>>
>>> Thanks,
>>>
>>> Happy holidays!
>>>
>>> MPark.
>>>
>>> On Thu, Dec 3, 2015 at 2:46 AM Michael Park <mcyp...@gmail.com> wrote:
>>>
>>>> Our next community sync will be tomorrow December 3 at 3pm PST.
>>>>
>>>> To join in person, come to Mesosphere HQ at 88 Stevenson St. and see
>>>> the reception on the 2nd floor.
>>>>
>>>> Please add your agenda items to the Google Doc
>>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>>>> !
>>>>
>>>> Subscribe to our Mesos events calendar at
>>>> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
>>>>  for
>>>> future meeting schedules.
>>>>
>>>> Thanks,
>>>>
>>>> MPark.
>>>>
>>>> We will use Hangouts + YouTube OnAir, the links will be shared on IRC
>>>> and via email shortly before the meeting.
>>>>
>>>> Please add agenda items to the Google Doc
>>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>>>> !
>>>>
>>>> Thanks,
>>>>
>>>> MPark.
>>>>
>>>> On Thu, Nov 19, 2015 at 12:01 PM Michael Park <mcyp...@gmail.com>
>>>> wrote:
>>>>
>>>>> Greg Mann and I will be hosting the community sync on the web today
>>>>> (November 19) at 9pm PST.
>>>>>
>>>>> We will use Hangouts + YouTube OnAir, the links will be shared on IRC
>>>>> and via email shortly before the meeting.
>>>>>
>>>>> Please add agenda items to the Google Doc
>>>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>>>>> !
>>>>>
>>>>> Thanks,
>>>>>
>>>>> MPark.
>>>>>
>>>>> On Thu, Nov 5, 2015 at 3:20 PM Adam Bordelon <a...@mesosphere.io>
>>>>> wrote:
>>>>>
>>>&g

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

[Michael Park]

Kapil is currently working on it. We'll publish it shortly :)

On 3 February 2016 at 13:41, Benjamin Mahler <bmah...@apache.org> wrote:

> Great! Is a blog post on the way?
>
> On Sun, Jan 31, 2016 at 5:39 PM, Michael Park <mp...@apache.org> wrote:
>
> > Hi all,
> >
> > The vote for Mesos 0.27.0 (rc2) has passed with the
> > following votes.
> >
> > +1 (Binding)
> > --
> > Vinod Kone
> > Joris Van Remoortere
> > Till Toenshoff
> >
> > +1 (Non-binding)
> > --
> > Jörg Schad
> > Marco Massenzio
> > Greg Mann
> >
> > There were no 0 or -1 votes.
> >
> > Please find the release at:
> > https://dist.apache.org/repos/dist/release/mesos/0.27.0
> >
> > 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=0.27.0
> >
> > The mesos-0.27.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,
> >
> > Tim, Kapil, MPark
> >
>

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

[Michael Park]

Hi all,

The vote for Mesos 0.27.0 (rc2) has passed with the
following votes.

+1 (Binding)
--
Vinod Kone
Joris Van Remoortere
Till Toenshoff

+1 (Non-binding)
--
Jörg Schad
Marco Massenzio
Greg Mann

There were no 0 or -1 votes.

Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/0.27.0

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=0.27.0

The mesos-0.27.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,

Tim, Kapil, MPark

Re: Apache Mesos Community Sync

[Michael Park]

Our next community sync will be tomorrow January 28, 2016 at 3pm PST.

To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the
reception on the 2nd floor.

Please add your agenda items to the Google Doc
<https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
!

P.S. Subscribe to the Mesos events calendar at
https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
for
future meetings and events.

Thanks,

MPark.

On 13 January 2016 at 13:43, Michael Park <mcyp...@gmail.com> wrote:

> Our next community sync will be tomorrow Jan 14 at 9pm PST (looks like I
> mistakenly said Jan 15 in my last email, sorry!).
>
> We'll host this one online only, and will send out links to Hangouts and
> OnAir tomorrow.
>
> Please add your agenda items to the Google Doc
> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>,
> and subscribe to the Mesos events calendar at
> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
>  for
> future meeting schedules.
>
> Thanks,
>
> MPark.
>
> On Tue, Dec 22, 2015 at 7:12 PM Michael Park <mcyp...@gmail.com> wrote:
>
>> Our last community sync was supposed to be on Dec 17, unfortunately we
>> missed it. Sorry if anyone was looking for where it was happening.
>>
>> The next one would have been on Dec 31, but given that most people will
>> likely be out for holidays I've updated the calendar to cancel it.
>>
>> Our next meeting is scheduled for Jan 15 at 9pm PST, and we'll send out
>> more detailed information as it approaches.
>>
>> Thanks,
>>
>> Happy holidays!
>>
>> MPark.
>>
>> On Thu, Dec 3, 2015 at 2:46 AM Michael Park <mcyp...@gmail.com> wrote:
>>
>>> Our next community sync will be tomorrow December 3 at 3pm PST.
>>>
>>> To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the
>>> reception on the 2nd floor.
>>>
>>> Please add your agenda items to the Google Doc
>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>>> !
>>>
>>> Subscribe to our Mesos events calendar at
>>> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
>>>  for
>>> future meeting schedules.
>>>
>>> Thanks,
>>>
>>> MPark.
>>>
>>> We will use Hangouts + YouTube OnAir, the links will be shared on IRC
>>> and via email shortly before the meeting.
>>>
>>> Please add agenda items to the Google Doc
>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>>> !
>>>
>>> Thanks,
>>>
>>> MPark.
>>>
>>> On Thu, Nov 19, 2015 at 12:01 PM Michael Park <mcyp...@gmail.com> wrote:
>>>
>>>> Greg Mann and I will be hosting the community sync on the web today
>>>> (November 19) at 9pm PST.
>>>>
>>>> We will use Hangouts + YouTube OnAir, the links will be shared on IRC
>>>> and via email shortly before the meeting.
>>>>
>>>> Please add agenda items to the Google Doc
>>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>>>> !
>>>>
>>>> Thanks,
>>>>
>>>> MPark.
>>>>
>>>> On Thu, Nov 5, 2015 at 3:20 PM Adam Bordelon <a...@mesosphere.io>
>>>> wrote:
>>>>
>>>>> Sorry for the late link, but you can see the youtube stream (and
>>>>> after-the-fact video) at: http://youtu.be/rJyT8xDzhcA
>>>>>
>>>>> We also have a hangout link for those with agenda items, or those who
>>>>> have
>>>>> lengthy things to discuss (ask if you need the link). For brief
>>>>> questions,
>>>>> you can add them to the agenda or ask in IRC and I will relay them for
>>>>> you.
>>>>>
>>>>> On Wed, Nov 4, 2015 at 4:42 PM, Adam Bordelon <a...@mesosphere.io>
>>>>> wrote:
>>>>>
>>>>> > Sounds great! Please join us at Mesosphere HQ, 88 Stevenson St., SF
>>>>> at 3pm
>>>>> > Pacific tomorrow.
>>>>> > We will use youtube-onair again, links to be posted to IRC/email
>>>>> shortly
>>>>> > before the meeting.
>>>>> &

[VOTE] Release Apache Mesos 0.27.0 (rc2)

[Michael Park]

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.27.0.

0.27.0 includes the following:

We added major features such as Implicit Roles, Quota, Multiple Disks and
more.

We also added major bug fixes such as performance improvements to
state.json requests and GLOG.

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=0.27.0-rc2


The candidate for Mesos 0.27.0 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.27.0-rc2/mesos-0.27.0.tar.gz

The tag to be voted on is 0.27.0-rc2:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.27.0-rc2

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.27.0-rc2/mesos-0.27.0.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.27.0-rc2/mesos-0.27.0.tar.gz.asc

The PGP key used to sign the release is here:
https://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-1100

Please vote on releasing this package as Apache Mesos 0.27.0!

The vote is open until Sat Jan 30 23:59:59 PST 2016 and passes if a
majority of at least 3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Mesos 0.27.0
[ ] -1 Do not release this package because ...

Thanks,

Tim, Kapil, MPark

Re: Apache Mesos Community Sync

[Michael Park]

Our next community sync will be tomorrow Jan 14 at 9pm PST (looks like I
mistakenly said Jan 15 in my last email, sorry!).

We'll host this one online only, and will send out links to Hangouts and
OnAir tomorrow.

Please add your agenda items to the Google Doc
<https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>,
and subscribe to the Mesos events calendar at
https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
for
future meeting schedules.

Thanks,

MPark.

On Tue, Dec 22, 2015 at 7:12 PM Michael Park <mcyp...@gmail.com> wrote:

> Our last community sync was supposed to be on Dec 17, unfortunately we
> missed it. Sorry if anyone was looking for where it was happening.
>
> The next one would have been on Dec 31, but given that most people will
> likely be out for holidays I've updated the calendar to cancel it.
>
> Our next meeting is scheduled for Jan 15 at 9pm PST, and we'll send out
> more detailed information as it approaches.
>
> Thanks,
>
> Happy holidays!
>
> MPark.
>
> On Thu, Dec 3, 2015 at 2:46 AM Michael Park <mcyp...@gmail.com> wrote:
>
>> Our next community sync will be tomorrow December 3 at 3pm PST.
>>
>> To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the
>> reception on the 2nd floor.
>>
>> Please add your agenda items to the Google Doc
>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>> !
>>
>> Subscribe to our Mesos events calendar at
>> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
>>  for
>> future meeting schedules.
>>
>> Thanks,
>>
>> MPark.
>>
>> We will use Hangouts + YouTube OnAir, the links will be shared on IRC and
>> via email shortly before the meeting.
>>
>> Please add agenda items to the Google Doc
>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>> !
>>
>> Thanks,
>>
>> MPark.
>>
>> On Thu, Nov 19, 2015 at 12:01 PM Michael Park <mcyp...@gmail.com> wrote:
>>
>>> Greg Mann and I will be hosting the community sync on the web today
>>> (November 19) at 9pm PST.
>>>
>>> We will use Hangouts + YouTube OnAir, the links will be shared on IRC
>>> and via email shortly before the meeting.
>>>
>>> Please add agenda items to the Google Doc
>>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>>> !
>>>
>>> Thanks,
>>>
>>> MPark.
>>>
>>> On Thu, Nov 5, 2015 at 3:20 PM Adam Bordelon <a...@mesosphere.io> wrote:
>>>
>>>> Sorry for the late link, but you can see the youtube stream (and
>>>> after-the-fact video) at: http://youtu.be/rJyT8xDzhcA
>>>>
>>>> We also have a hangout link for those with agenda items, or those who
>>>> have
>>>> lengthy things to discuss (ask if you need the link). For brief
>>>> questions,
>>>> you can add them to the agenda or ask in IRC and I will relay them for
>>>> you.
>>>>
>>>> On Wed, Nov 4, 2015 at 4:42 PM, Adam Bordelon <a...@mesosphere.io>
>>>> wrote:
>>>>
>>>> > Sounds great! Please join us at Mesosphere HQ, 88 Stevenson St., SF
>>>> at 3pm
>>>> > Pacific tomorrow.
>>>> > We will use youtube-onair again, links to be posted to IRC/email
>>>> shortly
>>>> > before the meeting.
>>>> >
>>>> > Please add agenda items:
>>>> >
>>>> >
>>>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#heading=h.za1f9dpxisdr
>>>> >
>>>> > On Wed, Nov 4, 2015 at 4:25 PM, Jie Yu <yujie@gmail.com> wrote:
>>>> >
>>>> >> Adam, since most of the Twitter folks are OOO this week. I chatted
>>>> with
>>>> >> Artem/Vinod. we think it makes sense to host the sync at Mesosphere
>>>> >> tomorrow.
>>>> >>
>>>> >> - Jie
>>>> >>
>>>> >> On Wed, Nov 4, 2015 at 4:22 PM, Adam Bordelon <a...@mesosphere.io>
>>>> wrote:
>>>> >>
>>>> >>> It's been a while since our last community sync, and tomorrow,
>>>> Thursday
>>>> >>> Nov 5th shows up on my calendar as a 3pm Twitte

Re: Apache Mesos Community Sync

[Michael Park]

Our last community sync was supposed to be on Dec 17, unfortunately we
missed it. Sorry if anyone was looking for where it was happening.

The next one would have been on Dec 31, but given that most people will
likely be out for holidays I've updated the calendar to cancel it.

Our next meeting is scheduled for Jan 15 at 9pm PST, and we'll send out
more detailed information as it approaches.

Thanks,

Happy holidays!

MPark.

On Thu, Dec 3, 2015 at 2:46 AM Michael Park <mcyp...@gmail.com> wrote:

> Our next community sync will be tomorrow December 3 at 3pm PST.
>
> To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the
> reception on the 2nd floor.
>
> Please add your agenda items to the Google Doc
> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
> !
>
> Subscribe to our Mesos events calendar at
> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
>  for
> future meeting schedules.
>
> Thanks,
>
> MPark.
>
> We will use Hangouts + YouTube OnAir, the links will be shared on IRC and
> via email shortly before the meeting.
>
> Please add agenda items to the Google Doc
> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
> !
>
> Thanks,
>
> MPark.
>
> On Thu, Nov 19, 2015 at 12:01 PM Michael Park <mcyp...@gmail.com> wrote:
>
>> Greg Mann and I will be hosting the community sync on the web today
>> (November 19) at 9pm PST.
>>
>> We will use Hangouts + YouTube OnAir, the links will be shared on IRC and
>> via email shortly before the meeting.
>>
>> Please add agenda items to the Google Doc
>> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
>> !
>>
>> Thanks,
>>
>> MPark.
>>
>> On Thu, Nov 5, 2015 at 3:20 PM Adam Bordelon <a...@mesosphere.io> wrote:
>>
>>> Sorry for the late link, but you can see the youtube stream (and
>>> after-the-fact video) at: http://youtu.be/rJyT8xDzhcA
>>>
>>> We also have a hangout link for those with agenda items, or those who
>>> have
>>> lengthy things to discuss (ask if you need the link). For brief
>>> questions,
>>> you can add them to the agenda or ask in IRC and I will relay them for
>>> you.
>>>
>>> On Wed, Nov 4, 2015 at 4:42 PM, Adam Bordelon <a...@mesosphere.io>
>>> wrote:
>>>
>>> > Sounds great! Please join us at Mesosphere HQ, 88 Stevenson St., SF at
>>> 3pm
>>> > Pacific tomorrow.
>>> > We will use youtube-onair again, links to be posted to IRC/email
>>> shortly
>>> > before the meeting.
>>> >
>>> > Please add agenda items:
>>> >
>>> >
>>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#heading=h.za1f9dpxisdr
>>> >
>>> > On Wed, Nov 4, 2015 at 4:25 PM, Jie Yu <yujie@gmail.com> wrote:
>>> >
>>> >> Adam, since most of the Twitter folks are OOO this week. I chatted
>>> with
>>> >> Artem/Vinod. we think it makes sense to host the sync at Mesosphere
>>> >> tomorrow.
>>> >>
>>> >> - Jie
>>> >>
>>> >> On Wed, Nov 4, 2015 at 4:22 PM, Adam Bordelon <a...@mesosphere.io>
>>> wrote:
>>> >>
>>> >>> It's been a while since our last community sync, and tomorrow,
>>> Thursday
>>> >>> Nov 5th shows up on my calendar as a 3pm Twitter-hosted meeting,
>>> since
>>> >>> those have traditionally been "Monthly on the first Thursday". After
>>> >>> this, the other meetings (third Thursday, or every other week?) can
>>> >>> alternate between 9pm/9am. Let's get these on the calendar
>>> officially.
>>> >>>
>>> >>> Vinod, are you/Twitter still planning to host the community sync
>>> >>> tomorrow?
>>> >>>
>>> >>> On Wed, Oct 14, 2015 at 1:01 AM, Adam Bordelon <a...@mesosphere.io>
>>> >>> wrote:
>>> >>>
>>> >>>> We'll have the next community sync this Thursday (Oct. 15th) from
>>> >>>> 9-10am Pacific.
>>> >>>>
>>> >>>> Please add items to the agenda
>>> >>>> <
>>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#
>>&

Re: Apache Mesos Community Sync

[Michael Park]

Our next community sync will be tomorrow December 3 at 3pm PST.

To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the
reception on the 2nd floor.

Please add your agenda items to the Google Doc
<https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
!

Subscribe to our Mesos events calendar at
https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com
for
future meeting schedules.

Thanks,

MPark.

We will use Hangouts + YouTube OnAir, the links will be shared on IRC and
via email shortly before the meeting.

Please add agenda items to the Google Doc
<https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
!

Thanks,

MPark.

On Thu, Nov 19, 2015 at 12:01 PM Michael Park <mcyp...@gmail.com> wrote:

> Greg Mann and I will be hosting the community sync on the web today
> (November 19) at 9pm PST.
>
> We will use Hangouts + YouTube OnAir, the links will be shared on IRC and
> via email shortly before the meeting.
>
> Please add agenda items to the Google Doc
> <https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#>
> !
>
> Thanks,
>
> MPark.
>
> On Thu, Nov 5, 2015 at 3:20 PM Adam Bordelon <a...@mesosphere.io> wrote:
>
>> Sorry for the late link, but you can see the youtube stream (and
>> after-the-fact video) at: http://youtu.be/rJyT8xDzhcA
>>
>> We also have a hangout link for those with agenda items, or those who have
>> lengthy things to discuss (ask if you need the link). For brief questions,
>> you can add them to the agenda or ask in IRC and I will relay them for
>> you.
>>
>> On Wed, Nov 4, 2015 at 4:42 PM, Adam Bordelon <a...@mesosphere.io> wrote:
>>
>> > Sounds great! Please join us at Mesosphere HQ, 88 Stevenson St., SF at
>> 3pm
>> > Pacific tomorrow.
>> > We will use youtube-onair again, links to be posted to IRC/email shortly
>> > before the meeting.
>> >
>> > Please add agenda items:
>> >
>> >
>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#heading=h.za1f9dpxisdr
>> >
>> > On Wed, Nov 4, 2015 at 4:25 PM, Jie Yu <yujie@gmail.com> wrote:
>> >
>> >> Adam, since most of the Twitter folks are OOO this week. I chatted with
>> >> Artem/Vinod. we think it makes sense to host the sync at Mesosphere
>> >> tomorrow.
>> >>
>> >> - Jie
>> >>
>> >> On Wed, Nov 4, 2015 at 4:22 PM, Adam Bordelon <a...@mesosphere.io>
>> wrote:
>> >>
>> >>> It's been a while since our last community sync, and tomorrow,
>> Thursday
>> >>> Nov 5th shows up on my calendar as a 3pm Twitter-hosted meeting, since
>> >>> those have traditionally been "Monthly on the first Thursday". After
>> >>> this, the other meetings (third Thursday, or every other week?) can
>> >>> alternate between 9pm/9am. Let's get these on the calendar officially.
>> >>>
>> >>> Vinod, are you/Twitter still planning to host the community sync
>> >>> tomorrow?
>> >>>
>> >>> On Wed, Oct 14, 2015 at 1:01 AM, Adam Bordelon <a...@mesosphere.io>
>> >>> wrote:
>> >>>
>> >>>> We'll have the next community sync this Thursday (Oct. 15th) from
>> >>>> 9-10am Pacific.
>> >>>>
>> >>>> Please add items to the agenda
>> >>>> <
>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#
>> >
>> >>>> .
>> >>>>
>> >>>>
>> >>>> We will use Hangouts on Air again. We will post the video stream link
>> >>>> shortly before the meeting, and only active participants (especially
>> people
>> >>>> on the agenda) should join the actual hangout. Others can watch the
>> video
>> >>>> stream and ask brief questions on #mesos on IRC. If you have
>> something
>> >>>> lengthier to discuss, put it on the agenda and ping us on email/IRC
>> to get
>> >>>> into the hangout.
>> >>>>
>> >>>> To join in person, come to Mesosphere HQ at 88 Stevenson St and see
>> >>>> reception on the 2nd floor.
>> >>>>
>> >>>>
>> >>>> On Thu, Oct 1, 2015 at 9:30 AM, haosdent <haosd...@gmail.com> wrote:
>> >>>&g

Re: Mesos Events Calendar

[Michael Park]

I can definitely add a finite list of admins, but I don't think I can just
open it up to the public (we probably don't want to anyway).
I've added your gmail account as one of the admins to start, I think
perhaps we organically grow the list for interested individuals?

Suggestions welcome for better approaches to this.

On Fri, Nov 20, 2015 at 8:54 AM Benjamin Mahler <benjamin.mah...@gmail.com>
wrote:

> Nice, is there a way to open up the calendar so that others can add events?
>
> On Fri, Nov 20, 2015 at 8:42 AM, Michael Park <mp...@apache.org> wrote:
>
>> Hello, I've created a public events calendar:
>>
>>
>> https://calendar.google.com/calendar/embed?src=2hecvndc0mnaqlir34cqnfvtak%40group.calendar.google.com=America/Los_Angeles
>>
>> The intent is to capture the community sync schedules there as well as
>> other events such as MesosCon and meet-ups.
>>
>> The following review request https://reviews.apache.org/r/40531/ embeds
>> the Events Calendar in our Community page.
>>
>> [image: Screen Shot 2015-11-19 at 11.34.17 PM.png]
>>
>
>

Re: Apache Mesos Community Sync

[Michael Park]

Greg Mann and I will be hosting the community sync on the web today
(November 19) at 9pm PST.

We will use Hangouts + YouTube OnAir, the links will be shared on IRC and
via email shortly before the meeting.

Please add agenda items to the Google Doc

!

Thanks,

MPark.

On Thu, Nov 5, 2015 at 3:20 PM Adam Bordelon  wrote:

> Sorry for the late link, but you can see the youtube stream (and
> after-the-fact video) at: http://youtu.be/rJyT8xDzhcA
>
> We also have a hangout link for those with agenda items, or those who have
> lengthy things to discuss (ask if you need the link). For brief questions,
> you can add them to the agenda or ask in IRC and I will relay them for you.
>
> On Wed, Nov 4, 2015 at 4:42 PM, Adam Bordelon  wrote:
>
> > Sounds great! Please join us at Mesosphere HQ, 88 Stevenson St., SF at
> 3pm
> > Pacific tomorrow.
> > We will use youtube-onair again, links to be posted to IRC/email shortly
> > before the meeting.
> >
> > Please add agenda items:
> >
> >
> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#heading=h.za1f9dpxisdr
> >
> > On Wed, Nov 4, 2015 at 4:25 PM, Jie Yu  wrote:
> >
> >> Adam, since most of the Twitter folks are OOO this week. I chatted with
> >> Artem/Vinod. we think it makes sense to host the sync at Mesosphere
> >> tomorrow.
> >>
> >> - Jie
> >>
> >> On Wed, Nov 4, 2015 at 4:22 PM, Adam Bordelon 
> wrote:
> >>
> >>> It's been a while since our last community sync, and tomorrow, Thursday
> >>> Nov 5th shows up on my calendar as a 3pm Twitter-hosted meeting, since
> >>> those have traditionally been "Monthly on the first Thursday". After
> >>> this, the other meetings (third Thursday, or every other week?) can
> >>> alternate between 9pm/9am. Let's get these on the calendar officially.
> >>>
> >>> Vinod, are you/Twitter still planning to host the community sync
> >>> tomorrow?
> >>>
> >>> On Wed, Oct 14, 2015 at 1:01 AM, Adam Bordelon 
> >>> wrote:
> >>>
>  We'll have the next community sync this Thursday (Oct. 15th) from
>  9-10am Pacific.
> 
>  Please add items to the agenda
>  <
> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#
> >
>  .
> 
> 
>  We will use Hangouts on Air again. We will post the video stream link
>  shortly before the meeting, and only active participants (especially
> people
>  on the agenda) should join the actual hangout. Others can watch the
> video
>  stream and ask brief questions on #mesos on IRC. If you have something
>  lengthier to discuss, put it on the agenda and ping us on email/IRC
> to get
>  into the hangout.
> 
>  To join in person, come to Mesosphere HQ at 88 Stevenson St and see
>  reception on the 2nd floor.
> 
> 
>  On Thu, Oct 1, 2015 at 9:30 AM, haosdent  wrote:
> 
> > Got it. Thank you.
> >
> > On Fri, Oct 2, 2015 at 12:27 AM, Gilbert Song  >
> > wrote:
> >
> > > Yes, community sync is at 3 pm PST today afternoon. Video Link is
> > still not
> > > available. And here is the link for meeting agenda/notes:
> > >
> > >
> > >
> >
> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit?usp=sharing
> > >
> > > On Thu, Oct 1, 2015 at 9:19 AM, haosdent 
> wrote:
> > >
> > > > Do today have community sync?
> > > >
> > > > On Fri, Sep 18, 2015 at 12:59 AM, Adam Bordelon <
> > a...@mesosphere.io>
> > > > wrote:
> > > >
> > > > > Today's community sync video/audio is archived at:
> > > > > http://youtu.be/ZQT6-fw8Ito
> > > > > The meeting agenda/notes are available at:
> > > > >
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit?usp=sharing
> > > > >
> > > > > For convenience, today's notes are reproduced below:
> > > > >
> > > > >-
> > > > >
> > > > >0.21.2-0.24.1 Patch Releases [Adam]
> > > > >-
> > > > >
> > > > >   What’s the plan for how many releases we want to support?
> > BenH:
> > > > >   Support at least 3 versions (e.g. 0.22.x, 0.23.x, 0.24.x)
> > for
> > > > > which we will
> > > > >   do patch fixes
> > > > >   Neil: Or support an LTS version + recent releases
> > > > >   -
> > > > >
> > > > >   Separate Release Manager for backports? Joris and MPark
> > will RM
> > > for
> > > > >   these patch releases, with Adam shepherding. In general,
> > > > patch/point
> > > > >   releases don’t need to be managed by the same person who
> > did the
> > > > > original
> > > > >   

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

[Michael Park]

+1 (binding)

Ran *make distcheck* successfully on Ubuntu 14.04 with gcc + clang, CentOS
7.1 with gcc
Ran *make check* with one non-blocker failure (MESOS-3604
) on OS X El Capitan with
clang

On Thu, Oct 8, 2015 at 12:33 AM Kapil Arya  wrote:

> PS: The fix is already in master branch
> (bfeb070a2aef52f445eb057076d344fd184eb461), just need to cherry-pick it
> into RC2.
>
> On Wed, Oct 7, 2015 at 7:25 PM, Kapil Arya  wrote:
>
>> -1 (non-binding)
>>
>> Compilation fails on OpenSUSE Tumbleweed (Linux 4.1.6, gcc 5.1.1, glibc
>> 2.22) with the following errors:
>> [Created Issue: https://issues.apache.org/jira/browse/MESOS-3603]
>>
>>
>> In file included from ../../src/tests/values_tests.cpp:22:0:
>> ../3rdparty/libprocess/3rdparty/gmock-1.7.0/gtest/include/gtest/gtest.h:
>> In instantiatio
>> n of ‘testing::AssertionResult testing::internal::CmpHelperEQ(const
>> char*, const char*,
>> const T1&, const T2&) [with T1 = int; T2 = long unsigned int]’:
>> ../3rdparty/libprocess/3rdparty/gmock-1.7.0/gtest/include/gtest/gtest.h:1484:23:
>>   requi
>> red from ‘static testing::AssertionResult
>> testing::internal::EqHelper> l>::Compare(const char*, const char*, const T1&, const T2&) [with T1 =
>> int; T2 = long un
>> signed int; bool lhs_is_null_literal = false]’
>> ../../src/tests/values_tests.cpp:287:3:   required from here
>> ../3rdparty/libprocess/3rdparty/gmock-1.7.0/gtest/include/gtest/gtest.h:1448:16:
>> error:
>> comparison between signed and unsigned integer expressions
>> [-Werror=sign-compare]
>>   if (expected == actual) {
>>^
>>  CXX  tests/containerizer/mesos_tests-provisioner_docker_tests.o
>> ^CMakefile:6779: recipe for target 'tests/mesos_tests-values_tests.o'
>> failed
>> make[3]: *** [tests/mesos_tests-values_tests.o] Interrupt
>>
>> ===
>>
>> System details:
>>
>> $ uname -a
>> Linux thinkpad 4.1.6-3-desktop #1 SMP PREEMPT Fri Aug 28 10:59:34 UTC
>> 2015 (d867e86) x86_64 x86_64 x86_64 GNU/Linux
>>
>> $ gcc --version
>> gcc (SUSE Linux) 5.1.1 20150713 [gcc-5-branch revision 225736]
>> Copyright (C) 2015 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.  There is NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>> PURPOSE.
>>
>> $ /lib64/libc.so.6
>> GNU C Library (GNU libc) stable release version 2.22 (git bbab82c25da9),
>> by Roland McGrath et al.
>> Copyright (C) 2015 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.
>> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
>> PARTICULAR PURPOSE.
>> Configured for x86_64-suse-linux.
>> Compiled by GNU CC version 5.1.1 20150713 [gcc-5-branch revision 225736].
>> Available extensions:
>> crypt add-on version 2.1 by Michael Glad and others
>> GNU Libidn by Simon Josefsson
>> Native POSIX Threads Library by Ulrich Drepper et al
>> BIND-8.2.3-T5B
>> libc ABIs: UNIQUE IFUNC
>> For bug reporting instructions, please see:
>> .
>>
>> $ cat /etc/SuSE-release
>> openSUSE 20150909 (x86_64)
>> VERSION = 20150909
>> CODENAME = Tumbleweed
>> # /etc/SuSE-release is deprecated and will be removed in the future, use
>> /etc/os-release instead
>>
>>
>>
>> On Wed, Oct 7, 2015 at 6:14 PM, Greg Mann  wrote:
>>
>>> Successfully built `sudo make distcheck` on CentOS 7.1 and Ubuntu 14.04
>>> with only expected test failures. On our Fedora 22 CI build, however,
>>> while
>>> the tests are building the following compile-time error is produced:
>>>
>>> [17:18:46][Step 4/6]   CXX
>>>  tests/containerizer/mesos_tests-composing_containerizer_tests.o
>>>
>>> [17:18:48][Step 4/6] In file included from
>>> ../../../src/tests/values_tests.cpp:22:0:
>>>
>>> [17:18:48][Step 4/6]
>>> ../3rdparty/libprocess/3rdparty/gmock-1.7.0/gtest/include/gtest/gtest.h:
>>> In
>>> instantiation of ‘testing::AssertionResult
>>> testing::internal::CmpHelperEQ(const char*, const char*, const T1&, const
>>> T2&) [with T1 = int; T2 = long unsigned int]’:
>>>
>>> [17:18:48][Step 4/6]
>>>
>>> ../3rdparty/libprocess/3rdparty/gmock-1.7.0/gtest/include/gtest/gtest.h:1484:23:
>>>   required from ‘static testing::AssertionResult
>>> testing::internal::EqHelper::Compare(const char*,
>>> const char*, const T1&, const T2&) [with T1 = int; T2 = long unsigned
>>> int;
>>> bool lhs_is_null_literal = false]’
>>>
>>> [17:18:48][Step 4/6] ../../../src/tests/values_tests.cpp:149:3:
>>>  required
>>> from here
>>>
>>> [17:18:48][Step 4/6]
>>>
>>> ../3rdparty/libprocess/3rdparty/gmock-1.7.0/gtest/include/gtest/gtest.h:1448:16:
>>> error: comparison between signed and unsigned integer expressions
>>> [-Werror=sign-compare]
>>>
>>> [17:18:48][Step 4/6]if (expected == actual) {
>>>
>>> [17:18:48][Step 4/6] ^
>>>
>>>
>>> Cherry-picking one commit (bfeb070a2aef52f445e "Fixed compiler 

Re: OS X build

[Michael Park]

Hi Vaibhav,

What version of OS X do you have? Do you not have */usr/include/apr-1* or
*/usr/include/apr-1.0* available?
I also installed *apr-1.5.2* via *brew install apr* and *../configure
--with-apr=/usr/local/Cellar/apr/1.5.2/libexec* worked fine for me.

As far as how *configure.ac * is written, when
*--with-apr* is specified, it prepends *-I${with_apr}/include/apr-1*
*-I${with_apr}/include/apr-1.0* and
*-L${with_apr}/lib*. if *--with-apr* is not specified, it uses
*-I/usr/include/apr-1
-I/usr/include/apr-1.0*.

I hope this helps a little. Please keep us posted.

Thanks,

MPark.

On Sun, Sep 27, 2015 at 9:25 PM James Peach  wrote:

>
> > On Sep 27, 2015, at 4:15 PM, Vaibhav Khanduja 
> wrote:
> >
> > Probably yes,
> >
> > The issue which I am pointing out is with the configure script not
> accepting option "—with-arp"
>
> OK then I'm confused because there is a --with-apr option, and it works
> AFAICT
>
> jpeach$ ./configure --help | grep apr
>   --with-apr=[=DIR]   specify where to locate the apr-1 library
>
> >
> > On Sat, Sep 26, 2015 at 9:26 PM, James Peach  wrote:
> >
> > > On Sep 26, 2015, at 12:01 PM, Vaibhav Khanduja <
> vaibhavkhand...@gmail.com> wrote:
> > >
> > > I am running into issues with build on my MAC - OSX … the configure
> scripts complaints about libapr-1 not present. I was able to find a
> workaround by passing configure with —with-apr option. Looks like the
> script checks for variable to be valid shell variable, if not it is
> rejected.
> > >
> > > I was able workaround with having quotes and missing a “-“ for the
> variable
> > >
> > >  ../configure -disable-python --disable-java
> "-with-apr=/usr/local/Cellar/apr/1.5.2/libexec/“
> > >
> > > the configure —help though suggests to use —with-apr
> >
> > AFAICT you are supposed to use apr-1-config to fish out the libapr path
> when using Homebrew. I think that is would be reasonable for the Mesos
> build to just automatically use apr-1-config if it is present.
> >
> > ./configure --with-apr=$(apr-1-config --prefix)
> >
> > >
> > >
> > > am I missing something here?
> > >
> > > Thx
> >
> >
>
>

Re: Reservations for multiple different agents

[Michael Park]

Regarding the credentials file behavior, it seems to be a bug. I've filed:
https://issues.apache.org/jira/browse/MESOS-3560

On Tue, Sep 29, 2015 at 8:28 PM Michael Park <mcyp...@gmail.com> wrote:

> Oops, that should've been:
>
> *  {*
> *"credentials": [*
> *  {*
> *"principal": "mesos-mach5-beta",*
> *"secret": " cGFzc3dvcmQ="*
> *  }*
> *]*
> *  }*
>
> On Tue, Sep 29, 2015 at 8:20 PM Michael Park <mcyp...@gmail.com> wrote:
>
>> I'll look into what's happening with the framework registration, but
>> meanwhile I've also taken a look at what's going on with the master
>> endpoints.
>>
>> It looks like the issue is around authentication rather than the dynamic
>> reservation endpoints.
>>
>> When using *JSON-based* credentials file, the password should be given
>> in *base64 encoded* format.
>> So your credentials file should be:
>>
>> *  {*
>> *"credentials": [*
>> *  {*
>> *"principal": "mesos-mach5-beta",*
>> *"secret": " cGFzc3dvcmQ"*
>> *  }*
>> *]*
>> *  }*
>>
>> It looks like this behavior is not documented well on the master. I'll be
>> fixing that shortly.
>>
>> Thanks,
>>
>> MPark.
>>
>>
>> On Tue, Sep 29, 2015 at 4:27 PM DiGiorgio, Mr. Rinaldo S. <
>> rdigior...@pace.edu> wrote:
>>
>>> MPark,
>>>
>>> Thanks for your identification of something that was not configured.  I
>>> am using the mesos-plugin in Jenkins. I had not specified a principal. I
>>> added the principal and it appears to register with that principal if I
>>> don’t provide a password from the meson-plugin.  When I  try to perform a
>>> reservation I get the authentication issue. So I thought perhaps the
>>> framework must register with a password. I added the password and restarted
>>> both jenkins and the meson-master.  I get the following in the logs.
>>>
>>>
>>> W0929 13:17:56.672214 346357760 master.cpp:5165] Failed to authenticate
>>> scheduler-a6d69250-48dc-4474-8af8-89bb35fabb92@10.133.69.83:49817:
>>> Refused authentication
>>> *** Aborted at 1443557876 (unix time) try "date -d @1443557876" if you
>>> are using GNU date ***
>>> PC: @     0x7fff8ad419a4 _pthread_mutex_check_init
>>> *** SIGSEGV (@0x1) received by PID 62883 (TID 0x114ad3000) stack trace:
>>> ***
>>> @ 0x7fff8d09f5aa _sigtramp
>>>
>>> I am sure ntp is the same since I have set the time with ntp and both
>>> the mesos master and jenkins are on the same machine.  The authentication
>>> process requires accurate clocks — since it is just the framework
>>> registering I have not looked at the slaves.
>>>
>>>
>>>
>>> Rinaldo
>>>
>>>
>>> On Sep 29, 2015, at 3:03 PM, Michael Park <mcyp...@gmail.com> wrote:
>>>
>>> Hi Rinaldo,
>>>
>>> Sorry that you're having trouble using dynamic reservations.
>>>
>>> I see that you're specifying the *mesos-mach5-beta* principal on the
>>> resources, but I'm not sure if your framework is registered with the
>>> *mesos-mach5-beta* principal? The framework must set the *
>>> FrameworkInfo::principal* to be registered under that *principal*.
>>>
>>> Please let me know whether that is the case or not, and I'll follow up
>>> with you to resolve the issue.
>>>
>>> Thanks,
>>>
>>> MPark.
>>>
>>> On Tue, Sep 29, 2015 at 1:53 PM DiGiorgio, Mr. Rinaldo S. <
>>> rdigior...@pace.edu> wrote:
>>>
>>>> Joseph,
>>>>
>>>>I thought I tried that.  So I must still not following the
>>>> directions. Here is what I have?
>>>>
>>>> mesos master running on OS X 10.10.5  mesos 0.26
>>>>
>>>> I perform the following curl operation below.
>>>>
>>>> server reads credentials file
>>>>
>>>> I0929 10:48:42.062871 291536896 credentials.hpp:37] Loading credentials
>>>> for authentication from '/etc/mesos-master/attributes/credentials'
>>>> I0929 10:48:42.065512 291536896 master.cpp:467] Using default 'crammd5'
>>>> authenticator
>>>>
>>>>
>>>>  The result of trying to reserve is:  *Could n

Re: Reservations for multiple different agents

[Michael Park]

I'll look into what's happening with the framework registration, but
meanwhile I've also taken a look at what's going on with the master
endpoints.

It looks like the issue is around authentication rather than the dynamic
reservation endpoints.

When using *JSON-based* credentials file, the password should be given
in *base64
encoded* format.
So your credentials file should be:

*  {*
*"credentials": [*
*  {*
*"principal": "mesos-mach5-beta",*
*"secret": " cGFzc3dvcmQ"*
*  }*
*]*
*  }*

It looks like this behavior is not documented well on the master. I'll be
fixing that shortly.

Thanks,

MPark.

On Tue, Sep 29, 2015 at 4:27 PM DiGiorgio, Mr. Rinaldo S. <
rdigior...@pace.edu> wrote:

> MPark,
>
> Thanks for your identification of something that was not configured.  I am
> using the mesos-plugin in Jenkins. I had not specified a principal. I added
> the principal and it appears to register with that principal if I don’t
> provide a password from the meson-plugin.  When I  try to perform a
> reservation I get the authentication issue. So I thought perhaps the
> framework must register with a password. I added the password and restarted
> both jenkins and the meson-master.  I get the following in the logs.
>
>
> W0929 13:17:56.672214 346357760 master.cpp:5165] Failed to authenticate
> scheduler-a6d69250-48dc-4474-8af8-89bb35fabb92@10.133.69.83:49817:
> Refused authentication
> *** Aborted at 1443557876 (unix time) try "date -d @1443557876" if you are
> using GNU date ***
> PC: @ 0x7fff8ad419a4 _pthread_mutex_check_init
> *** SIGSEGV (@0x1) received by PID 62883 (TID 0x114ad3000) stack trace: ***
> @ 0x7fff8d09f5aa _sigtramp
>
> I am sure ntp is the same since I have set the time with ntp and both the
> mesos master and jenkins are on the same machine.  The authentication
> process requires accurate clocks — since it is just the framework
> registering I have not looked at the slaves.
>
>
>
> Rinaldo
>
>
> On Sep 29, 2015, at 3:03 PM, Michael Park <mcyp...@gmail.com> wrote:
>
> Hi Rinaldo,
>
> Sorry that you're having trouble using dynamic reservations.
>
> I see that you're specifying the *mesos-mach5-beta* principal on the
> resources, but I'm not sure if your framework is registered with the
> *mesos-mach5-beta* principal? The framework must set the *
> FrameworkInfo::principal* to be registered under that *principal*.
>
> Please let me know whether that is the case or not, and I'll follow up
> with you to resolve the issue.
>
> Thanks,
>
> MPark.
>
> On Tue, Sep 29, 2015 at 1:53 PM DiGiorgio, Mr. Rinaldo S. <
> rdigior...@pace.edu> wrote:
>
>> Joseph,
>>
>>I thought I tried that.  So I must still not following the directions.
>> Here is what I have?
>>
>> mesos master running on OS X 10.10.5  mesos 0.26
>>
>> I perform the following curl operation below.
>>
>> server reads credentials file
>>
>> I0929 10:48:42.062871 291536896 credentials.hpp:37] Loading credentials
>> for authentication from '/etc/mesos-master/attributes/credentials'
>> I0929 10:48:42.065512 291536896 master.cpp:467] Using default 'crammd5'
>> authenticator
>>
>>
>>  The result of trying to reserve is:  *Could not authenticate
>> 'mesos-mach5-beta'*
>>
>> === the credentials file is ===
>>
>> {
>>   "credentials": [
>> {
>>   "principal": "*mesos-mach5-beta*",
>>   "secret": "*password*"
>> }
>>   ]
>> }
>> ===
>>
>> User curl post to reserve a slave not a framework
>>  =
>> SLAVE_ID="efb748eb-e1ce-423d-a795-7589c92b2a32-S1"
>> OPERATOR_PRINCIPAL="mach5"
>> CPUS="3"
>> MESOS_HOST="scaaa979.us.oracle.com:5050"
>> curl -u "*mesos-mach5-beta*:password" -d slaveId="$SLAVE_ID" -d @- -X
>> POST http://$MESOS_HOST/master/reserve <> resources=[
>> {
>>   "name": "cpus",
>>  "type": "SCALAR",
>>  "scalar": { "value": 8 },
>>  "role": "mach5",
>>  "reservation": {
>>"principal": "*mesos-mach5-beta*"
>>  }
>> },
>> {
>> "name": "mem",
>> "type": "SCALAR",
>> "scalar": { "value": 4096 },
>> "role": "mach5",
>> "reservation": {

Re: Reservations for multiple different agents

[Michael Park]

Hi Rinaldo,

Sorry that you're having trouble using dynamic reservations.

I see that you're specifying the *mesos-mach5-beta* principal on the
resources, but I'm not sure if your framework is registered with the
*mesos-mach5-beta* principal? The framework must set the
*FrameworkInfo::principal* to be registered under that *principal*.

Please let me know whether that is the case or not, and I'll follow up with
you to resolve the issue.

Thanks,

MPark.

On Tue, Sep 29, 2015 at 1:53 PM DiGiorgio, Mr. Rinaldo S. <
rdigior...@pace.edu> wrote:

> Joseph,
>
>I thought I tried that.  So I must still not following the directions.
> Here is what I have?
>
> mesos master running on OS X 10.10.5  mesos 0.26
>
> I perform the following curl operation below.
>
> server reads credentials file
>
> I0929 10:48:42.062871 291536896 credentials.hpp:37] Loading credentials
> for authentication from '/etc/mesos-master/attributes/credentials'
> I0929 10:48:42.065512 291536896 master.cpp:467] Using default 'crammd5'
> authenticator
>
>
>  The result of trying to reserve is:  *Could not authenticate
> 'mesos-mach5-beta'*
>
> === the credentials file is ===
>
> {
>   "credentials": [
> {
>   "principal": "*mesos-mach5-beta*",
>   "secret": "*password*"
> }
>   ]
> }
> ===
>
> User curl post to reserve a slave not a framework
>  =
> SLAVE_ID="efb748eb-e1ce-423d-a795-7589c92b2a32-S1"
> OPERATOR_PRINCIPAL="mach5"
> CPUS="3"
> MESOS_HOST="scaaa979.us.oracle.com:5050"
> curl -u "*mesos-mach5-beta*:password" -d slaveId="$SLAVE_ID" -d @- -X
> POST http://$MESOS_HOST/master/reserve < resources=[
> {
>   "name": "cpus",
>  "type": "SCALAR",
>  "scalar": { "value": 8 },
>  "role": "mach5",
>  "reservation": {
>"principal": "*mesos-mach5-beta*"
>  }
> },
> {
> "name": "mem",
> "type": "SCALAR",
> "scalar": { "value": 4096 },
> "role": "mach5",
> "reservation": {
> "principal": *"mesos-mach5-beta*"
> }
> }
> ]
> =
>
> On Sep 29, 2015, at 12:34 PM, Joseph Wu  wrote:
>
> Rinaldo,
>
> The principle is taken from authentication, rather than from the body of
> the resources.  In this case, you'll be using Basic Authentication:
> https://en.wikipedia.org/wiki/Basic_access_authentication#Client_side
>
> With curl, you'd add something like: -H "Authorization: Basic
> bWVzb3MtbWFjaDUtYmV0YTpwYXNzd29yZA=="
> That base64 blurb is the encoded version of "mesos-mach5-beta:password".
>
> ~Joseph
>
> On Mon, Sep 28, 2015 at 8:25 PM, DiGiorgio, Mr. Rinaldo S. <
> rdigior...@pace.edu> wrote:
>
>>
>> On Sep 28, 2015, at 8:03 PM, Joseph Wu  wrote:
>>
>> Hi Rinaldo,
>>
>> I'd like to point out a small error in your ACLs.
>>
>> If you want to specify "ANY", you should set the "type" field.  i.e. For
>> the RegisterFramework ACL:
>> "register_frameworks": [
>>   {
>> "principals": { "values": "mesos-mach5-beta" },
>> "roles": { "type": 1 }
>>   }
>> ]
>>
>>
>> Thanks — can’t keep my eyes open any more.  This is the response I get to
>> the following request.
>>
>> *Invalid RESERVE operation: Cannot reserve resources without a principal.
>>  *
>>
>> The example shows -u principal:password in curl which is an auentycation
>> string for the browser so I am totally confused on how to provide a
>> principal.   The documentation for the framework reserve
>>
>>
>>
>> curl -i  -d slaveId="$SLAVE_ID" -d @- -X POST
>> http://$MESOS_HOST/master/reserve <> resources=[
>> {
>>   "name": "cpus",
>>  "type": "SCALAR",
>>  "scalar": { "value": 8 },
>>  "role": "mach5",
>>  "reservation": {
>>"principal": "mach5"
>>  }
>> },
>> {
>> "name": "mem",
>> "type": "SCALAR",
>> "scalar": { "value": 4096 },
>> "role": "mach5",
>> "reservation": {
>> "principal": "mach5"
>> }
>> }
>> ]
>> <>
>>
>> The ANY "type" is part of an enumeration, defined here:
>>
>> https://github.com/apache/mesos/blob/master/include/mesos/authorizer/authorizer.proto#L33-L45
>>
>> Hope that helps,
>> ~Joseph
>>
>> On Mon, Sep 28, 2015 at 2:51 PM, DiGiorgio, Mr. Rinaldo S. <
>> rdigior...@pace.edu> wrote:
>>
>>>
>>> On Sep 28, 2015, at 5:27 PM, Marco Massenzio 
>>> wrote:
>>>
>>> Hi Rinaldo,
>>>
>>> sorry about the trouble you're having in getting this to work!
>>> If I got this one right, the original requirement was...
>>>
>>> I have some tasks that need to run on different types of agents.
>>>
>>>
>>> for that, I think you can use either (or both) of `roles` and
>>> `attributes` (see the Configuration doc [0] for more info).
>>>
>>> If you would like to run a 0.24 Mesos on your Mac for testing, you could
>>> use the Mesosphere published packages[1] or, if Vagrant is more your thing,
>>> feel free to "take inspiration" form [2].
>>>
>>> Marco,
>>>
>>>Thanks — We  are running 0.23, 0.24 and the current branch as of this
>>> 

Re: SSL in Mesos 0.23

[Michael Park]

Hi Dharmit,

I'm not certain whether the Mesosphere deb packages have SSL enabled or
not, although based on Craig's observation it looks like it is.

I think the correct way to enable SSL is to set the *SSL_ENABLED* environment
variable, rather than */etc/mesos-master/ssl_enabled*. Of course, along
with the rest of the *SSL_* environment variables.

e.g. SSL_ENABLED=true SSL_KEY_FILE=path-to-your-private-key
SSL_CERT_FILE=path-to-your-certificate ./mesos-master master-flags

MPark.

On Thu, Aug 6, 2015 at 9:30 AM craig w codecr...@gmail.com wrote:

 I've run ldd on /usr/sbin/mesos-master (on CentOS 7 using mesos 0.23 from
 mesosphere repo) and I see libssl.3.so and libssl.so.10

 On Thu, Aug 6, 2015 at 12:20 PM, Jeff Schroeder 
 jeffschroe...@computer.org wrote:

 Can you run ldd on the mesos-master or mesos-slave binaries? I believe
 you *should* see openssl libraries in the output if those packages are
 configured using --enable-ssl.

 On Thu, Aug 6, 2015 at 9:46 AM, Dharmit Shah shahdhar...@gmail.com
 wrote:

 Hello,

 I followed Mesos cluster setup guide on the Mesosphere website [1]. I
 set it up on a CentOS 7 system. For installation of packages, I went
 with Mesosphere provided repositories.

 Now that Mesos 0.23 has been released with SSL capabilities, I believe
 it is possible to have communication between the master, slaves and
 frameworks be secured by SSL. Am I right?

 I would like to set it up in my environment. I am using
 `mesos-0.23.0-1.0.centos701406.x86_64`.

 The official Mesos documentation on the topic [2] illustrates how
 things can be setup when building Mesos from source.

 I would like to know if Mesos package shipped by Mesosphere repo has
 this feature or not yet? I tried setting
 `/etc/mesos-master/ssl_enabled` on one of the master nodes. But
 restarting `mesos-master` service failed stating that option
 `ssl_enabled` is unknown.

 Thanks for your help!

 [1] http://open.mesosphere.com/getting-started/datacenter/install/
 [2] http://mesos.apache.org/documentation/latest/mesos-ssl/

 Regards,
 Dharmit.




 --
 Jeff Schroeder

 Don't drink and derive, alcohol and analysis don't mix.
 http://www.digitalprognosis.com




 --

 https://github.com/mindscratch
 https://www.google.com/+CraigWickesser
 https://twitter.com/mind_scratch
 https://twitter.com/craig_links

Re: Build 0.23 gcc Version

[Michael Park]

Hi John,

I would first suggest trying *CC=gcc CXX=g++ ../configure*, and if that
works, try to find out what *which* *cc* and *which* *c++* return and find
out what they symlink to.
I believe autotools uses *cc* and *c++* rather than *gcc* and *g++* by
default, so I think there's probably something funky going on there.

MPark.

On Fri, Jul 24, 2015 at 2:31 PM Benjamin Hindman benjamin.hind...@gmail.com
wrote:

 Hey John,

 It appears that we're finding gcc 4.6.3 on your machine. Is it possible
 that your autotools are hard coded to look for a gcc that is not the gcc
 that you've installed and is on your path?

 At least for me I use devtoolset-2 and Software Collections (scl) and I
 can get my machine into funky set ups where I've got a gcc 4.8 installed
 but using autotools it picks the wrong compiler.

 Ben.

 On Fri, Jul 24, 2015 at 2:02 PM John Omernik j...@omernik.com wrote:

 I am trying to build 0.23, I got the error below.  I already installed
 gcc-4.8 and set my alternatives to work with 4.8 as you can see gcc
 --version returns the right version, where is the configure script pulling
 that data? Are there flags I could use to help it through the process? :)

 John



 configure: error: GCC 4.8 or higher required (found 4.6.3)

 darkness@hadoopmapr1:/opt/mapr/mesos/mesos-0.23.0/build$ gcc --version

 gcc (Ubuntu 4.8.1-2ubuntu1~12.04) 4.8.1

 Copyright (C) 2013 Free Software Foundation, Inc.

 This is free software; see the source for copying conditions.  There is NO

 warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
 PURPOSE.

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

[Michael Park]

+1 (non-binding)

*make check* passes on:

   - Mac OS X 10.10.2 + clang 3.5.0
   - Ubuntu 14.04 + gcc 4.4.7
   - Ubuntu 14.04 + gcc 4.6.4
   - Ubuntu 14.04 + gcc 4.8.2


On 24 March 2015 at 01:01, Niklas Nielsen nik...@mesosphere.io wrote:

 I would like to steer this conversation/thread back to the release vote.
 Can you restart the distcc discussion in another thread?

 Cheers,
 Niklas

 On 23 March 2015 at 21:31, CCAAT cc...@tampabay.rr.com wrote:

 Excellent start! Nice links I was not aware of (thanks).
  Folks can use distcc now to test new rollouts of mesos?
 That was the quest of the thread was/is to establish some codes for
 testing new rollouts of mesos.

 It'll need to be 'extended' for cross compiling too for my needs.
 I'd like to follow up with anyone that get's distcc working with cross
 compiling for different arches. arm64 would be really cool. (LLVM?)

 My small cluster needs some work, much of it not related to mesos, but
 my efforts to run mesos and spark without the HDFS and use Cephfs, btrfs
 and supporting codes. So I'm not sure when I'll get this mesos-distcc
 installed and running in the near future; but I am most interested in
 follow the issues other encounter on compiling and cross compiling on a
 mesos cluster.

 What would be really cool is to run this distcc-mesos on top of spark
 and cephfs for some real fast compile times of large codes.


 Thanks,
 James


 On 03/23/2015 10:22 PM, Adam Bordelon wrote:

 I know it's over a year old and hasn't been updated, but bmahler already
 created a distcc framework example for Mesos.
 https://github.com/mesos/mesos-distcc

 On Mon, Mar 23, 2015 at 7:56 PM, CCAAT cc...@tampabay.rr.com
 mailto:cc...@tampabay.rr.com wrote:

 On 03/23/2015 09:02 PM, Adam Bordelon wrote:

 Integration tests are definitely desired/recommended. Some of us
 devs
 just do make [dist]check, but others test integrations with their
 favourite frameworks, or push it to their internal testing
 clusters.
 We're open to any additional testing you would like to propose
 and/or
 perform.

 Thanks,
 -Adam-


 Distcc is a distributed compiling program that has been a long
 staple on
 Gentoo linux and many other distros. I work on Gentoo and I think
 that
 setting up distcc to run on a mesos cluster is a fabulous idea. Not
 only
 can you compile native binaries for the inherent arch, but cross
 compiling should work too. Everyone has to recompile (optimized)
 kernels
 frequently with the release cycle of the linux kernel team. With the
 current roll out of all sorts of 64 bit arm systems, there's going
 to be
 a great opportunity to cross compile arm64 bit codes on CISC (X86_64)
 bit clusters.

 This also starts the process of heterogeneous mesos clusters, surely
 inevitable.

 https://code.google.com/p/__distcc/ https://code.google.com/p/
 distcc/

 https://code.google.com/p/__distcc/downloads/list
 https://code.google.com/p/distcc/downloads/list

 With LLvm, gnu and other projects, compiling and cross compiling on
 a mesos cluster is sure to be a very, very popoular idea. Any CI
 endeavor
 will necessitate lots of compiling too.

 hope this helps,
 James

Re: Is launchTasks() with multiple offers limited to a single slave?

[Michael Park]

Hi Itamar,

Wow, thanks for bringing this up!

The intended behavior is for *launchTasks* to take a set of tasks to be
launched on a *single *slave. This means that the multiple offers passed to
*launchTasks* must be from the *same *slave. The Python documentation
absolutely should state this explicitly as it does for acceptOffers
https://github.com/apache/mesos/blob/master/src/python/interface/src/mesos/interface/__init__.py#L204-L213
as
well as C++ *launchTasks
https://github.com/apache/mesos/blob/2985ae05634038b70f974bbfed6b52fe47231418/include/mesos/scheduler.hpp#L226-L237*.
If you would create a review request for this that would be awesome!

Now, if this *is* the intended behavior, it raises the question - why does
 launchTasks() support a set of tasks? doesn't mesos already aggregate
 resources from the same slave to a single offer?


The primary use case of this feature is to allow frameworks to hold onto
offers and use them in conjunction with other offers from the same slave
later on.

MPark.

On 19 March 2015 at 14:28, Sharma Podila spod...@netflix.com wrote:

 I will assume that you are not talking of the case that a task actually is
 being launched on multiple salves, since a task can only be launched on one
 slave with existing concepts.

 Yes, that call is for one or more tasks on a single slave. That call
 (since 0.18, I believe) also takes multiple offers of the same slave, which
 can happen due to tasks finishing at different times on the host.

 I have seen discussion on batching status updates/acks. But, not on
 batching launching of tasks across multiple slaves. From a user
 perspective, I'd imagine that this should be possible. It would be useful
 for frameworks with high rate of task dispatching.

 I suspect (purely my opinion) that this model may have come up in the
 beginning when most frameworks were scheduling one task at a time before
 moving to the next pending task. My framework, for example, runs a
 scheduling loop/iteration and comes up with schedules for multiple tasks
 across one more slaves. I would find it useful as well to batch up task
 launches across multiple hosts.

 That said, I haven't found the existing method to be limiting in
 performance/latency for our needs at this time.



 On Thu, Mar 19, 2015 at 8:19 AM, Itamar Ostricher ita...@yowza3d.com
 wrote:

 Hi,

 According to the Python interface docstring
 https://github.com/apache/mesos/blob/master/src/python/interface/src/mesos/interface/__init__.py#L184-L193,
 launchTasks() may be called with a set of tasks.

 In our framework, we thought this is used to issue a single RPC for
 launching many tasks onto many offers (potentially from many slaves), as an
 optimization (e.g., less communication overhead).

 But, when running with multiple slaves, we saw that tasks are lost when
 they are assigned to different slaves with the same launchTasks() call.

 Reading the docstring of launchTasks carefully, I still couldn't figure
 out that this is the intended behavior, so I'm here to verify that.
 If that's by design, it should be stated clearly in the docstring (I'd be
 happy to provide a documentation pull request for this).

 Now, if this *is* the intended behavior, it raises the question - why
 does launchTasks() support a set of tasks? doesn't mesos already aggregate
 resources from the same slave to a single offer?

 Thanks,
 - Itamar.

Re: Who is the user in Mesos Authorization ACL definition?

[Michael Park]

On 9 March 2015 at 07:36, Sivaram Kannan sivara...@gmail.com wrote:


 Hi,

 I apologize for bombarding with so many emails on the same issue. So, I
 modified the acl.json as below.

 1. I was able to launch the framework with authentication as users devel1
 and devel2.


Just so that our terminologies match here, you were able to *register*
 frameworks *authenticated* as *principals* *devel1* and *devel2.*

Your ACL specifies *devel1* and *devel2* can register under *apps* and
*dev-ops* roles, so as long as the frameworks registered under those roles,
the success here makes sense.


 2. I was able to launch a task as user devel1


I agree with Vinod that maybe the point of confusion is regarding *principal
*vs *user* for *run_tasks*. To reiterate, *principal* is essentially a
username for Mesos to authenticate the framework, and *user* is the unix
user under which the task will run. Your ACL specifies that *principal*
*devel1* can launch tasks as *user* *root*. So you shouldn't be able to
launch a task as user *devel1*, but rather launch a task as user* root* with
the framework registered as principal=*devel1*. If this is not the case,
something's wrong.


 3. I get TASK_LOST when I try to launch task with the framework registered
 as devel2.


This is correct. Vinod already covered this point. In short, framework
registered as *devel2* is not permitted to run anything based on your ACL
since none of the specified cases match and permissive is set to false.


 4. In the same config, if I change the run_tasks = users to devel, the
 task fails with the error described in the previous email. As far as I
 understand, an error in run_tasks users, does not give TASK_LOST, but a
 TASK_FAILED.


I'm not sure what you mean by an error in run_tasks users. The error you
get in this case is because you don't have a *devel* user available in the
environment you're launching the task. The relevant line in the error
message that illustrate this is:

Mar 06 06:06:03 node-0800279564ad sh[27684]: E0306 06:06:03.89847313
 slave.cpp:2787] Container '9835da8c-a844-4d53-a7f7-4a5e6e808a9b' for
 executor 'busybox.d4ef22c6-c3c6-11e4-a31a-56847afe9799' of framework
 '20150306-054714-24707342-5050-1-' failed to start: Failed to create
 container: Failed to chown: *Failed to get user information for 'devel'*:
 Success


This is indeed a *TASK_FAILED*, since authorization succeeded, but the task
failed to launch.


 But a mismatch in principals between register_frameworks and run_tasks
 gives a TASK_LOST.


It's not clear exactly what you mean by a *mismatch* in principals between
register_frameworks and run_tasks. If you mean that all principals under
register_frameworks should have a matching portion in run_tasks, that's not
quite correct. For example, you modified the ACL to be:

{
 permissive: false,
 register_frameworks: [
 {
 principals: { values: [ devel1, devel2 ] },
 roles: { values: [ apps, dev-ops ] }
 },
 {
 principals: { type: NONE },
 roles: { values: [ apps, dev-ops ] }
 }
 ],
 run_tasks: [
 {
 principals: { values: [ devel1, *devel2* ] },
 users: { values: [ root ] }
 },

{
 principals: { values: [ marathon ] },
 users: { type: NONE }
 }
 ]
 }


If we attempt to launch a task as user mpark with the framework
registered as devel2 (or devel1), we'll get continue to get the
*TASK_LOST* message because it fails at the *authorization* phase.


 Does the above makes sense? Please correct me if I am wrong.


I hope my explanation above made sense!



 permissive: false,
 register_frameworks: [
 {
 principals: { values: [ devel1, devel2 ] },
 roles: { values: [ apps, dev-ops ] }
 },
 {
 principals: { type: NONE },
 roles: { values: [ apps, dev-ops ] }
 }
 ],
 run_tasks: [
 {
 principals: { values: [ devel1 ] },
 users: { values: [ root ] }
 },
 {
 principals: { values: [ marathon ] },
 users: { type: NONE } } ]
 }

 Thanks,
 ./Siva.


Thanks,

MPark.


 On Mon, Mar 9, 2015 at 3:57 PM, Sivaram Kannan sivara...@gmail.com
 wrote:


 Hi Vinod,

 The users in below run_tasks definition - does it refer to unix users in
 the machine where the framework is run or the unix users in the mesos-slave
 machine. I think the fact that I run all softwares (mesos-master,
 mesos-slave, marathon) as docker containers is of significance and reason
 for the below failure.

 run_tasks: [
 {
 principals: {
 values: [
 marathon
 ]
 },
 users: {
 values: [
 devel
 ]
 }
 },
 {
 principals: {
 values: