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

2018-09-14 Thread Kapil Arya
+1 (binding).

Internal CI succeeded. The binary deb/rpm packages for this RC can be found
here:
http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.7.0-rc3

On Fri, Sep 14, 2018 at 4:18 AM Alex Rukletsov  wrote:

> +1 (binding)
>
> Mesosphere's internal CI run with the aforementioned tag. Observed 4 flaky
> tests, 3 are known:
> https://issues.apache.org/jira/browse/MESOS-5048
> https://issues.apache.org/jira/browse/MESOS-8260
> https://issues.apache.org/jira/browse/MESOS-8951
>
> One has been introduced as part of adding GC to nested containers
> (MESOS-7947), which is disabled in the release:
> https://issues.apache.org/jira/browse/MESOS-9217
>
>
> On Tue, Sep 11, 2018 at 8:09 PM, Gastón Kleiman 
> wrote:
>
>> Hi all,
>>
>> Please vote on releasing the following candidate as Apache Mesos 1.7.0.
>>
>>
>> 1.7.0 includes the following:
>>
>> 
>> * Performance Improvements:
>>   * Master `/state` endpoint: ~130% throughput improvement through
>> RapidJSON
>>   * Allocator: Improved allocator cycle significantly
>>   * Agent `/containers` endpoint: Fixed a performance issue
>>   * Agent container launch / destroy throughput is significantly improved
>> * Containerization:
>>   * **Experimental** Supported docker image tarball fetching from HDFS
>>   * Added new `cgroups/all` and `linux/devices` isolators
>>   * Added metrics for `network/cni` isolator and docker pull latency
>> * Windows:
>>   * Added support to libprocess for the Windows Thread Pool API
>> * Multi-Framework Workloads:
>>   * **Experimental** Added per-framework metrics to the master
>>   * A new weighted random sorter was added as an alternative to the DRF
>> sorter
>>
>> The CHANGELOG for the release is available at:
>>
>> https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.7.0-rc3
>>
>> 
>>
>> The candidate for Mesos 1.7.0 release is available at:
>> https://dist.apache.org/repos/dist/dev/mesos/1.7.0-rc3/mesos-1.7.0.tar.gz
>>
>> The tag to be voted on is 1.7.0-rc3:
>> https://gitbox.apache.org/repos/asf?p=mesos.git;a=commit;h=1.7.0-rc3
>>
>> The SHA512 checksum of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/1.7.0-rc3/mesos-1.7.0.tar.gz.sha512
>>
>> The signature of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/1.7.0-rc3/mesos-1.7.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 in a staging repository here:
>> https://repository.apache.org/content/repositories/orgapachemesos-1234
>>
>> Please vote on releasing this package as Apache Mesos 1.7.0!
>>
>> The vote is open until Fri Sep 14 11:06:30 PDT 2018 and passes if a
>> majority of at least 3 +1 PMC votes are cast.
>>
>> [ ] +1 Release this package as Apache Mesos 1.7.0
>> [ ] -1 Do not release this package because ...
>>
>> Thanks,
>>
>> Chun-Hung & Gastón
>>
>
>


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

2018-08-20 Thread Kapil Arya
Hi all,

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

+1 (Binding)
--
*** Ben Mahler
*** Kapil Arya
*** Alex Ruklestov

There were no 0 or -1 votes.

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

The mesos-1.4.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,
Anand and Kapil


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

2018-08-20 Thread Kapil Arya
+1 binding (internal CI).

The Apache CI failures reported by Vinod are all known flaky tests. I have
inserted the details inline.

Best,
Kapil

On Tue, Aug 14, 2018 at 11:03 AM Vinod Kone  wrote:

> I see some flaky tests in ASF CI, that I don't see already reported.
>
> @Kapil Arya   Can you take a look at
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/53 and see
> if the flaky tests are due to bugs in test code and not source?
>
> *Revision*: 612ec2c63a68b4d5b60d1d864e6703fde1c2a023
>
>- refs/tags/1.4.2-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/53/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)/
> >
>

Failed due to the timeout being too short -- leveldb took 11 seconds to
responds while the timeout expired at 10 seconds. It also looks like the
previous operation also took longer than expected potentially due to some
machine load at the time.

E0814 00:51:13.001557  8738 registrar.cpp:575] Registrar aborting:
Failed to update registry: Failed to perform store within 10secs
../../src/tests/registrar_tests.cpp:331: Failure
(registrar.apply( Owned( new MarkSlaveUnreachable(info1,
protobuf::getCurrentTime().failure(): Failed to update registry:
Failed to perform store within 10secs
I0814 00:51:18.990106  8743 leveldb.cpp:341] Persisting action (218
bytes) to leveldb took 11.656345772secs


ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools
> [image: Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/53/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/53/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)/
> >
>

> --verbose autotools

[image: Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/53/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)/
> >
>

Failures because of known double-free corruption in test code due to
parallel manipulation of signal and control handler:
https://issues.apache.org/jira/browse/MESOS-8084



> cmake
> [image: Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/53/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)/
> >
>

Failure due to known flaky: https://issues.apache.org/jira/browse/MESOS-7028

On Mon, Aug 13, 2018 at 7:41 PM Benjamin Mahler  wrote:

>
> > +1 (binding)
> >
> > make check passes on macOS 10.13.6 with Apple LLVM version 9.1.0
> > (clang-902.0.39.2).
> >
> > Thanks Kapil!
> >
> > On Wed, Aug 8, 2018 at 3:06 PM, Kapil Arya  wrote:
> >
> > > Hi all,
> > >
> > > Please vote on releasing the following candidate as Apache Mesos 1.4.2.
> > >
> > > 1.4.2 is a bug fix release. The CHANGELOG for the release is available
> > at:
> > > https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_
> > > plain;f=CHANGELOG;hb=1.4.2-rc1
> > >
> > > The candidate for Mesos 1.4.2 release is available at:
> > >
> >
> https://dist.apache.org/repos/dist/dev/mesos/1.4.2-rc1/mesos-1.4.2.tar.gz
> > >
> > > The tag to be voted on is 1.4.2-rc1:
> > > https://gitbox.apache.org/repos/asf?p=mesos.git;a=commit;h=1.4.2-rc1
> > >
> > > The SHA512 checksum of the tarball can be found at:
> > > https://dist.apache.org/repos/dist/dev/mesos/1.4.2-rc1/
> > > mesos-1.4.2.tar.gz.sha512
> > >
> > > The signature of the tarball can be found at:
> > > https://dist.apache.org/repos/dist/dev/mesos/1.4.2-rc1/
> > > mesos-1.4.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 in a staging repository here:
> > > https://repository.apache.org/content/repositories/orgapachemesos-1231
> > >
> > > Please vote on releasing this package as Apache Mesos 1.4.2!
> > >
> > > The vote is open until Sat Aug 11 11:59:59 PDT 2018 and passes if a
> > > majority of at least 3 +1 PMC votes are cast.
> > >
> > > [ ] +1 Release this package as Apache Mesos 1.4.2
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thanks,
> > > Anand and Kapil
> > >
> >
>


[VOTE] Release Apache Mesos 1.4.2 (rc1)

2018-08-08 Thread Kapil Arya
Hi all,

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

1.4.2 is a bug fix release. The CHANGELOG for the release is available at:
https://gitbox.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.4.2-rc1

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

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

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

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.2-rc1/mesos-1.4.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 in a staging repository here:
https://repository.apache.org/content/repositories/orgapachemesos-1231

Please vote on releasing this package as Apache Mesos 1.4.2!

The vote is open until Sat Aug 11 11:59:59 PDT 2018 and passes if a
majority of at least 3 +1 PMC votes are cast.

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

Thanks,
Anand and Kapil


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

2018-05-11 Thread Kapil Arya
I don’t remember seeing a major release with just one RC — good job, Greg!
:)

On Fri, May 11, 2018 at 6:12 PM Greg Mann  wrote:

> Hi all,
>
> The vote for Mesos 1.6.0 (rc1) has passed with the
> following votes.
>
> +1 (Binding)
> --
> Vinod Kone
> Chun-Hung Hsiao
> James Peach
> Zhitao Li
> Andrew Schwartzmeyer
>
>
> There were no 0 or -1 votes.
>
> Please find the release at:
> https://dist.apache.org/repos/dist/release/mesos/1.6.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.6.0
>
> The mesos-1.6.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!
> Greg
>


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

2017-11-15 Thread Kapil Arya
Hi all,

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

+1 (Binding)
--
*** Vinod Kone
*** Kapil Arya
*** Anand Mazumdar

There were no 0 or -1 votes.

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

The mesos-1.4.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,
Anand and Kapil


Re: .deb packages of mesos releases

2017-11-14 Thread Kapil Arya
On Tue, Nov 14, 2017 at 6:05 PM, Adam Cécile <adam.cec...@hitec.lu> wrote:

> Hi,
>
> It's usually considered as being a bad practise to put the Debian
> packaging itself into the upstream tree because it conflicts with the
> "real" packaging if it gets uploaded to Debian.
> But that's probably something we can figure out easily (maybe use another
> folder name and add hacky step in CI renaming the folder to Debian).
>

I'm not sure if I understand this. I used to maintain a debian package that
was uploaded to debian/ubuntu official repos and there we just kept a
`debian` folder inside the source tree (https://github.com/dmtcp/dmtcp).
With every upstream release, we updated the debian packaging to reflect an
updated version, etc. and that seemed to work fine. However, that was a
simpler package to maintain compared to Mesos, so I can imagine concerns
around that :).


> How would you do that ? Do you have workers running Debian/Ubuntu ? It's
> quite easy to create the package for any target (including foreign
> architectures, thanks to QEmu userland binary wrapper) but I don't think it
> can be done from a RHEL-based worker.
>
> Yeah, the ASF CI has Ubuntu workers that should work. However, to ensure a
sane environment, I would recommend using Debian/Ubuntu containers just
like we do for the CentOS builds. That way we can test/run it locally to
debug any issues and so on. Does that sound reasonable?



> Regards, Adam.
>
>
> On 11/14/2017 11:56 PM, Kapil Arya wrote:
>
> Hi Adam,
>
> I am wondering if you would have some time to bring your debian packaging
> into Mesos source tree. We can then use the ASF Jenkins CI to build and
> publish packages to bintray just like we started doing for CentOS 6/7? This
> will also allow the community to more actively participate in maintaining
> it in future.
>
> Best,
> Kapil
>
> On Wed, Sep 13, 2017 at 2:08 PM, Adam Cécile <adam.cec...@hitec.lu> wrote:
>
>> In case someone's interrested in, I added 1.1.3 debs on my repository:
>>
>> https://packages.le-vert.net/mesos/
>>
>>
>> On 09/09/2017 06:40 PM, Adam Cecile wrote:
>>
>> Hey,
>>
>> Well that's not really a problem, I can provide 1.1.x packages if your
>> interested in.
>>
>> Regards, Adam.
>>
>> On September 8, 2017 10:47:23 AM GMT+02:00, Tomek Janiszewski
>> <jani...@gmail.com> <jani...@gmail.com> wrote:
>>>
>>> @Adam Thanks for taking care of this. There is one problem, Mesos 1.1.3
>>> is missing in provided repository.
>>>
>>> @Kapil What is the status of official Apache Mesos packages? At Mesos
>>> Developer Community Meeting (Jan 26, 2017) you presented a proposal for
>>> this: https://youtu.be/m7WzKia68Rg
>>>
>>> wt., 5 wrz 2017 o 15:31 użytkownik Adam Cecile <adam.cec...@hitec.lu>
>>> napisał:
>>>
>>>> On 09/05/2017 11:55 AM, Oskar Jagodziński wrote:
>>>> > Hi all,
>>>> >
>>>> > What is standard interval between release of mesos package and
>>>> > 'official' .deb build by Mesosphere? Mesos 1.1.3 was released 11 days
>>>> > ago and there is no package at
>>>> > https://open.mesosphere.com/downloads/mesos/ only rc-packages
>>>> > https://open.mesosphere.com/downloads/mesos-rc/ are up to date.
>>>> >
>>>> Hello,
>>>>
>>>>
>>>> First, I like to make an important statement:
>>>>
>>>> *I'm not an official mesosphere guy*
>>>>
>>>> That being said, Mesosphere package are binary copy of CentOS built file
>>>> into a deb container. That's not what I call a Debian package at all and
>>>> I already had severe issue with that (libcurl-nss backed built which
>>>> does not support https on Debian-based system).
>>>>
>>>> For this reason, I create my own Mesos package, as a REAL debian
>>>> package, built from sources in a clean environment using pbuilder. I
>>>> also provide armhf and arm64 build because I've plan for that ;-)
>>>>
>>>> These package are in-use at three customers place and work just fine. I
>>>> provide multiple branches packages and build them with additional
>>>> network isolator using libnl and XFS disk isolator.
>>>>
>>>>
>>>> It's available there:
>>>>
>>>> https://packages.le-vert.net/mesos/
>>>>
>>>> Feel free to do what the f*** you want, use the repository directly,
>>>> sync it, rebuild debs from sources packages...
>>>>
>>>>
>>>> Regards, Adam.
>>>>
>>>>
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>
>>
>>
>
>


Re: .deb packages of mesos releases

2017-11-14 Thread Kapil Arya
Hi Adam,

I am wondering if you would have some time to bring your debian packaging
into Mesos source tree. We can then use the ASF Jenkins CI to build and
publish packages to bintray just like we started doing for CentOS 6/7? This
will also allow the community to more actively participate in maintaining
it in future.

Best,
Kapil

On Wed, Sep 13, 2017 at 2:08 PM, Adam Cécile  wrote:

> In case someone's interrested in, I added 1.1.3 debs on my repository:
>
> https://packages.le-vert.net/mesos/
>
>
> On 09/09/2017 06:40 PM, Adam Cecile wrote:
>
> Hey,
>
> Well that's not really a problem, I can provide 1.1.x packages if your
> interested in.
>
> Regards, Adam.
>
> On September 8, 2017 10:47:23 AM GMT+02:00, Tomek Janiszewski
>   wrote:
>>
>> @Adam Thanks for taking care of this. There is one problem, Mesos 1.1.3
>> is missing in provided repository.
>>
>> @Kapil What is the status of official Apache Mesos packages? At Mesos
>> Developer Community Meeting (Jan 26, 2017) you presented a proposal for
>> this: https://youtu.be/m7WzKia68Rg
>>
>> wt., 5 wrz 2017 o 15:31 użytkownik Adam Cecile 
>> napisał:
>>
>>> On 09/05/2017 11:55 AM, Oskar Jagodziński wrote:
>>> > Hi all,
>>> >
>>> > What is standard interval between release of mesos package and
>>> > 'official' .deb build by Mesosphere? Mesos 1.1.3 was released 11 days
>>> > ago and there is no package at
>>> > https://open.mesosphere.com/downloads/mesos/ only rc-packages
>>> > https://open.mesosphere.com/downloads/mesos-rc/ are up to date.
>>> >
>>> Hello,
>>>
>>>
>>> First, I like to make an important statement:
>>>
>>> *I'm not an official mesosphere guy*
>>>
>>> That being said, Mesosphere package are binary copy of CentOS built file
>>> into a deb container. That's not what I call a Debian package at all and
>>> I already had severe issue with that (libcurl-nss backed built which
>>> does not support https on Debian-based system).
>>>
>>> For this reason, I create my own Mesos package, as a REAL debian
>>> package, built from sources in a clean environment using pbuilder. I
>>> also provide armhf and arm64 build because I've plan for that ;-)
>>>
>>> These package are in-use at three customers place and work just fine. I
>>> provide multiple branches packages and build them with additional
>>> network isolator using libnl and XFS disk isolator.
>>>
>>>
>>> It's available there:
>>>
>>> https://packages.le-vert.net/mesos/
>>>
>>> Feel free to do what the f*** you want, use the repository directly,
>>> sync it, rebuild debs from sources packages...
>>>
>>>
>>> Regards, Adam.
>>>
>>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
>
>


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

2017-11-14 Thread Kapil Arya
+1 (binding)

Mesosphere-internal CI with CentOS 6/7, Debian 8, Fedora 23, and Ubuntu
1[467].04.

On Mon, Nov 13, 2017 at 7:14 PM, Vinod Kone <vinodk...@apache.org> wrote:

> +1 (binding)
>
> Tested on ASF CI. Couple red failure builds were due to known flaky tests,
> one of which is already resolved on master.
>
>
> *Revision*: c844db9ac7c0cef59be87438c6781bfb71adcc42
>
>- refs/tags/1.4.1-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/43/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/43/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/43/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/43/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/43/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/43/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/43/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/43/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/43/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/43/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/43/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/43/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, Nov 9, 2017 at 6:27 PM, Kapil Arya <ka...@mesosphere.io> wrote:
>
> > Hi all,
> >
> > Please vote on releasing the following candidate as Apache Mesos 1.4.1.
> >
> > 1.4.1 includes the follow

[VOTE] Release Apache Mesos 1.4.1 (rc1)

2017-11-09 Thread Kapil Arya
Hi all,

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

1.4.1 includes the following:

* [MESOS-7873] - Expose `ExecutorInfo.ContainerInfo.NetworkInfo` in Mesos
`state` endpoint.
* [MESOS-7921] - ProcessManager::resume sometimes crashes accessing
EventQueue.
* [MESOS-7964] - Heavy-duty GC makes the agent unresponsive.

* [MESOS-7968] - Handle `/proc/self/ns/pid_for_children` when parsing
available namespace.
* [MESOS-7969] - Handle cgroups v2 hierarchy when parsing
/proc/self/cgroups.
* [MESOS-7980] - Stout fails to compile with libc >= 2.26.

* [MESOS-8051] - Killing TASK_GROUP fail to kill some tasks.

* [MESOS-8080] - The default executor does not propagate missing task exit
status correctly.
* [MESOS-8090] - Mesos 1.4.0 crashes with 1.3.x agent with oversubscription

* [MESOS-8135] - Masters can lose track of tasks' executor IDs.

* [MESOS-8169] - Incorrect master validation forces executor IDs to be
globally unique.


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


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

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

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

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.1-rc1/mesos-1.4.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 in a staging repository here:
https://repository.apache.org/content/repositories/orgapachemesos-1216

Please vote on releasing this package as Apache Mesos 1.4.1!

The vote is open until Monday, November 13, 2017, 11:59 PM EST and passes
if a majority of at least 3 +1 PMC votes are cast.

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

Thanks,
Anand and Kapil


Re: Binary RPM packages for CentOS

2017-11-09 Thread Kapil Arya
Hi Marc,

I'm not sure if I understand the concern. Looks like you are using the
mesosphere repository. The mesos-zookeeper package is no longer
supported/maintained.

The packages mentioned my previous email are published on bintray are not
maintained by mesosphere. Please let us know if you have any feedback on
the new packages.

Best,
Kapil

On Sat, Nov 4, 2017 at 6:54 AM, Marc Roos <m.r...@f1-outsourcing.eu> wrote:

>
> I am testing a bit with mesos and using this repository
> http://repos.mesosphere.io/el/7/$basearch/ is that the correct one to
> use? (mesos-zookeeper from 2015?)
>
> If so, maybe you could allow rsync access? I am testing on some vm's
> that don’t have internet access.
>
> Also add maybe index listing on such pages
> http://repos.mesosphere.com/el/7/noarch/RPMS/
>
>
>
>
>
>
>
>
>
> -Original Message-
> From: Vinod Kone [mailto:vinodk...@apache.org]
> Sent: vrijdag 3 november 2017 20:49
> To: dev
> Cc: user
> Subject: Re: Binary RPM packages for CentOS
>
> This is great to see! Thanks for driving this Kapil.
>
> Once the official packages are vetted, we should update our website to
> point users to it. For new users, getting started with binary packages
> is infinitely better than having to build from source.
>
> Folks, please help us by testing this packages and provide feedback.
>
> On Fri, Nov 3, 2017 at 10:32 AM, Kapil Arya <ka...@mesosphere.io> wrote:
>
>
> Hi All,
>
> We have some updates regarding the binary RPM build/release process
> for
> Mesos.
>
> Here are some important bullet points:
>
> * Jira: https://issues.apache.org/jira/browse/MESOS-7981
> <https://issues.apache.org/jira/browse/MESOS-7981>
> * The RPM packages are now built using a jenkins job [1] on the
> Apache CI.
> * The build scripts are part of the Mesos source tree
> (support/packaging).
> * Packages are distributed using bintray [2].
> * Currently, we are using the mesos org under bintray. Once we have
> more
>   confidence in the packages, we'll move under the apache org to
> benefit
> from
>   the superior resource limits.
>
> Here are the steps to install the CentOS 7 packages from bintray:
>
> *$* cat > /tmp/bintray-mesos-el.repo < #bintray-mesos-el - packages by mesos from Bintray
> [bintray-mesos-el]
> name=bintray-mesos-el
> baseurl=https://dl.bintray.com/mesos/el/7/x86_64
> <https://dl.bintray.com/mesos/el/7/x86_64>
> gpgcheck=0
> repo_gpgcheck=0
> enabled=1
> EOF
>
> *$* sudo mv /tmp/bintray-mesos-el.repo
> /etc/yum.repos.d/bintray-mesos-el.repo
>
> *$* sudo yum update
>
> *$* sudo yum install mesos
>
>
> To start, we have released 1.4.0 packages in the hope to get some
> feedback
> from
> the community before releasing rpms for other supported version.
>
> Future work:
> * Release RC packages in bintray.com/mesos/el-testing repo.
> * Release (rotating) nightly builds in
> bintray.com/mesos/el-unstable repo.
> * Create/release debian/ubuntu packages with the help from
> community
> members who
>   are already publishing such packages.
>
> Best,
> Kapil
>
> [1]:
> https://builds.apache.org/job/Mesos/job/Packaging/job/CentosRPMs
> <https://builds.apache.org/job/Mesos/job/Packaging/job/CentosRPMs>
> [2]: https://bintray.com/mesos/
>
>
>
>
>


Binary RPM packages for CentOS

2017-11-03 Thread Kapil Arya
Hi All,

We have some updates regarding the binary RPM build/release process for
Mesos.

Here are some important bullet points:

* Jira: https://issues.apache.org/jira/browse/MESOS-7981
* The RPM packages are now built using a jenkins job [1] on the Apache CI.
* The build scripts are part of the Mesos source tree (support/packaging).
* Packages are distributed using bintray [2].
* Currently, we are using the mesos org under bintray. Once we have more
  confidence in the packages, we'll move under the apache org to benefit
from
  the superior resource limits.

Here are the steps to install the CentOS 7 packages from bintray:

*$* cat > /tmp/bintray-mesos-el.repo 

1.4.1 release

2017-11-02 Thread Kapil Arya
Please reply to this email if you have pending patches to be backported to
1.4.x as we are aiming to cut a release candidate for 1.4.1 early next week.

Thanks,
Anand and Kapil


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

2017-09-18 Thread Kapil Arya
Hi all,

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

+1 (Binding)
--
Vinod Kone
Kapil arya
Anand Mazumdar

There were no 0 or -1 votes.

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

The mesos-1.4.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,
Anand and Kapil


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

2017-09-15 Thread Kapil Arya
p=(docker%
>>> 7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
>>> --verbose autotools
>>> [image: Success]
>>> <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Rel
>>> ease/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-Rel
>>> ease/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-Rel
>>> ease/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-Rel
>>> ease/42/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--
>>> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A1
>>> 4.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
>>>
>>>
>>>
>>>
>>>
>>> On Sat, Sep 9, 2017 at 6:49 AM, Kapil Arya <ka...@mesosphere.io> 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 candidate using the Maven staging repository provided below.]
>>> >
>>> > 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_p
>>> > lain;f=CHANGELOG;hb=1.4.0-rc5
>>> > 
>>> 
>>> >
>>> >
>>> > The candidate for Mesos 1.4.0 release is available at:
>>> > https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc5/mesos
>>> -1.4.0.tar.gz
>>> >
>>> > The tag to be voted on is 1.4.0-rc5:
>>> > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit
>>> ;h=1.4.0-rc5
>>> >
>>> > The MD5 checksum of the tarball can be found at:
>>> > https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc5/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-rc5/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-1215
>>> >
>>> > Please vote on releasing this package as Apache Mesos 1.4.0!
>>> >
>>> > The vote is open until Wed Sep 13 11:59:00 PM EDT 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
>>> >
>>>
>>
>


[VOTE] Release Apache Mesos 1.4.0 (rc5)

2017-09-09 Thread Kapil Arya
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 candidate using the Maven staging repository provided below.]

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



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

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

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc5/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-rc5/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-1215

Please vote on releasing this package as Apache Mesos 1.4.0!

The vote is open until Wed Sep 13 11:59:00 PM EDT 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


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

2017-09-07 Thread Kapil Arya
Looks like an important patch (https://reviews.apache.org/r/62053/) is
missing from this RC and so we're canceling the vote. We will
publish another RC shortly.

Sorry for the inconvenience.

Best,
Anand and Kapil

On Thu, Sep 7, 2017 at 1:57 PM, Kapil Arya <ka...@mesosphere.io> 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-rc4
> 
>
>
> The candidate for Mesos 1.4.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc4/mesos-1.4.0.tar.gz
>
> The tag to be voted on is 1.4.0-rc4:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.4.0-rc4
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc4/
> 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-rc4/
> 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-1214
>
> Please vote on releasing this package as Apache Mesos 1.4.0!
>
> The vote is open until Mon Sep 11 11:59:00 PM EDT 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
>


[VOTE] Release Apache Mesos 1.4.0 (rc4)

2017-09-07 Thread Kapil Arya
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-rc4



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

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

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc4/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-rc4/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-1214

Please vote on releasing this package as Apache Mesos 1.4.0!

The vote is open until Mon Sep 11 11:59:00 PM EDT 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


[VOTE] Release Apache Mesos 1.4.0 (rc3)

2017-08-28 Thread Kapil Arya
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


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

2017-08-28 Thread Kapil Arya
Hi All,

Due to a discrepancy in the CHANGELOG, we are retracting this release
candidate and will put out a new release candidate for voting in a little
while.

Best,
Anand and Kapil

On Mon, Aug 28, 2017 at 12:44 PM, Kapil Arya <ka...@mesosphere.io> 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-rc2
> 
>
>
> The candidate for Mesos 1.4.0 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc2/mesos-1.4.0.tar.gz
>
> The tag to be voted on is 1.4.0-rc2:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.4.0-rc2
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc2/
> 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-rc2/
> 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-1210
>
> Please vote on releasing this package as Apache Mesos 1.4.0!
>
> The vote is open until Thursday, Aug 31 11:59 AM 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
>


[VOTE] Release Apache Mesos 1.4.0 (rc2)

2017-08-28 Thread Kapil Arya
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-rc2



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

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

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc2/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-rc2/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-1210

Please vote on releasing this package as Apache Mesos 1.4.0!

The vote is open until Thursday, Aug 31 11:59 AM 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


[VOTE] Release Apache Mesos 1.4.0 (rc1)

2017-08-18 Thread Kapil Arya
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.
  * 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-rc1



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

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

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/1.4.0-rc1/
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-rc1/
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-1206

Please vote on releasing this package as Apache Mesos 1.4.0!

The vote is open until Wed. Aug 23, 2017 11:59:59 PM PDT, 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


Re: Mesos 1.4.0

2017-08-11 Thread Kapil Arya
1.4.0 Update

We currently have 5 blockers, 4 critical, and 4 major issues.

To ramp up the process, we are cutting the 1.4.x branch today to allow
master to continue without affecting the 1.4.0 release. Please contact the
1.4.0 release managers for getting your changes cherry-picked from master
into the 1.4.x branch.

Best,
Anand and Kapil

On Thu, Jul 27, 2017 at 3:30 PM, Anand Mazumdar  wrote:

> Hello everyone,
>
> It's about time for Mesos 1.4.0 (somewhat late though, 1.3 rc1 was cut on
> 5/5) . Kapil would be the primary release manager and I would be the
> co-release manager.
>
> We expect to cut rc1 in the coming couple of weeks. Here's how you can
> help:
> - Set *Target Version = "1.4.0"* for anything that needs to go into this
> release. Anything not critical can wait for Mesos 1.5.
> - Upgrade release blockers to *"Blocker" priority*. Use "Critical" for
> any issues that would be painful (but possible) to ship Mesos 1.4 without.
>
> Mesos 1.4 release dashboard: https://issues.apache.org/jira/secure/
> Dashboard.jspa?selectPageId=12331513
>
> -anand
>


[RFC] File-based secrets

2017-04-24 Thread Kapil Arya
Hi All,

Recently, we started working on providing file-based secrets for Mesos
tasks (MESOS-7418 ). The
goal is to allow users to populate files within a task's environment with
contents fetched from a backend secret store. A new secret fetching module
interface is proposed to allow interaction with arbitrary third-party
secret stores.

Further details are covered in the following design doc:

https://docs.google.com/document/d/18raiiUfxTh-JBvjd6RyHe_TOScY87G_bMi5zBzMZmpc/

There might be a few minor pieces missing, but most of the design is there
and should answer most concerns. Please do raise an issue if you find
something missing. As always, any feedback is most welcome.

Best,
Kapil


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

2017-02-08 Thread Kapil Arya
+1 binding.

Internal CI to build deb/rpm packages.

The deb/rpm binary packages are available at:
http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.1.1-rc1


On Tue, Feb 7, 2017 at 5:39 PM, Alex R  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.1.1.
>
> 1.1.1 includes the following:
> 
> 
> ** Bug
>   * [MESOS-6002] - The whiteout file cannot be removed correctly using
> aufs backend.
>   * [MESOS-6010] - Docker registry puller shows decode error "No response
> decoded".
>   * [MESOS-6142] - Frameworks may RESERVE for an arbitrary role.
>   * [MESOS-6360] - The handling of whiteout files in provisioner is not
> correct.
>   * [MESOS-6411] - Add documentation for CNI port-mapper plugin.
>   * [MESOS-6526] - `mesos-containerizer launch --environment` exposes
> executor env vars in `ps`.
>   * [MESOS-6571] - Add "--task" flag to mesos-execute.
>   * [MESOS-6597] - Include v1 Operator API protos in generated JAR and
> python packages.
>   * [MESOS-6621] - SSL downgrade path will CHECK-fail when using both
> temporary and persistent sockets.
>   * [MESOS-6624] - Master WebUI does not work on Firefox 45.
>   * [MESOS-6676] - Always re-link with scheduler during re-registration.
>   * [MESOS-6848] - The default executor does not exit if a single task pod
> fails.
>   * [MESOS-6852] - Nested container's launch command is not set correctly
> in docker/runtime isolator.
>   * [MESOS-6917] - Segfault when the executor sets an invalid UUID when
> sending a status update.
>   * [MESOS-7008] - Quota not recovered from registry in empty cluster.
>
> 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.1.1-rc1
> 
> 
>
> The candidate for Mesos 1.1.1 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.1.1-rc1/mesos-1.1.1.tar.gz
>
> The tag to be voted on is 1.1.1-rc1:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.1.1-rc1
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.1.1-rc1/
> mesos-1.1.1.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.1.1-rc1/
> mesos-1.1.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-1177
>
> Please vote on releasing this package as Apache Mesos 1.1.1!
>
> The vote is open until Fri Feb 10 23:59:59 CET 2017 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 1.1.1
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Till & Alex
>


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

2017-02-06 Thread Kapil Arya
+1 binding.

Built rpm/deb packages on internal build jobs. Packages are available here:
 http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.3-rc2

On Mon, Feb 6, 2017 at 3:01 PM, Adam Bordelon  wrote:

> +1 binding
>
> Tests passed against DC/OS 1.8.8 (prerelease), which is based on the Apache
> Mesos 1.0.x branch.
> https://github.com/dcos/dcos/pull/1210
>
> On Wed, Feb 1, 2017 at 10:01 AM, Vinod Kone  wrote:
>
> > +1 (binding)
> >
> > Tested on ASF CI
> >
> >
> > *Revision*: c673fdd00e7f93ab7844965435d57fd691fb4d8d
> >
> >- refs/tags/1.0.3-rc2
> >
> > Configuration Matrix gcc clang
> > centos:7 --verbose --enable-libevent --enable-ssl autotools
> > [image: Success]
> >  Release/26/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Not run]
> > cmake
> > [image: Success]
> >  Release/26/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%
> 7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Not run]
> > --verbose autotools
> > [image: Success]
> >  Release/26/BUILDTOOL=autotools,COMPILER=gcc,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_
> exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Not run]
> > cmake
> > [image: Success]
> >  Release/26/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%
> 3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Not run]
> > ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools
> > [image: Success]
> >  Release/26/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]
> >  Release/26/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose%20--
> enable-libevent%20--enable-ssl,ENVIRONMENT=GLOG_v=1%
> 20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%
> 7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > cmake
> > [image: Success]
> >  Release/26/BUILDTOOL=cmake,COMPILER=gcc,CONFIGURATION=--
> verbose%20--enable-libevent%20--enable-ssl,ENVIRONMENT=
> GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(
> docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > [image: Success]
> >  Release/26/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]
> >  Release/26/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]
> >  Release/26/BUILDTOOL=autotools,COMPILER=clang,CONFIGURATION=--verbose,
> ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,
> label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/>
> > cmake
> > [image: Success]
> >  Release/26/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]
> >  Release/26/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 Tue, Jan 31, 2017 at 11:46 AM, Vinod Kone 
> wrote:
> >
> >> Hi all,
> >>
> >>
> >> Please vote on releasing the following candidate as Apache Mesos 1.0.3.
> >>
> >>
> >> 1.0.3 includes the following:
> >>
> >> 
> >> 
> >>
> >> * [MESOS-6052] - Unable to launch containers on CNI networks on
> >> CoreOS
> >>
> >> * [MESOS-6142] - Frameworks may RESERVE for an arbitrary role.
> 

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

2016-08-12 Thread Kapil Arya
+1 (binding)

You can find the rpm/deb packages here:
  http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.1-rc1

The following docker tags (built off of ubuntu 14.04) are also available:
mesosphere/mesos:1.0.1-rc1
mesosphere/mesos-master:1.0.1-rc1
mesosphere/mesos-slave:1.0.1-rc1

Kapil

On Fri, Aug 12, 2016 at 4:39 PM, Alex Rukletsov  wrote:

> +1 (binding)
>
> make check on Mac OS 10.11.6 with apple clang-703.0.31.
>
> DockerFetcherPluginTest.INTERNET_CURL_FetchImage is flaky (MESOS-4570),
> but
> this does not seem to be a regression or a blocker.
>
> On Fri, Aug 12, 2016 at 10:30 PM, Radoslaw Gruchalski <
> ra...@gruchalski.com>
> wrote:
>
> > I am trying to build Mesos 1.0.1 for Centos 7 in a Docker container but
> > I'm hitting this: https://issues.apache.org/jira/browse/MESOS-5925.
> >
> > Kind regards,
> >
> > Radek Gruchalski
> > ra...@gruchalski.com
> > +4917685656526
> >
> > *Confidentiality:*
> > This communication is intended for the above-named person and may be
> > confidential and/or legally privileged.
> > If it has come to you in error you must take no action based on it, nor
> > must you copy or show it to anyone; please delete/destroy and inform the
> > sender immediately.
> >
> > On Thu, Aug 11, 2016 at 2:32 AM, Vinod Kone 
> wrote:
> >
> >> Hi all,
> >>
> >>
> >> Please vote on releasing the following candidate as Apache Mesos 1.0.1.
> >>
> >>
> >> The CHANGELOG for the release is available at:
> >>
> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
> >> lain;f=CHANGELOG;hb=1.0.1-rc1
> >>
> >> 
> >> 
> >>
> >>
> >> The candidate for Mesos 1.0.1 release is available at:
> >>
> >> https://dist.apache.org/repos/dist/dev/mesos/1.0.1-rc1/
> mesos-1.0.1.tar.gz
> >>
> >>
> >> The tag to be voted on is 1.0.1-rc1:
> >>
> >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=
> commit;h=1.0.1-rc1
> >>
> >>
> >> The MD5 checksum of the tarball can be found at:
> >>
> >> https://dist.apache.org/repos/dist/dev/mesos/1.0.1-rc1/mesos
> >> -1.0.1.tar.gz.md5
> >>
> >>
> >> The signature of the tarball can be found at:
> >>
> >> https://dist.apache.org/repos/dist/dev/mesos/1.0.1-rc1/mesos
> >> -1.0.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-1155
> >>
> >>
> >> Please vote on releasing this package as Apache Mesos 1.0.1!
> >>
> >>
> >> The vote is open until Mon Aug 15 17:29:33 PDT 2016 and passes if a
> >> majority of at least 3 +1 PMC votes are cast.
> >>
> >>
> >> [ ] +1 Release this package as Apache Mesos 1.0.1
> >>
> >> [ ] -1 Do not release this package because ...
> >>
> >>
> >> Thanks,
> >>
> >
> >
>


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

2016-07-28 Thread Kapil Arya
PS: Please note that starting with this Mesos 1.0.0 release, the binary
rpm/deb packages published at http://open.mesosphere.com/downloads/mesos
(for the Mesosphere package repos hosted at: repo.mesosphere.com) are built
with libevent+SSL and module dependency installation (i.e.
`./configure --enable-libevent --enable-ssl --enable-install-module-
dependencies`).

All future 1.x.y releases will continue to be configured with SSL+libevent

All older releases, i.e., 0.x.y, will continue to be configured _without_
SSL+libevent.

Best,
Kapil


On Wed, Jul 27, 2016 at 6:10 PM, Kapil Arya <ka...@mesosphere.io> wrote:

> You can find the 1.0.0 rpm/deb packages at:
>
> http://open.mesosphere.com/downloads/mesos/#apache-mesos-1.0.0
>
>
> And here are the corresponding docker images based off of Ubuntu 14.04:
>
> mesosphere/mesos:1.0.0
> mesosphere/mesos-master:1.0.0
> mesosphere/mesos-slave:1.0.0
>
> Kapil
>
> On Wed, Jul 27, 2016 at 2:52 PM, Jeff Schroeder <
> jeffschroe...@computer.org> wrote:
>
>> Small nit but can you s/experimnental/experimental/ under the "Storage"
>> header in the release post please?
>>
>> Great work otherwise everyone!
>>
>>
>> On Wednesday, July 27, 2016, Vinod Kone <vinodk...@apache.org> wrote:
>>
>>> Hi all,
>>>
>>> The vote for Mesos 1.0.0 (rc4) has passed with the following votes.
>>>
>>>
>>> +1 (Binding)
>>>
>>> --
>>>
>>> Kapil Arya
>>>
>>> Jie Yu
>>>
>>> Benjamin Mahler
>>>
>>>
>>> +1 (Non-binding)
>>>
>>> --
>>>
>>> Haosdent
>>>
>>> Greg Mann
>>>
>>> Zhitao Li
>>>
>>>
>>> +0
>>>
>>> -
>>>
>>> Yan Xu
>>>
>>>
>>> There were no  -1 votes.
>>>
>>>
>>> *NOTE: There were a couple known issues [MESOS-5911
>>> <https://issues.apache.org/jira/browse/MESOS-5911>, MESOS-5913
>>> <https://issues.apache.org/jira/browse/MESOS-5913>] that couldn't be fixed
>>> in time for the 1.0. We plan to do a patch release to fix these ASAP.*
>>>
>>>
>>> Please find the release at:
>>>
>>> https://dist.apache.org/repos/dist/release/mesos/1.0.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.0.0
>>>
>>>
>>> The mesos-1.0.0.jar has been released to:
>>>
>>> https://repository.apache.org
>>>
>>>
>>> The website (http://mesos.apache.org) will be updated shortly to
>>> reflect this release.
>>>
>>>
>>> Thanks,
>>>
>>> On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone <vinodk...@apache.org>
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>>
>>>> Please vote on releasing the following candidate as Apache Mesos 1.0.0.
>>>>
>>>> *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a
>>>> majority of at least 3 +1 PMC votes are cast.*
>>>>
>>>> 1.0.0 includes the following:
>>>>
>>>>
>>>> 
>>>>
>>>>   * Scheduler and Executor v1 HTTP APIs are now considered stable.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>   * [MESOS-4791] - **Experimental** support for v1 Master and Agent
>>>> APIs. These
>>>>
>>>> APIs let operators and services (monitoring, load balancers) send
>>>> HTTP
>>>>
>>>> requests to '/api/v1' endpoint on master or agent. See
>>>>
>>>>
>>>> `docs/operator-http-api.md` for details.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>   * [MESOS-4828] - **Experimental** support for a new `disk/xfs'
>>>> isolator
>>>>
>>>> has been added to isolate disk resources more efficiently. Please
>>>> refer to
>>>>
>>>> docs/mesos-containerizer.md for more details.
>>>>
>>>>
&g

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

2016-07-27 Thread Kapil Arya
You can find the 1.0.0 rpm/deb packages at:

http://open.mesosphere.com/downloads/mesos/#apache-mesos-1.0.0


And here are the corresponding docker images based off of Ubuntu 14.04:

mesosphere/mesos:1.0.0
mesosphere/mesos-master:1.0.0
mesosphere/mesos-slave:1.0.0

Kapil

On Wed, Jul 27, 2016 at 2:52 PM, Jeff Schroeder <jeffschroe...@computer.org>
wrote:

> Small nit but can you s/experimnental/experimental/ under the "Storage"
> header in the release post please?
>
> Great work otherwise everyone!
>
>
> On Wednesday, July 27, 2016, Vinod Kone <vinodk...@apache.org> wrote:
>
>> Hi all,
>>
>> The vote for Mesos 1.0.0 (rc4) has passed with the following votes.
>>
>>
>> +1 (Binding)
>>
>> --
>>
>> Kapil Arya
>>
>> Jie Yu
>>
>> Benjamin Mahler
>>
>>
>> +1 (Non-binding)
>>
>> --
>>
>> Haosdent
>>
>> Greg Mann
>>
>> Zhitao Li
>>
>>
>> +0
>>
>> -
>>
>> Yan Xu
>>
>>
>> There were no  -1 votes.
>>
>>
>> *NOTE: There were a couple known issues [MESOS-5911
>> <https://issues.apache.org/jira/browse/MESOS-5911>, MESOS-5913
>> <https://issues.apache.org/jira/browse/MESOS-5913>] that couldn't be fixed
>> in time for the 1.0. We plan to do a patch release to fix these ASAP.*
>>
>>
>> Please find the release at:
>>
>> https://dist.apache.org/repos/dist/release/mesos/1.0.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.0.0
>>
>>
>> The mesos-1.0.0.jar has been released to:
>>
>> https://repository.apache.org
>>
>>
>> The website (http://mesos.apache.org) will be updated shortly to reflect
>> this release.
>>
>>
>> Thanks,
>>
>> On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone <vinodk...@apache.org>
>> wrote:
>>
>>> Hi all,
>>>
>>>
>>> Please vote on releasing the following candidate as Apache Mesos 1.0.0.
>>>
>>> *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a
>>> majority of at least 3 +1 PMC votes are cast.*
>>>
>>> 1.0.0 includes the following:
>>>
>>>
>>> 
>>>
>>>   * Scheduler and Executor v1 HTTP APIs are now considered stable.
>>>
>>>
>>>
>>>
>>>
>>>   * [MESOS-4791] - **Experimental** support for v1 Master and Agent
>>> APIs. These
>>>
>>> APIs let operators and services (monitoring, load balancers) send
>>> HTTP
>>>
>>> requests to '/api/v1' endpoint on master or agent. See
>>>
>>>
>>> `docs/operator-http-api.md` for details.
>>>
>>>
>>>
>>>
>>>
>>>   * [MESOS-4828] - **Experimental** support for a new `disk/xfs'
>>> isolator
>>>
>>> has been added to isolate disk resources more efficiently. Please
>>> refer to
>>>
>>> docs/mesos-containerizer.md for more details.
>>>
>>>
>>>
>>>
>>>
>>>   * [MESOS-4355] - **Experimental** support for Docker volume plugin. We
>>> added a
>>>
>>> new isolator 'docker/volume' which allows users to use external
>>> volumes in
>>>
>>> Mesos containerizer. Currently, the isolator interacts with the
>>> Docker
>>>
>>> volume plugins using a tool called 'dvdcli'. By speaking the Docker
>>> volume
>>>
>>> plugin API, most of the Docker volume plugins are supported.
>>>
>>>
>>>
>>>
>>>
>>>   * [MESOS-4641] - **Experimental** A new network isolator, the
>>>
>>>
>>> `network/cni` isolator, has been introduced in the
>>> `MesosContainerizer`. The
>>>
>>> `network/cni` isolator implements the Container Network Interface
>>> (CNI)
>>>
>>> specification proposed by CoreOS.  With CNI the `network/cni`
>>> isolator is
>>>
>>> able to allocate a network namespace to Mesos containers and attach
>

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

2016-07-26 Thread Kapil Arya
+1 sounds good to me. However, if we end up going with (2), I'd commit to
test the new RC and provide a +1 tonight.

On Tue, Jul 26, 2016 at 10:02 PM, Jie Yu <yujie@gmail.com> wrote:

> I prefer 2 if possible. Since this is a UI fix which should be easy to
> validate. I am worried about people trying 1.0.0 because of the blog posts
> without noticing 1.0.1. If 2 does not work, I am OK with 1.
>
>
> On Jul 26, 2016, at 5:39 PM, Vinod Kone <vinodk...@apache.org> wrote:
>
> We've the ASF press wire and other community blog posts lined up to be
> posted tomorrow, so it will be really hard to tell all those folks to
> postpone it this late. I've a couple options that I want to propose
>
> 1) Fix the webui bug in 1.0.1 which we will cut as soon as we fix this bug.
>
> 2) Try to fix the bug in the next couple hours, cut rc5, and vote it in
> tonight without doing the typical 72 hour voting period.
>
>
> I'm personally leaning towards 1) given the timing and the nature of the
> bug. What do others think? PMC?
>
> On Tue, Jul 26, 2016 at 4:08 PM, Yan Xu <xuj...@apple.com> wrote:
>
>> I don't mind if it's shepherd by folks with more front-end expertise.
>> Actually my original suggested solution on
>> https://issues.apache.org/jira/browse/MESOS-5911 seemed incorrect. Let's
>> discuss the actual fix on the ticket, I feel that a short term fix
>> shouldn't be more than a few lines to unblock the release.
>>
>> On Jul 26, 2016, at 3:26 PM, Jie Yu <yujie@gmail.com> wrote:
>>
>> Yan, are you going to shepherd the fix for this one? If yes, when do you
>> think it can be done?
>>
>> - Jie
>>
>> On Tue, Jul 26, 2016 at 3:05 PM, Yan Xu <xuj...@apple.com> wrote:
>>
>> -1
>>
>> We tested it in our testing environment but webUI redirect didn't work. We
>> filed: https://issues.apache.org/jira/browse/MESOS-5911
>>
>> Given that webUI is the portal for Mesos clusters I feel that we should at
>> least have a basic fix (more context in the JIRA) before release 1.0.
>> Thoughts?
>>
>> On Jul 26, 2016, at 2:52 PM, Kapil Arya <ka...@mesosphere.io> wrote:
>>
>> +1 (binding)
>>
>> OpenSUSE Tumbleweed:
>>./configure --disable-java --disable-python && make check
>>
>> On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li <zhitaoli...@gmail.com> wrote:
>>
>> Also tested:
>>
>> make check passes on OS X
>>
>> One thing I found when testing RC4 debian with Aurora integration test
>> suite (on its master) is that scheduler previously expected GPU resource
>> will not receive offers without new `GPU_RESOURCES` capability even it's
>> the only scheduler.
>>
>> Given that GPU support is not technically released until 1.0, I don't
>> consider this is a blocker to me, but it might be surprising to people
>> already testing GPU support.
>>
>> On Tue, Jul 26, 2016 at 12:45 PM, Benjamin Mahler <bmah...@apache.org>
>> wrote:
>>
>> +1 (binding)
>>
>> OS X 10.11.6
>> ./configure --disable-python --disable-java
>> make check
>>
>> On Tue, Jul 26, 2016 at 10:24 AM, Greg Mann <g...@mesosphere.io> wrote:
>>
>> +1 (non-binding)
>>
>> * Ran `sudo make distcheck` successfully on CentOS 7.1 with only one
>>
>> test
>>
>> failure: ExamplesTest.PythonFramework fails for me the first time it's
>> executed as part of the whole test suite, and then succeeds on
>>
>> subsequent
>>
>> executions. I'm investigating further, and will file a ticket if
>>
>> necessary.
>>
>> * Ran the upgrade testing script successfully from 0.28.2 -> 1.0.0-rc4
>>
>> Cheers,
>> Greg
>>
>> On Tue, Jul 26, 2016 at 1:58 AM, haosdent <haosd...@gmail.com> wrote:
>>
>> +1
>>
>> * make check in CentOS 7.2
>> * make check in Ubuntu 14.04
>> * test upgrade from 0.28.2 to 1.0.0-rc4
>>
>>
>> On Tue, Jul 26, 2016 at 8:33 AM, Kapil Arya <ka...@mesosphere.io>
>>
>> wrote:
>>
>>
>> One can find the deb/rpm packages here:
>>
>> http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc4
>>
>>
>> And here are the corresponding docker images based off of Ubuntu
>>
>> 14.04:
>>
>>mesosphere/mesos:1.0.0-rc4
>>mesosphere/mesos-master:1.0.0-rc4
>>mesosphere/mesos-slave:1.0.0-rc4
>>
>> Kapil
>>
>> On Sat, Jul 23, 2016 at 1:40 AM, Vinod Kone <vinodk...@apache.org>
>>
>> wrote:
>>

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

2016-07-26 Thread Kapil Arya
+1 (binding)

OpenSUSE Tumbleweed:
./configure --disable-java --disable-python && make check

On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li <zhitaoli...@gmail.com> wrote:

> Also tested:
>
> make check passes on OS X
>
> One thing I found when testing RC4 debian with Aurora integration test
> suite (on its master) is that scheduler previously expected GPU resource
> will not receive offers without new `GPU_RESOURCES` capability even it's
> the only scheduler.
>
> Given that GPU support is not technically released until 1.0, I don't
> consider this is a blocker to me, but it might be surprising to people
> already testing GPU support.
>
> On Tue, Jul 26, 2016 at 12:45 PM, Benjamin Mahler <bmah...@apache.org>
> wrote:
>
>> +1 (binding)
>>
>> OS X 10.11.6
>> ./configure --disable-python --disable-java
>> make check
>>
>> On Tue, Jul 26, 2016 at 10:24 AM, Greg Mann <g...@mesosphere.io> wrote:
>>
>> > +1 (non-binding)
>> >
>> > * Ran `sudo make distcheck` successfully on CentOS 7.1 with only one
>> test
>> > failure: ExamplesTest.PythonFramework fails for me the first time it's
>> > executed as part of the whole test suite, and then succeeds on
>> subsequent
>> > executions. I'm investigating further, and will file a ticket if
>> necessary.
>> > * Ran the upgrade testing script successfully from 0.28.2 -> 1.0.0-rc4
>> >
>> > Cheers,
>> > Greg
>> >
>> > On Tue, Jul 26, 2016 at 1:58 AM, haosdent <haosd...@gmail.com> wrote:
>> >
>> >> +1
>> >>
>> >> * make check in CentOS 7.2
>> >> * make check in Ubuntu 14.04
>> >> * test upgrade from 0.28.2 to 1.0.0-rc4
>> >>
>> >>
>> >> On Tue, Jul 26, 2016 at 8:33 AM, Kapil Arya <ka...@mesosphere.io>
>> wrote:
>> >>
>> >> > One can find the deb/rpm packages here:
>> >> >
>> >> http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc4
>> >> >
>> >> > And here are the corresponding docker images based off of Ubuntu
>> 14.04:
>> >> > mesosphere/mesos:1.0.0-rc4
>> >> > mesosphere/mesos-master:1.0.0-rc4
>> >> > mesosphere/mesos-slave:1.0.0-rc4
>> >> >
>> >> > Kapil
>> >> >
>> >> > On Sat, Jul 23, 2016 at 1:40 AM, Vinod Kone <vinodk...@apache.org>
>> >> wrote:
>> >> >
>> >> > > Hi all,
>> >> > >
>> >> > >
>> >> > > Please vote on releasing the following candidate as Apache Mesos
>> >> 1.0.0.
>> >> > >
>> >> > > *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if
>> a
>> >> > > majority of at least 3 +1 PMC votes are cast.*
>> >> > >
>> >> > > 1.0.0 includes the following:
>> >> > >
>> >> > >
>> >> > >
>> >> >
>> >>
>> 
>> >> > >
>> >> > >   * Scheduler and Executor v1 HTTP APIs are now considered stable.
>> >> > >
>> >> > >
>> >> > >
>> >> > >
>> >> > >
>> >> > >   * [MESOS-4791] - **Experimental** support for v1 Master and Agent
>> >> APIs.
>> >> > > These
>> >> > >
>> >> > > APIs let operators and services (monitoring, load balancers)
>> send
>> >> > > HTTP
>> >> > >
>> >> > > requests to '/api/v1' endpoint on master or agent. See
>> >> > >
>> >> > >
>> >> > > `docs/operator-http-api.md` for details.
>> >> > >
>> >> > >
>> >> > >
>> >> > >
>> >> > >
>> >> > >   * [MESOS-4828] - **Experimental** support for a new `disk/xfs'
>> >> isolator
>> >> > >
>> >> > >
>> >> > > has been added to isolate disk resources more efficiently.
>> Please
>> >> > > refer to
>> >> > >
>> >> > > docs/mesos-containerizer.md for more details.
>> >> > >
>> >> > >
>> >> > >
>> >> > >
>>

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

2016-07-25 Thread Kapil Arya
One can find the deb/rpm packages here:
http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc4

And here are the corresponding docker images based off of Ubuntu 14.04:
mesosphere/mesos:1.0.0-rc4
mesosphere/mesos-master:1.0.0-rc4
mesosphere/mesos-slave:1.0.0-rc4

Kapil

On Sat, Jul 23, 2016 at 1:40 AM, Vinod Kone  wrote:

> Hi all,
>
>
> Please vote on releasing the following candidate as Apache Mesos 1.0.0.
>
> *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a
> majority of at least 3 +1 PMC votes are cast.*
>
> 1.0.0 includes the following:
>
>
> 
>
>   * Scheduler and Executor v1 HTTP APIs are now considered stable.
>
>
>
>
>
>   * [MESOS-4791] - **Experimental** support for v1 Master and Agent APIs.
> These
>
> APIs let operators and services (monitoring, load balancers) send
> HTTP
>
> requests to '/api/v1' endpoint on master or agent. See
>
>
> `docs/operator-http-api.md` for details.
>
>
>
>
>
>   * [MESOS-4828] - **Experimental** support for a new `disk/xfs' isolator
>
>
> has been added to isolate disk resources more efficiently. Please
> refer to
>
> docs/mesos-containerizer.md for more details.
>
>
>
>
>
>   * [MESOS-4355] - **Experimental** support for Docker volume plugin. We
> added a
>
> new isolator 'docker/volume' which allows users to use external
> volumes in
>
> Mesos containerizer. Currently, the isolator interacts with the
> Docker
>
> volume plugins using a tool called 'dvdcli'. By speaking the Docker
> volume
>
> plugin API, most of the Docker volume plugins are supported.
>
>
>
>
>
>   * [MESOS-4641] - **Experimental** A new network isolator, the
>
>
> `network/cni` isolator, has been introduced in the
> `MesosContainerizer`. The
>
> `network/cni` isolator implements the Container Network Interface
> (CNI)
>
> specification proposed by CoreOS.  With CNI the `network/cni` isolator
> is
>
> able to allocate a network namespace to Mesos containers and attach
> the
>
> container to different types of IP networks by invoking network
> drivers
>
> called CNI plugins.
>
>
>
>
>
>   * [MESOS-2948, MESOS-5403] - The authorizer interface has been
> refactored in
>
> order to decouple the ACLs definition language from the interface.
>
>
> It additionally includes the option of retrieving `ObjectApprover`.
> An
>
> `ObjectApprover` can be used to synchronously check authorizations for
> a
>
> given object and is hence useful when authorizing a large number of
> objects
>
> and/or large objects (which need to be copied using request based
>
>
> authorization). NOTE: This is a **breaking change** for authorizer
> modules.
>
>
>
>
>   * [MESOS-5405] - The `subject` and `object` fields in
> authorization::Request
>
> have been changed from required to optional. If either of these fields
> is
>
> not set, the request should only be authorized if any subject/object
> should
>
> be allowed.
>
>
> NOTE: This is a semantic change for authorizer modules.
>
>
>
>
>
>   * [MESOS-4931, MESOS-5709, MESOS-5704] - Authorization based HTTP
> endpoint
>
> filtering enables operators to restrict what part of the cluster state
> a
>
> user is authorized to see.
>
>
> Consider for example the `/state` master endpoint: an operator can
> now
>
> authorize users to only see a subset of the running frameworks, tasks,
> or
>
> Consider for example the `/state` master endpoint: an operator can
> now
>
> authorize users to only see a subset of the running frameworks, tasks,
> or
>
> executors. The following endpoints support HTTP endpoint filtering:
>
>
> '/state', '/state-summary', '/tasks', '/frameworks','/weights',
>
>
> and '/roles'. Additonally the following v1 API calls support
> filtering:
>
> 'GET_ROLES','GET_WEIGHTS','GET_FRAMEWORKS', 'GET_STATE', and
> 'GET_TASKS'.
>
>
>
>
>   * [MESOS-4909] - Tasks can now specify a kill policy. They are
> best-effort,
>
> because machine failures or forcible terminations may occur.
> Currently, the
>
> only available kill policy is how long to wait between graceful and
> forcible
>
> task kill. In the future, more policies may be available (e.g. hitting
> an
>
> HTTP endpoint, running a command, etc). Note that it is the
> executor's
>
> responsibility to enforce kill policies. For executor-less
> command-based
>
> tasks, the kill is performed via sending a signal to the task
> process:
>
> SIGTERM for the graceful kill and SIGKILL for the forcible kill. For
> docker
>
> executor-less tasks the grace period is passed to 'docker stop
> --time'. This
>
> feature supersedes the '--docker_stop_timeout', which is now
> deprecated.
>
>
>
>
>   * [MESOS-4908] - The task kill policy defined within 'TaskInfo' can now
> be
>
> overridden when the scheduler 

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

2016-07-11 Thread Kapil Arya
None of the stable builds have SSL yet. The first SSL-enabled stable build
will be 1.0.0. Sorry for the confusion.

Kapil

On Mon, Jul 11, 2016 at 1:03 PM, Zhitao Li <zhitaoli...@gmail.com> wrote:

> Hi Kapil,
>
> Do you mean that the stable builds from
> http://open.mesosphere.com/downloads/mesos is using the new configuration?
>
> On Sun, Jul 10, 2016 at 10:07 AM, Kapil Arya <ka...@mesosphere.io> wrote:
>
>> The binary rpm/deb packages can be found here:
>> http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc2
>> .
>>
>> Please note that starting with the 1.0.0 release (including RCs and
>> recent nightly builds), Mesos is configured with SSL and 3rdparty
>> module dependency installation. Here is the configure command line:
>> ./configure --enable-libevent --enable-ssl
>> --enable-install-module-dependencies
>>
>> As always, the stable builds are available at:
>> http://open.mesosphere.com/downloads/mesos
>>
>> The instructions for nightly builds are available at:
>> http://open.mesosphere.com/downloads/mesos-nightly/
>>
>> Best,
>> Kapil
>>
>>
>> On Thu, Jul 7, 2016 at 9:35 PM, Vinod Kone <vinodk...@apache.org> wrote:
>> >
>> > Hi all,
>> >
>> >
>> > Please vote on releasing the following candidate as Apache Mesos 1.0.0.
>> >
>> >
>> > 1.0.0 includes the following:
>> >
>> >
>> 
>> >
>> >   * Scheduler and Executor v1 HTTP APIs are now considered stable.
>> >
>> >
>> >
>> >
>> >
>> >   * [MESOS-4791] - **Experimental** support for v1 Master and Agent
>> APIs.
>> > These
>> >
>> > APIs let operators and services (monitoring, load balancers) send
>> HTTP
>> >
>> >
>> > requests to '/api/v1' endpoint on master or agent. See
>> >
>> >
>> > `docs/operator-http-api.md` for details.
>> >
>> >
>> >
>> >
>> >
>> >   * [MESOS-4828] - **Experimental** support for a new `disk/xfs'
>> isolator
>> >
>> >
>> > has been added to isolate disk resources more efficiently. Please
>> refer
>> > to
>> >
>> > docs/mesos-containerizer.md for more details.
>> >
>> >
>> >
>> >
>> >
>> >   * [MESOS-4355] - **Experimental** support for Docker volume plugin. We
>> > added a
>> >
>> > new isolator 'docker/volume' which allows users to use external
>> volumes
>> > in
>> >
>> > Mesos containerizer. Currently, the isolator interacts with the
>> Docker
>> >
>> >
>> > volume plugins using a tool called 'dvdcli'. By speaking the Docker
>> > volume
>> >
>> > plugin API, most of the Docker volume plugins are supported.
>> >
>> >
>> >
>> >
>> >
>> >   * [MESOS-4641] - **Experimental** A new network isolator, the
>> >
>> >
>> > `network/cni` isolator, has been introduced in the
>> > `MesosContainerizer`. The
>> >
>> > `network/cni` isolator implements the Container Network Interface
>> (CNI)
>> >
>> >
>> > specification proposed by CoreOS.  With CNI the `network/cni`
>> isolator
>> > is
>> >
>> > able to allocate a network namespace to Mesos containers and attach
>> the
>> >
>> >
>> > container to different types of IP networks by invoking network
>> drivers
>> >
>> >
>> > called CNI plugins.
>> >
>> >
>> >
>> >
>> >
>> >   * [MESOS-2948, MESOS-5403] - The authorizer interface has been
>> refactored
>> > in
>> >
>> > order to decouple the ACLs definition language from the interface.
>> >
>> >
>> > It additionally includes the option of retrieving `ObjectApprover`.
>> An
>> >
>> >
>> > `ObjectApprover` can be used to synchronously check authorizations
>> for
>> > a
>> >
>> > given object and is hence useful when authorizing a large number of
>> > objects
>> >
>> > and/or large objects (which need to be copied using request based
>> >
>> >
>> > authorization). NOTE: This 

Re: Setting up SSL for mesos

2016-07-10 Thread Kapil Arya
Starting with Mesos 1.0.0 (including RCs and the recently nightly builds),
the binary rpm/deb packages published at repo.mesosphere.com are built with
SSL and module dependency installation (i.e. `./configure --enable-libevent
--enable-ssl --enable-install-module-dependencies`).

You can find the appropriate rpm/deb packages at:
 * Stable: http://open.mesosphere.com/downloads/mesos/
 * RC: http://open.mesosphere.com/downloads/mesos-rc/
 * Nightly: http://open.mesosphere.com/downloads/mesos-nightly/

Best,
Kapil

On Fri, Jul 8, 2016 at 1:40 PM, Tim Harper  wrote:

> Id like to see it enabled. Or, a docker image to make it easy to build
> packages would be super cool too.
>
> Sent from my iPhone
>
> On Jul 7, 2016, at 17:56, Douglas Nelson  wrote:
>
> Inlining the environment variable fixed it! I had to use sudo to run
> mesos, so I either needed to inline it or use -E. *Facepalm*
>
> On the note of building mesos, is there any chance in the future that
> mesosphere would create a prebuilt mesos package with ssl included? It
> would be nice to avoid building on each machine I want to run mesos on.
> Also, it would be great to have the convenience of using config files,
> having automatic startup, etc with a simple apt-get install mesos-ssl. Is
> that something that's been considered?
>
> Thanks!
>
> On Thu, Jul 7, 2016 at 1:14 PM, Joseph Wu  wrote:
>
>> Can you double-check if your master is linking to openssl?
>>
>> From your build folder, you should get something like:
>> ldd src/.libs/mesos-master | grep ssl
>> libevent_openssl-2.0.so.5 => /lib64/libevent_openssl-2.0.so.5
>> libssl.so.10 => /lib64/libssl.so.10
>> libssl3.so => /lib64/libssl3.so
>>
>> There doesn't seem to be anything wrong with your configure/build steps.
>> And your environment variables setup should work on any sane Unix shell.
>> (Perhaps inline the environment variable?  SSL_ENABLED=true
>> ./mesos-master.sh ...)
>>
>> On Thu, Jul 7, 2016 at 11:53 AM, Douglas Nelson 
>> wrote:
>>
>>> I rebuilt from scratch with SSL support and got no errors. I only set 
>>> *export
>>> SSL_ENABLED=true* and then I ran the mesos-master.
>>>
>>> No errors were thrown and I can see the web UI via HTTP. I double
>>> checked that I was running the .sh from the build folder I created. Is
>>> mesos not connecting with the environment variable I set for some reason?
>>>
>>>
>>>
>>> On Wed, Jul 6, 2016 at 2:20 PM, Joseph Wu  wrote:
>>>
 If you can see the WebUI via HTTP, without downgrade support, you might
 be inadvertently running a different version of Mesos than the one you
 built.

 You can quickly sanity check this by removing either SSL_KEY_FILE or
 SSL_CERT_FILE and starting your master.  If your build has SSL support, it
 should immediately exit with an error message.


 On Wed, Jul 6, 2016 at 12:33 PM, Douglas Nelson 
 wrote:
 >
 > I attempted to set up SSL following this guide:
 http://mesos.apache.org/documentation/latest/ssl/
 >
 > I'm able to hit the WebUI with http but using https gives me nothing.
 I must be missing something. Here are the steps I'm taking:
 >
 > I downloaded 0.28.2 from here:
 https://github.com/apache/mesos/releases
 > I ran ./configure --enable-libevent --enable-ssl
 > Then I ran make and make install
 > I set the following environment variables:
 >
 > export SSL_ENABLED=1
 > export SSL_SUPPORT_DOWNGRADE=0
 > export SSL_KEY_FILE=
 > export SSL_CERT_FILE=
 >
 > Finally, I ran ./bin/mesos-master.sh --ip=127.0.0.1
 --work_dir=/var/lib/mesos
 >
 > I can provide any additional information if needed. Thanks!
 >
 > Also, I read that SSL would be included in mesosphere's nightly
 builds: https://open.mesosphere.com/downloads/mesos-nightly/
 >
 > How stable are those builds and has SSL already been included?
 >
 > -Doug Nelson


>>>
>>
>


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

2016-07-10 Thread Kapil Arya
The binary rpm/deb packages can be found here:
http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc2.

Please note that starting with the 1.0.0 release (including RCs and
recent nightly builds), Mesos is configured with SSL and 3rdparty
module dependency installation. Here is the configure command line:
./configure --enable-libevent --enable-ssl
--enable-install-module-dependencies

As always, the stable builds are available at:
http://open.mesosphere.com/downloads/mesos

The instructions for nightly builds are available at:
http://open.mesosphere.com/downloads/mesos-nightly/

Best,
Kapil

On Thu, Jul 7, 2016 at 9:35 PM, Vinod Kone  wrote:
>
> Hi all,
>
>
> Please vote on releasing the following candidate as Apache Mesos 1.0.0.
>
>
> 1.0.0 includes the following:
>
>

>
>   * Scheduler and Executor v1 HTTP APIs are now considered stable.
>
>
>
>
>
>   * [MESOS-4791] - **Experimental** support for v1 Master and Agent APIs.
> These
>
> APIs let operators and services (monitoring, load balancers) send HTTP
>
>
> requests to '/api/v1' endpoint on master or agent. See
>
>
> `docs/operator-http-api.md` for details.
>
>
>
>
>
>   * [MESOS-4828] - **Experimental** support for a new `disk/xfs' isolator
>
>
> has been added to isolate disk resources more efficiently. Please
refer
> to
>
> docs/mesos-containerizer.md for more details.
>
>
>
>
>
>   * [MESOS-4355] - **Experimental** support for Docker volume plugin. We
> added a
>
> new isolator 'docker/volume' which allows users to use external
volumes
> in
>
> Mesos containerizer. Currently, the isolator interacts with the Docker
>
>
> volume plugins using a tool called 'dvdcli'. By speaking the Docker
> volume
>
> plugin API, most of the Docker volume plugins are supported.
>
>
>
>
>
>   * [MESOS-4641] - **Experimental** A new network isolator, the
>
>
> `network/cni` isolator, has been introduced in the
> `MesosContainerizer`. The
>
> `network/cni` isolator implements the Container Network Interface
(CNI)
>
>
> specification proposed by CoreOS.  With CNI the `network/cni` isolator
> is
>
> able to allocate a network namespace to Mesos containers and attach
the
>
>
> container to different types of IP networks by invoking network
drivers
>
>
> called CNI plugins.
>
>
>
>
>
>   * [MESOS-2948, MESOS-5403] - The authorizer interface has been
refactored
> in
>
> order to decouple the ACLs definition language from the interface.
>
>
> It additionally includes the option of retrieving `ObjectApprover`. An
>
>
> `ObjectApprover` can be used to synchronously check authorizations for
> a
>
> given object and is hence useful when authorizing a large number of
> objects
>
> and/or large objects (which need to be copied using request based
>
>
> authorization). NOTE: This is a **breaking change** for authorizer
> modules.
>
>
>
>
>   * [MESOS-5405] - The `subject` and `object` fields in
> authorization::Request
>
> have been changed from required to optional. If either of these fields
> is
>
> not set, the request should only be authorized if any subject/object
> should
>
> be allowed.
>
> NOTE: This is a semantic change for authorizer modules.
>
>
>
>
>
>   * [MESOS-4931, MESOS-5709, MESOS-5704] - Authorization based HTTP
> endpoint
>
> filtering enables operators to restrict what part of the cluster state
> a
>
> user is authorized to see.
>
>
> Consider for example the `/state` master endpoint: an operator can now
>
>
> authorize users to only see a subset of the running frameworks, tasks,
> or
>
> executors. The following endpoints support HTTP endpoint filtering:
>
>
> '/state', '/state-summary', '/tasks', '/frameworks','/weights',
>
>
> and '/roles'. Additonally the following v1 API calls support
filtering:
>
>
> 'GET_ROLES','GET_WEIGHTS','GET_FRAMEWORKS', 'GET_STATE', and
> 'GET_TASKS'.
>
>
>
>
>   * [MESOS-4909] - Tasks can now specify a kill policy. They are
> best-effort,
>
> because machine failures or forcible terminations may occur.
Currently,
> the
>
> only available kill policy is how long to wait between graceful and
> forcible
>
> task kill. In the future, more policies may be available (e.g. hitting
> an
>
> HTTP endpoint, running a command, etc). Note that it is the executor's
>
>
> responsibility to enforce kill policies. For executor-less
> command-based
>
> tasks, the kill is performed via sending a signal to the task process:
>
>
> SIGTERM for the graceful kill and SIGKILL for the forcible kill. For
> docker
>
> executor-less tasks the grace period is passed to 'docker stop
--time'.
> This
>
> feature supersedes the '--docker_stop_timeout', which is now
> deprecated.
>
>
>
>
>   * [MESOS-4908] - The task kill policy defined within 'TaskInfo' can now
> be
>

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

2016-06-20 Thread Kapil Arya
+1 (binding) Internal CI build.

Here is a link to the deb/rpm packages:

http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-0.26.2-rc1



On Mon, Jun 20, 2016 at 6:07 PM, Vinod Kone  wrote:

> +1 (binding)
>
> Tested on ASF CI w/ ubuntu. Note that centos:7 build issue is due to a
> known configuration issue (unable to find JAVA_HOME), fixed in 0.27.0, with
> the build script.
>
> *Revision*: 5edc7bab79649341c44df21c8842e05fb6d6c2bb
>
>- refs/tags/0.26.2-rc1
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl
> [image: Failed]
> 
> [image: Not run]
> --verbose
> [image: Failed]
> 
> [image: Not run]
> ubuntu:14.04 --verbose --enable-libevent --enable-ssl
> [image: Success]
> 
> [image: Success]
> 
> --verbose
> [image: Success]
> 
> [image: Success]
> 
>
> On Mon, Jun 20, 2016 at 11:25 AM, Jie Yu  wrote:
>
>> Hi all,
>>
>> Please vote on releasing the following candidate as Apache Mesos 0.26.2.
>>
>>
>> 0.26.2 is a bug fix release. It includes the following:
>>
>> 
>> [MESOS-4705] - Linux 'perf' parsing logic may fail when OS distribution
>> has perf backports.
>> [MESOS-5449] - Memory leak in SchedulerProcess.declineOffer.
>>
>> 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.2-rc1
>>
>> 
>>
>> The candidate for Mesos 0.26.2 release is available at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.26.2-rc1/mesos-0.26.2.tar.gz
>>
>> The tag to be voted on is 0.26.2-rc1:
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.26.2-rc1
>>
>> The MD5 checksum of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.26.2-rc1/mesos-0.26.2.tar.gz.md5
>>
>> The signature of the tarball can be found at:
>>
>> https://dist.apache.org/repos/dist/dev/mesos/0.26.2-rc1/mesos-0.26.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-1147
>>
>> Please vote on releasing this package as Apache Mesos 0.26.2!
>>
>> The vote is open until Thu Jun 23 11:23:33 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.2
>> [ ] -1 Do not release this package because ...
>>
>> Thanks
>> - Jie
>>
>
>


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

2016-06-07 Thread Kapil Arya
Here is a link to the rpm/deb packages for Mesos 1.0.0-rc1:

http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-1.0.0-rc1

Please note that from this release (>=1.0.0-rc1) onwards, we are
configuring Mesos with SSL support. We have also added
`--enable-install-module-dependencies` configure flag to help ease module
development.

Finally, we'll continue to build the older bugfix releases for Mesos
versions <1.0.0 _without_ SSL support.

Best,
Kapil

On Tue, Jun 7, 2016 at 5:45 AM, Jörg Schad  wrote:

> Hi,
> the authorization documentation in the RC seems to be messing some changes
> introduced by https://issues.apache.org/jira/browse/MESOS-5405.
> We already added and committed fixes as part this ticket (see
>
> https://issues.apache.org/jira/browse/MESOS-5405?focusedCommentId=15318058=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15318058
> )
> but they should be included in the next RC (given that there will be a rc2
> :-) ).
>
> On Tue, Jun 7, 2016 at 3:32 AM, Robert Lacroix  wrote:
>
> > Hi Vinod,
> >
> > In convert.cpp
> > <
> https://github.com/apache/mesos/blob/master/src/java/jni/convert.cpp#L153>
> we
> > compare the major versions of the native library and the jar. This makes
> > upgrading frameworks unnecessarily hard because you would have to deploy
> > Mesos and frameworks in lockstep.
> >
> > Non-binding -1 , as this check isn’t strictly useful - especially given
> > this is probably the last major upgrade where libmesos is even relevant.
> >
> >  Robert
> >
> > On Jun 1, 2016, at 12:38 AM, Vinod Kone  wrote:
> >
> > Hi all,
> >
> > Please vote on releasing the following candidate as Apache Mesos 1.0.0.
> >
> >
> > NOTE: The voting period for this release is 3 weeks. Also, we are willing
> > to make API changes before the final release. So please test it
> thoroughly.
> >
> >
> > 1.0.0 includes the following features:
> >
> >
> >
> 
> >
> >  * Scheduler and Executor v1 HTTP APIs are now considered stable.
> >
> >
> >
> >
> >
> >  * [MESOS-4791] - **Experimental** support for v1 Master and Agent APIs.
> > These
> >
> >APIs let operators and services (monitoring, load balancers) send HTTP
> >
> >
> >requests to '/api/v1' endpoint on master or agent. These APIs look
> > similar
> >
> >to the v1 Scheduler and Executor APIs.
> >
> >
> >
> >
> >
> >  * [MESOS-4828] - **Experimental** support for a new `disk/xfs' isolator
> >
> >
> >has been added to isolate disk resources more efficiently. Please
> refer
> > to
> >
> >docs/mesos-containerizer.md for more details.
> >
> >
> >
> >
> >
> >  * [MESOS-4355] - **Experimental** support for Docker volume plugin. We
> > added a
> >
> >new isolator 'docker/volume' which allows users to use external
> volumes
> > in
> >
> >Mesos containerizer. Currently, the isolator interacts with the Docker
> >
> >
> >volume plugins using a tool called 'dvdcli'. By speaking the Docker
> > volume
> >
> >plugin API, most of the Docker volume plugins are supported.
> >
> >
> >
> >
> >
> >  * [MESOS-4641] - **Experimental** A new network isolator, the
> >
> >
> >`network/cni` isolator, has been introduced in the
> > `MesosContainerizer`. The
> >
> >`network/cni` isolator implements the Container Network Interface
> (CNI)
> >
> >
> >specification proposed by CoreOS.  With CNI the `network/cni` isolator
> > is
> >
> >able to allocate a network namespace to Mesos containers and attach
> the
> >
> >
> >container to different types of IP networks by invoking network
> drivers
> >
> >
> >called CNI plugins.
> >
> >
> >
> >
> >
> >  * [MESOS-2948, MESOS-5403] - The authorizer interface has been
> refactored
> > in
> >
> >order to decouple the ACLs definition language from the interface.
> >
> >
> >It additionally includes the option of retrieving `ObjectApprover`. An
> >
> >
> >`ObjectApprover` can be used to synchronously check authorizations for
> > a
> >
> >given object and is hence useful when authorizing a large number of
> > objects
> >
> >and/or large objects (which need to be copied using request based
> >
> >
> >authorization). NOTE: This is a **breaking change** for authorizer
> > modules.
> >
> >
> >
> >
> >  * [MESOS-4931] - Authorization based HTTP endpoint filtering enables
> > operators
> >
> >to restrict what part of the cluster state a user is authorized to
> see.
> >
> >
> >Consider for example the `/state` master endpoint: an operator can now
> >
> >
> >authorize users to only see a subset of the running frameworks, tasks,
> > or
> >
> >executors.
> >
> >
> >
> >
> >
> >  * [MESOS-4909] - Tasks can now specify a kill policy. They are
> > best-effort,
> >
> >because machine failures or forcible terminations may occur.
> Currently,
> > the
> >
> >only available kill policy is how 

Re: 0.28.2 has been released

2016-06-07 Thread Kapil Arya
Hi All,

The 0.28.2 rpm/deb packages can be found here:
http://open.mesosphere.com/downloads/mesos/#apache-mesos-0.28.2

Best,
Kapil

On Mon, Jun 6, 2016 at 5:21 PM, Kapil Arya <ka...@mesosphere.io> wrote:

> Hi Craig,
>
> I should be sending out a link to the RPM packages in a couple of days.
> (Our packaging scripts had some issues and I am working on fixing them).
>
> Kapil
>
> On Mon, Jun 6, 2016 at 6:15 AM, craig w <codecr...@gmail.com> wrote:
>
>> Jie,
>>
>> Thanks for the updates. When will the packages be available (in
>> particular RPM)?
>>
>> -craig
>>
>> On Sun, Jun 5, 2016 at 2:31 PM, Jie Yu <yujie@gmail.com> wrote:
>>
>>> Hi folks,
>>>
>>> I just released Mesos 0.28.2 and updated the website.
>>>
>>> It includes some important bug fixes. The change log can be found here:
>>>
>>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2
>>>
>>> If you are considering using 0.28, please use 0.28.2!
>>>
>>> Thanks!
>>> - Jie
>>>
>>
>>
>>
>> --
>>
>> https://github.com/mindscratch
>> https://www.google.com/+CraigWickesser
>> https://twitter.com/mind_scratch
>> https://twitter.com/craig_links
>>
>>
>


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

2016-06-07 Thread Kapil Arya
+1 (binding) Ran CI builds for various distros.

The deb/rpm packages can be found here:

http://open.mesosphere.com/downloads/mesos-rc/#apache-mesos-0.27.3-rc1

Kapil

On Tue, Jun 7, 2016 at 1:42 PM, Jie Yu  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 0.27.3.
>
> NOTE: I fat fingered and accidentally released the 0.27.3 jar to maven repo
> and I have no permission to remove it (apologies!). If this vote passes,
> nothing needs to be done. If not, I'll see how I can update it. Sorry about
> that.
>
>
> 0.27.3 is a bug fix release. It includes the following fixes:
>
> 
> ** Bug
>   * [MESOS-4705] - Linux 'perf' parsing logic may fail when OS distribution
> has perf backports.
>   * [MESOS-4869] - /usr/libexec/mesos/mesos-health-check using/leaking a
> lot of memory.
>   * [MESOS-5018] - FrameworkInfo Capability enum does not support upgrades.
>   * [MESOS-5021] - Memory leak in subprocess when 'environment' argument is
> provided.
>   * [MESOS-5449] - Memory leak in SchedulerProcess.declineOffer.
>
> 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.3-rc1
>
> 
>
> The candidate for Mesos 0.27.3 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/0.27.3-rc1/mesos-0.27.3.tar.gz
>
> The tag to be voted on is 0.27.3-rc1:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.27.3-rc1
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.27.3-rc1/mesos-0.27.3.tar.gz.md5
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.27.3-rc1/mesos-0.27.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-1145
>
> Please vote on releasing this package as Apache Mesos 0.27.3!
>
> The vote is open until Fri Jun 10 10:38:44 PDT 2016 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 0.27.3
> [ ] -1 Do not release this package because ...
>
> Thanks,
> - Jie
>


Re: 0.28.2 has been released

2016-06-06 Thread Kapil Arya
Hi Craig,

I should be sending out a link to the RPM packages in a couple of days.
(Our packaging scripts had some issues and I am working on fixing them).

Kapil

On Mon, Jun 6, 2016 at 6:15 AM, craig w  wrote:

> Jie,
>
> Thanks for the updates. When will the packages be available (in particular
> RPM)?
>
> -craig
>
> On Sun, Jun 5, 2016 at 2:31 PM, Jie Yu  wrote:
>
>> Hi folks,
>>
>> I just released Mesos 0.28.2 and updated the website.
>>
>> It includes some important bug fixes. The change log can be found here:
>>
>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2
>>
>> If you are considering using 0.28, please use 0.28.2!
>>
>> Thanks!
>> - Jie
>>
>
>
>
> --
>
> https://github.com/mindscratch
> https://www.google.com/+CraigWickesser
> https://twitter.com/mind_scratch
> https://twitter.com/craig_links
>
>


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

2016-05-30 Thread Kapil Arya
+1 (binding)

Distro package building for Ubuntu, Debian and CentOS. Here is the link to
the RC downloads page:
  http://open.mesosphere.com/downloads/mesos-rc/

Best,
Kapil



On Mon, May 30, 2016 at 3:17 PM, Till Toenshoff  wrote:

> +1
>
> Tested on OSX and various distros via private CI.
>
> OSX 10.11.5 (15F34), clang version 3.7.0 (trunk 235831) (llvm/trunk
> 235813):
>
> 
> [--] Global test environment tear-down
> [==] 1009 tests from 132 test cases ran. (299208 ms total)
> [  PASSED  ] 1003 tests.
> [  FAILED  ] 6 tests, listed below:
> [  FAILED  ] ExamplesTest.TestFramework
> [  FAILED  ] ExamplesTest.NoExecutorFramework
> [  FAILED  ] ExamplesTest.JavaFramework
> [  FAILED  ] ExamplesTest.PythonFramework
> [  FAILED  ] FetcherCacheTest.LocalUncachedExtract
> [  FAILED  ] FetcherCacheHttpTest.HttpMixed
>
>
> Debian 8
>
> ---
> [19:05:20][Step 10/10] [  PASSED  ] 1126 tests.
>
> Debian 8 - SSL
>
> ---
> [19:03:47][Step 10/10] [  PASSED  ] 1126 tests.
>
>
> Ubuntu 12
>
> ---
> [19:00:36][Step 10/10] [  PASSED  ] 1127 tests.
>
> Ubuntu 12 - SSL
>
> ---
> [19:01:53][Step 10/10] [  PASSED  ] 1127 tests.
>
> Ubuntu 14
>
> ---
> [19:01:19][Step 10/10] [  PASSED  ] 1125 tests.
>
> Ubuntu 14 - SSL
>
> ---
> [19:00:20][Step 10/10] [  PASSED  ] 1125 tests.
>
> Ubuntu 15
>
> ---
> [19:05:28][Step 10/10] [  PASSED  ] 1128 tests.
>
> Ubuntu 15 - SSL
>
> ---
> [19:05:58][Step 10/10] [  PASSED  ] 1128 tests.
>
>
> Centos 6
>
> ---
> [19:07:27][Step 10/10] [  PASSED  ] 1127 tests.
> [19:07:27][Step 10/10] [  FAILED  ] 1 test, listed below:
> [19:07:27][Step 10/10] [  FAILED  ]
> MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>
> Centos 6 - SSL
>
> ---
> [19:07:29][Step 10/10] [  PASSED  ] 1127 tests.
> [19:07:29][Step 10/10] [  FAILED  ] 1 test, listed below:
> [19:07:29][Step 10/10] [  FAILED  ]
> MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>
> Centos 7
>
> ---
> [19:05:43][Step 10/10] [  PASSED  ] 1129 tests.
> [19:05:43][Step 10/10] [  FAILED  ] 1 test, listed below:
> [19:05:43][Step 10/10] [  FAILED  ]
> LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>
> Centos 7 - SSL
>
> ---
> [19:04:53][Step 10/10] [  PASSED  ] 1129 tests.
> [19:04:53][Step 10/10] [  FAILED  ] 1 test, listed below:
> [19:04:53][Step 10/10] [  FAILED  ]
> LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>
>
>
>
>
> On May 30, 2016, at 8:23 AM, Vinod Kone  wrote:
>
> +1 (binding)
>
> Tested on ASF CI
>
> *Revision*: ceecad69bd9656cf405ca7378ad021c4ad51aaed
>
>   - refs/tags/0.28.2-rc1
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/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)/
> >
> [image: Not run]
> --verbose
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/
> >
> [image: Not run]
> ubuntu:14.04 --verbose --enable-libevent --enable-ssl
> [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/15/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)/
> >
> [image: Success]
> <
> 

Re: Mesos 0.28 SSL in official packages

2016-04-12 Thread Kapil Arya
At Mesosphere, we are planning to enable SSL into the nightlies starting
sometime later this week. The goal is to have both SSL and non-SSL Mesos
packages for Mesos 0.29.0 onwards in the Mesosphere deb/rpm repos. I will
send out another email as soon as the stuff is ready for the community.

Best,
Kapil

On Tue, Apr 12, 2016 at 12:22 PM, Steven Borrelli 
wrote:

> I’d be willing to assist in the effort to have standard packages (and
> additional packages for modules like net-modules).
>
> Steven Borrelli
> st...@borrelli.org
>
>
>
> > On Apr 12, 2016, at 11:10 AM, Adam Bordelon  wrote:
> >
> > We've discussed Apache-built/distributed packages before, and nobody
> > has any objections, but we need somebody to take on the work to get
> > the package builds setup. I believe Vinod had some thoughts on how to
> > get started, but any Apache committer (Zameer?) should have access to
> > builds.apache.org
> > I think we're all also in favor of improved documentation/website for
> > the Apache Mesos project, but we need your help for that too. File
> > JIRAs, submit patches!
> >
> > On Tue, Apr 12, 2016 at 5:42 AM, June Taylor  wrote:
> >> I heartily agree on both points. While I've found Mesosphere's
> documentation
> >> very helpful, it is often mixed up with the DCOS commercial offering.
> That
> >> may be something we're interested in down the road, but right now we are
> >> trying to stand up a relatively small cluster using straight
> >> Mesos/Marathon/Chronos, etc., and finding good documentation is very
> >> challenging due to the overlap with DCOS.
> >>
> >> The Apache documentation also, I think, is suffering precisely because
> >> Mesosphere has been serving up better materials on their own. It's
> certainly
> >> useful, but I'm a bit uncomfortable with that arrangement.
> >>
> >>
> >> Thanks,
> >> June Taylor
> >> System Administrator, Minnesota Population Center
> >> University of Minnesota
> >>
> >> On Tue, Apr 12, 2016 at 7:04 AM, Paul Bell  wrote:
> >>>
> >>> FWIW, I quite agree with Zameer's point.
> >>>
> >>> That said, I want to make abundantly clear that in my experience the
> folks
> >>> at Mesosphere are wonderfully helpful.
> >>>
> >>> But what happens if down the road Mesosphere is acquired or there
> occurs
> >>> some other event that could represent, if not a conflict of interest,
> then
> >>> simply a different strategic direction?
> >>>
> >>> My 2 cents.
> >>>
> >>> -Paul
> >>>
> >>> On Mon, Apr 11, 2016 at 5:19 PM, Zameer Manji 
> wrote:
> 
>  I have suggested this before and I will suggest it again here.
> 
>  I think the Apache Mesos project should build and distribute packages
>  instead of relying on the generosity of a commercial vendor. The
> Apache
>  Aurora project does this already with good success. As a user of
> Apache
>  Mesos I don't care about Mesosphere Inc and I feel uncomfortable that
> the
>  project is so dependent on its employees.
> 
>  Doing this would allow users to contribute packaging fixes directly to
>  the project, such as enabling SSL.
> 
>  On Mon, Apr 11, 2016 at 3:02 AM, Adam Bordelon 
>  wrote:
> >
> > Hi Kamil,
> >
> > Technically, there are no "official" Apache-built packages for Apache
> > Mesos.
> >
> > At least once company (Mesosphere) chooses to build and distribute
> > Mesos packages, but does not currently offer SSL builds. It wouldn't
> > be hard to add an SSL build to our regular builds, but it hasn't been
> > requested enough to prioritize it.
> >
> > cc: Joris, Kapil
> >
> > On Thu, Apr 7, 2016 at 7:42 AM, haosdent  wrote:
> >> Hi, ssl didn't enable default. You need compile it by following this
> >> doc
> >> http://mesos.apache.org/documentation/latest/ssl/
> >>
> >> On Thu, Apr 7, 2016 at 10:04 PM, Kamil Wokitajtis
> >> 
> >> wrote:
> >>>
> >>> This is my first post, so Hi everyone!
> >>>
> >>> Is SSL enabled in official packages (CentOS in my case)?
> >>> I can see libssl in ldd output, but I cannot see libevent.
> >>> I had to compile mesos from sources to run it over ssl.
> >>> I would prefer to install it from packages.
> >>>
> >>> Regards,
> >>> Kamil
> >>
> >>
> >>
> >>
> >> --
> >> Best Regards,
> >> Haosdent Huang
> >
> > --
> > Zameer Manji
> >
> >>>
> >>
>
>


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

2016-04-11 Thread Kapil Arya
+1 (binding)

CI runs with: amd64/centos/6 amd64/centos/7 amd64/debian/jessie
amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid
amd64/ubuntu/wily

On Wed, Apr 6, 2016 at 11:51 PM, Vinod Kone  wrote:

> +1 (binding)
>
> Tested on ASF CI. There was one flaky test that's new:
> https://issues.apache.org/jira/browse/MESOS-5139
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/13/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)/
> >
> [image:
> Not run]
> --verbose [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/13/COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/
> >
> [image:
> Not run]
> ubuntu:14.04 --verbose --enable-libevent --enable-ssl [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/13/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)/
> >
> [image:
> Failed]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/13/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)/
> >
> --verbose [image: Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/13/COMPILER=gcc,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/
> >
> [image:
> Success]
> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/13/COMPILER=clang,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/
> >
>
> On Wed, Apr 6, 2016 at 7:34 PM, Michael Park  wrote:
>
> > +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 

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

2016-04-07 Thread Kapil Arya
+1 (binding)

CI runs with: amd64/centos/6 amd64/centos/7 amd64/debian/jessie
amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid
amd64/ubuntu/wily

On Wed, Apr 6, 2016 at 11:53 PM, Vinod Kone  wrote:

> +1(binding)
>
> Tested on ASF CI.
>
> The centos failures are due to a known bug in the docker build script that
> cannot guess JAVA_HOME (has been fixed since).
>
> Configuration Matrix gcc clang
> centos:7 --verbose --enable-libevent --enable-ssl
> [image: Failed]
> 
> [image: Not run]
> --verbose
> [image: Failed]
> 
> [image: Not run]
> ubuntu:14.04 --verbose --enable-libevent --enable-ssl
> [image: Success]
> 
> [image: Success]
> 
> --verbose
> [image: Success]
> 
> [image: Success]
> 
>
> On Wed, Apr 6, 2016 at 8:50 PM, Vinod Kone  wrote:
>
>> oops wrong email thread. this should be for 28.1 voting thread.
>>
>> canceling this particular vote. i'll vote for 26.1 shortly.
>>
>> On Wed, Apr 6, 2016 at 8:46 PM, Vinod Kone  wrote:
>>
>>> +1 (binding)
>>>
>>> Tested on ASF CI. There was one flaky test that's new:
>>> https://issues.apache.org/jira/browse/MESOS-5139
>>>
>>> Configuration Matrix gcc clang
>>> centos:7 --verbose --enable-libevent --enable-ssl
>>> [image: Success]
>>> 
>>> [image: Not run]
>>> --verbose
>>> [image: Success]
>>> 
>>> [image: Not run]
>>> ubuntu:14.04 --verbose --enable-libevent --enable-ssl
>>> [image: Success]
>>> 
>>> [image: Failed]
>>> 
>>> --verbose
>>> [image: Success]
>>> 
>>> [image: Success]
>>> 
>>>
>>> On Wed, Apr 6, 2016 at 6:17 PM, Benjamin Mahler 
>>> wrote:
>>>
 +1 (binding)

 The following passes on OS X:
 $ ./configure CC=clang CXX=clang++ --disable-python --disable-java
 $ make check

 On Tue, Apr 5, 2016 at 11:41 PM, Michael Park  wrote:

> 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 

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

2016-04-07 Thread Kapil Arya
+1 (binding)

CI runs for amd64/centos/6 amd64/centos/7 amd64/debian/jessie
amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid amd64/


On Wed, Apr 6, 2016 at 9:43 PM, Vinod Kone  wrote:

> +1 (binding)
>
> `./configure && make check` on ubuntu 14.04
>
> On Wed, Apr 6, 2016 at 6:18 PM, Benjamin Mahler 
> wrote:
>
>> +1 (binding)
>>
>> The following passes on OS X:
>> $ ./configure CC=clang CXX=clang++ --disable-python --disable-java
>> $ make check
>>
>> On Tue, Apr 5, 2016 at 11:41 PM, Michael Park  wrote:
>>
>> > 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  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
>> >>
>> >
>> >
>>
>
>


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

2016-04-07 Thread Kapil Arya
+1 (binding)

CI runs for amd64/centos/6 amd64/centos/7 amd64/debian/jessie
amd64/ubuntu/precise amd64/ubuntu/trusty amd64/ubuntu/vivid amd64/




On Thu, Apr 7, 2016 at 12:44 AM, Vinod Kone  wrote:

> +1 (binding)
>
> make check on ubuntu 14.04
>
> On Wed, Apr 6, 2016 at 6:17 PM, Benjamin Mahler 
> wrote:
>
>> +1 (binding)
>>
>> The following passes on OS X:
>> $ ./configure CC=clang CXX=clang++ --disable-python --disable-java
>> $ make check
>>
>> On Tue, Apr 5, 2016 at 10:51 PM, Michael Park  wrote:
>>
>>> 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: [RESULT][VOTE] Release Apache Mesos 0.28.0 (rc2)

2016-03-19 Thread Kapil Arya
Here is a link to the rpm/deb packages:

http://open.mesosphere.com/downloads/mesos/#apache-mesos-0.28.0

Best,
Kapil

On Thu, Mar 17, 2016 at 2:33 PM, Vinod Kone <vinodk...@gmail.com> wrote:

> +1
>
> @vinodkone
>
> On Mar 17, 2016, at 11:27 AM, Bill Farner <wfar...@apache.org> wrote:
>
> Jake - i think that would be wonderful!
>
> On Thu, Mar 17, 2016 at 11:17 AM, Jake Farrell <jfarr...@apache.org>
> wrote:
>
>> I've been maintaining a deb/rpm set for Mesos and for Aurora and Thrift we
>> have been using the infra supported Bintray to make it available to the
>> community via http://www.apache.org/dist/${project}/${os}
>>
>> If there is interest I'd be happy to put some time into bringing my
>> patches
>> into reviews and helping setup jenkins tests, etc.
>>
>> -Jake
>>
>>
>>
>>
>>
>>
>> On Thu, Mar 17, 2016 at 1:41 PM, Vinod Kone <vinodk...@apache.org> wrote:
>>
>> > The project itself doesn't officially release rpms/debs, but the
>> community
>> > members do.  For example, Mesosphere is planning to release rpms/debs
>> > shortly.
>> >
>> > On Thu, Mar 17, 2016 at 10:38 AM, craig w <codecr...@gmail.com> wrote:
>> >
>> > > Great news. Do the rpm's get automatically built and released or will
>> > they
>> > > come later this week?
>> > >
>> > > On Thu, Mar 17, 2016 at 1:28 PM, Vinod Kone <vinodk...@apache.org>
>> > wrote:
>> > >
>> > >> Hi all,
>> > >>
>> > >>
>> > >> The vote for Mesos 0.28.0 (rc2) has passed with the
>> > >>
>> > >> following votes.
>> > >>
>> > >>
>> > >> +1 (Binding)
>> > >>
>> > >> --
>> > >>
>> > >> Vinod Kone
>> > >>
>> > >> Michael Park
>> > >>
>> > >> Kapil Arya
>> > >>
>> > >>
>> > >> +1 (Non-binding)
>> > >>
>> > >> --
>> > >>
>> > >> Greg Mann
>> > >>
>> > >> Daniel Osborne
>> > >>
>> > >> Jorg Schad
>> > >>
>> > >> Zhitao Li
>> > >>
>> > >>
>> > >> There were no 0 or -1 votes.
>> > >>
>> > >>
>> > >> Please find the release at:
>> > >>
>> > >> https://dist.apache.org/repos/dist/release/mesos/0.28.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.28.0
>> > >>
>> > >>
>> > >> The mesos-0.28.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,
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > >
>> > > https://github.com/mindscratch
>> > > https://www.google.com/+CraigWickesser
>> > > https://twitter.com/mind_scratch
>> > > https://twitter.com/craig_links
>> > >
>> > >
>> >
>>
>
>


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

2016-03-19 Thread Kapil Arya
+1 (binding).

You can find the links to rpm/deb files for this RC here:

http://open.mesosphere.com/downloads/mesos-rc/

On Thu, Mar 17, 2016 at 12:58 PM, Michael Park  wrote:

> +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 

Re: 0.27.2 RPMs

2016-03-10 Thread Kapil Arya
Hi All,

The 0.27.2 rpm/debian packages should now be in Mesosphere repositories.

Best,
Kapil

On Thu, Mar 10, 2016 at 3:57 PM, Pradeep Chhetri <
pradeep.chhetr...@gmail.com> wrote:

> Hello all,
>
> I still don't see any Mesos 0.27.2 deb/rpm artifacts in the mesosphere
> repository. Is this expected ?
>
> Thanks.
> On Mar 9, 2016 3:46 PM, "Rad Gruchalski"  wrote:
>
>> Oh, cool, I was expecting some info here.
>> Going to build one now :)
>>
>> Kind regards,
>> Radek Gruchalski
>> ra...@gruchalski.com 
>> de.linkedin.com/in/radgruchalski/
>>
>>
>> *Confidentiality:*This communication is intended for the above-named
>> person and may be confidential and/or legally privileged.
>> If it has come to you in error you must take no action based on it, nor
>> must you copy or show it to anyone; please delete/destroy and inform the
>> sender immediately.
>>
>> On Wednesday, 9 March 2016 at 16:44, craig w wrote:
>>
>> I thought so based on the website:
>> http://mesos.apache.org/blog/mesos-0-27-2-released/
>>
>>
>>


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

2016-03-04 Thread Kapil Arya
+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


On Fri, Mar 4, 2016 at 1:06 PM, Vinod Kone  wrote:

> Bad copy paste into the email, sorry. It looks fine in the CHANGELOG.
>
> On Fri, Mar 4, 2016 at 12:52 AM, Shuai Lin  wrote:
>
> >   * [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-4712] - Remove 'force' field from the Subscribe Call in v1
> >> Scheduler API.
> >
> >
> > MESOS-4712 is included twice.
> >
> > On Fri, Mar 4, 2016 at 1:25 PM, Vinod Kone  wrote:
> >
> >> On Thu, Mar 3, 2016 at 5:43 PM, Vinod Kone 
> wrote:
> >>
> >> > Tue Mar  10 17:00:00 PST 2016
> >>
> >>
> >> Sorry. This should be Mar 8th not 10th.
> >>
> >
> >
>


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

2016-02-29 Thread Kapil Arya
+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  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.26.1 (rc1)

2016-02-29 Thread Kapil Arya
+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:26 AM, Michael Park  wrote:

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


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

2016-02-29 Thread Kapil Arya
+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 Fri, Feb 26, 2016 at 11:54 PM, Michael Park  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
>


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

2016-02-29 Thread Kapil Arya
+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  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: [RESULT][VOTE] Release Apache Mesos 0.27.0 (rc2)

2016-02-04 Thread Kapil Arya
And here is the ticket tracking the user doc:
https://issues.apache.org/jira/browse/MESOS-4531. Will link to the
blog post once the doc is ready :-).

On Thu, Feb 4, 2016 at 11:38 AM, Jie Yu <yujie@gmail.com> wrote:
> Niklas,
>
> I think Joris is still working on the user doc for multi-disk support in
> Mesos.
>
> - Jie
>
> On Thu, Feb 4, 2016 at 1:22 AM, Niklas Nielsen <n...@qni.dk> wrote:
>
>> Awesome guys!
>>
>> Kapil, we usually linked to the user documentation in the blog to the new
>> features. Do you have a link to the docs on multiple disk resources?
>>
>> On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya <ka...@mesosphere.io> wrote:
>>
>> > And here is the blog post:
>> > http://mesos.apache.org/blog/mesos-0-27-0-released.
>> >
>> > On Wed, Feb 3, 2016 at 4:48 PM, Michael Park <mp...@apache.org> wrote:
>> > > 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
>> > >> >
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Niklas
>>


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

2016-02-04 Thread Kapil Arya
That's a good point, Niklas!

IMO, we should be able to ship a major feature as long as we have an
assurance that the user doc will land in the next few days (not
weeks).

On Thu, Feb 4, 2016 at 11:55 AM, Niklas Nielsen <n...@qni.dk> wrote:
> Thanks Jie and Kapil! Looking forward to it.
>
> I did read the proposal, but playing the devils advocate for a bit; how can
> we ship a 'major feature' without bundled user documentation? Referring to
> tickets and design docs (which may/or may not be the way things ended up
> getting implemented) or to code is not good enough, in my mind.
>
> Should we line up some expectations to available user docs, example
> framework code, etc. before announcing the availability of a feature?
>
> Niklas
>
> On Thu, Feb 4, 2016 at 5:41 PM, Kapil Arya <ka...@mesosphere.io> wrote:
>>
>> And here is the ticket tracking the user doc:
>> https://issues.apache.org/jira/browse/MESOS-4531. Will link to the
>> blog post once the doc is ready :-).
>>
>> On Thu, Feb 4, 2016 at 11:38 AM, Jie Yu <yujie@gmail.com> wrote:
>> > Niklas,
>> >
>> > I think Joris is still working on the user doc for multi-disk support in
>> > Mesos.
>> >
>> > - Jie
>> >
>> > On Thu, Feb 4, 2016 at 1:22 AM, Niklas Nielsen <n...@qni.dk> wrote:
>> >
>> >> Awesome guys!
>> >>
>> >> Kapil, we usually linked to the user documentation in the blog to the
>> >> new
>> >> features. Do you have a link to the docs on multiple disk resources?
>> >>
>> >> On Wed, Feb 3, 2016 at 11:27 PM, Kapil Arya <ka...@mesosphere.io>
>> >> wrote:
>> >>
>> >> > And here is the blog post:
>> >> > http://mesos.apache.org/blog/mesos-0-27-0-released.
>> >> >
>> >> > On Wed, Feb 3, 2016 at 4:48 PM, Michael Park <mp...@apache.org>
>> >> > wrote:
>> >> > > 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
>> >> > >> >
>> >> > >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Niklas
>> >>
>
>
>
>
> --
> Niklas


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

2016-02-03 Thread Kapil Arya
And here is the blog post: http://mesos.apache.org/blog/mesos-0-27-0-released.

On Wed, Feb 3, 2016 at 4:48 PM, Michael Park  wrote:
> Kapil is currently working on it. We'll publish it shortly :)
>
> On 3 February 2016 at 13:41, Benjamin Mahler  wrote:
>>
>> Great! Is a blog post on the way?
>>
>> On Sun, Jan 31, 2016 at 5:39 PM, Michael Park  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
>> >
>
>


Re: Welcome Kapil as Mesos committer and PMC member!

2015-11-05 Thread Kapil Arya
Thanks everyone! :-).



On Thu, Nov 5, 2015 at 3:50 PM, Elizabeth Lingg <elizab...@mesosphere.io>
wrote:

> Congrats Professor! You definitely deserve it.
>
> -Elizabeth
>
> On Thu, Nov 5, 2015 at 10:53 AM, Jie Yu <yujie@gmail.com> wrote:
>
> > Congrats Kapil!
> >
> > On Thu, Nov 5, 2015 at 2:02 AM, Till Toenshoff <toensh...@me.com> wrote:
> >
> > > I'm happy to announce that Kapil Arya has been voted a Mesos committer
> > and
> > > PMC member!
> > >
> > > Welcome Kapil, and thanks for all of your great contributions to the
> > > project so far!
> > >
> > > Looking forward to lots more of your contributions!
> > >
> > > Thanks
> > > Till
> >
>


Re: IP Per Container, Calico, etc

2015-10-26 Thread Kapil Arya
Github issue sounds like a good idea. That way we don't have to spam
everyone on the mailing list until we have a user doc ready.

Kapil

On Mon, Oct 26, 2015 at 2:52 PM, <connor@gmail.com> wrote:

> Hi John,
>
> One way to get connected could be to open an issue to track docs on the
> net-modules github project.  The Mesosphere and Project Calico folks will
> be able to answer specific questions about how to package and deploy the
> modules.  Your main points of contact are Spike Curtis on the Calico side
> and Kapil Arya for Mesos and modules.
>
> If you want to get a head start, the Vagrantfile, Dockerfile, and
> docker-compose.yml files in the net-modules repository pretty much describe
> the test setup on one virtual machine.
>
> --
> Connor
>
> On Oct 26, 2015, at 11:16, John Omernik <j...@omernik.com> wrote:
>
> Hey all, wondering if there was some resources out there for hacking on
> this. I saw the Mesos Con Presso and was impressed and would love to play
> with this more.
>
> Get Started
>
> Things are very early stage and in flux, but are ready for you to start
> trying out.  We’d love your feedback, issue reports, or pull requests.
>
> https://github.com/mesosphere/net-modules
>
> https://github.com/projectcalico/calico-mesos
>
> I started here, and this is where my questions start.
>
> First question I will lay out is a meta question: Are there any good
> resources I am missing (besides those links) that would help with
> background knowledge here?
>
> I am hoping to take my current lab/home mesos cluster and do a writeup on
> how to implement this on it.  I know that there is a demo out there, but I
> think it would help me (and perhaps others) to hack this into an existing
> cluster to better understand what has to happen to make this work. I will
> gladly share a write up of my progress with the group, and would be happy
> to post questions on list or do off lists with people to get things moving.
>
> I guess that leads to my second question: Does it make sense to put all my
> questions and stumbling out on list, or would it be better to work with
> some knowledgable folks and prepare a writeup for the community to use?
>
> I'll start with those questions and go from there...
>
> John
>
>


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

2015-10-10 Thread Kapil Arya
+1 (non-binding)

On Sat, Oct 10, 2015 at 9:58 AM, Joris Van Remoortere 
wrote:

> +1 (binding)
>
> On Fri, Oct 9, 2015 at 5:36 PM, Niklas Nielsen 
> wrote:
>
> > Hi all,
> >
> > Following up with an RC with the build fix suggested by Kapil:
> >
> > Please vote on releasing the following candidate as Apache Mesos 0.25.0.
> >
> >
> >
> > 0.25.0 includes the following:
> >
> >
> >
> 
> >
> >  * [MESOS-1474] - Experimental support for maintenance primitives.
> >
> >  * [MESOS-2600] - Added master endpoints /reserve and /unreserve for
> > dynamic reservations.
> >
> >  * [MESOS-2044] - Extended Module APIs to enable IP per container
> > assignment, isolation and resolution.
> >
> >
> > ** Bug fixes
> >
> >   * [MESOS-2635] - Web UI Display Bug when starting lots of tasks with
> > small cpu value.
> >
> >   * [MESOS-2986] - Docker version output is not compatible with Mesos.
> >
> >   * [MESOS-3046] - Stout's UUID re-seeds a new random generator during
> > each call to UUID::random.
> >
> >   * [MESOS-3051] - performance issues with port ranges comparison.
> >
> >   * [MESOS-3052] - Allocator performance issue when using a large number
> > of filters.
> >
> >   * [MESOS-3136] - COMMAND health checks with Marathon 0.10.0 are broken.
> >
> >   * [MESOS-3169] - FrameworkInfo should only be updated if the
> > re-registration is valid.
> >
> >   * [MESOS-3185] - Refactor Subprocess logic in linux/perf.cpp to use
> > common subroutine.
> >
> >   * [MESOS-3239] - Refactor master HTTP endpoints help messages such that
> > they cannot be out of sync.
> >
> >   * [MESOS-3245] - The comments of DRFSorter::dirty is not correct.
> >
> >   * [MESOS-3254] - Cgroup CHECK fails test harness.
> >
> >   * [MESOS-3258] - Remove Frameworkinfo capabilities on re-registration.
> >
> >   * [MESOS-3261] - Move QoS plug-ins to a specified folder like
> > resource_estimator.
> >
> >   * [MESOS-3269] - The comments of Master::updateSlave() is not correct.
> >
> >   * [MESOS-3282] - Web UI no longer shows Tasks information.
> >
> >   * [MESOS-3344] - Add more comments for strings::internal::fmt.
> >
> >   * [MESOS-3351] - duplicated slave id in master after master failover.
> >
> >   * [MESOS-3387] - Refactor MesosContainerizer to accept namespace
> > dynamically.
> >
> >   * [MESOS-3408] - Labels field of FrameworkInfo should be added into v1
> > mesos.proto.
> >
> >   * [MESOS-3411] - ReservationEndpointsTest.AvailableResources appears to
> > be faulty.
> >
> >   * [MESOS-3423] - Perf event isolator stops performing sampling if a
> > single timeout occurs.
> >
> >   * [MESOS-3426] - process::collect and process::await do not perform
> > discard propagation.
> >
> >   * [MESOS-3430] -
> > LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithoutRootFilesystem
> > fails on CentOS 7.1.
> >
> >   * [MESOS-3450] - Update Mesos C++ Style Guide for namespace usage.
> >
> >   * [MESOS-3451] - Failing tests after changes to
> > Isolator/MesosContainerizer API.
> >
> >   * [MESOS-3458] - Segfault when accepting or declining inverse offers.
> >
> >   * [MESOS-3474] - ExamplesTest.{TestFramework, JavaFramework,
> > PythonFramework} failed on CentOS 6.
> >
> >   * [MESOS-3489] - Add support for exposing Accept/Decline responses for
> > inverse offers.
> >
> >   * [MESOS-3490] - Mesos UI fails to represent JSON entities.
> >
> >   * [MESOS-3512] - Don't retry close() on EINTR.
> >
> >   * [MESOS-3513] - Cgroups Test Filters aborts tests on Centos 6.6.
> >
> >   * [MESOS-3519] - Fix file descriptor leakage / double close in the code
> > base.
> >
> >   * [MESOS-3538] -
> > CgroupsNoHierarchyTest.ROOT_CGROUPS_NOHIERARCHY_MountUnmountHierarchy
> test
> > is flaky.
> >
> >   * [MESOS-3575] - V1 API java/python protos are not generated.
> >
> >
> > ** Improvements
> >
> >   * [MESOS-2719] - Deprecating '.json' extension in master endpoints
> urls.
> >
> >   * [MESOS-2757] - Add -> operator for Option, Try, Result,
> > Future.
> >
> >   * [MESOS-2875] - Add containerId to ResourceUsage to enable QoS
> > controller to target a container.
> >
> >   * [MESOS-2964] - libprocess io does not support peek().
> >
> >   * [MESOS-2983] - Deprecating '.json' extension in slave endpoints url.
> >
> >   * [MESOS-2984] - Deprecating '.json' extension in files endpoints url.
> >
> >   * [MESOS-3037] - Add a SUPPRESS call to the scheduler.
> >
> >   * [MESOS-3187] - Docker cli option support.
> >
> >   * [MESOS-3304] - Remove remnants of LIBPROCESS_STATISTICS_WINDOW.
> >
> >   * [MESOS-3312] - Factor out JSON to repeated protobuf conversion.
> >
> >   * [MESOS-3340] - Command-line flags should take precedence over OS Env
> > variables.
> >
> >   * [MESOS-3347] - Remove dead code in src/linux/perf.cpp.
> >
> >   * [MESOS-3377] - mesos docker container with container_name as ENV
> > variable.
> >
> >   * [MESOS-3457] - Add flag to disable hostname 

Re: Removing external containerizer from code base

2015-10-08 Thread Kapil Arya
On Thu, Oct 8, 2015 at 1:57 PM, Jie Yu  wrote:

> Alex,
>
> Implementing your own containerizer totally makes sense. The containerizer
> interface can be modulized and your own containerizer can be implemented as
> a module. Please take a look at the module documentation
> . From what I
> can tell, implementing your own containerizer as a module will definitely
> be simpler than an external solution.
>
>  I assume we would have to implement it in cpp,
>
>
> Most likely because that's the most straightforward way. Other languages
> are also possible (e.g., using JNI for Java).
>

I don't know all the details, but I guess, depending upon the exact
interface, it might be possible to have a C++ wrapper around a non-C++
containerizer module. In a very naive approach, one simply fork/execs the
"external" non-C++ containerizer script/program.


>
> it might require recompiling (parts of) Mesos, some other things?
>
>
> No. With modules, you don't have to.
>
> Let me know if you have any further questions!
>
> - Jie
>
> On Thu, Oct 8, 2015 at 10:44 AM, Alex Glikson  wrote:
>
> > Actually we have been thinking to implement our own containerizer, and
> the
> > option to use ECP seemed attractive.
> > Can you, please, elaborate on the implications of having our own
> > containerizer without ECP? I assume we would have to implement it in cpp,
> > it might require recompiling (parts of) Mesos, some other things?
> >
> > Thanks,
> > Alex
> >
> >
> >
> >
> > From:Jie Yu 
> > To:mesos , "user@mesos.apache.org" <
> > user@mesos.apache.org>
> > Date:08/10/2015 03:12 AM
> > Subject:Removing external containerizer from code base
> > --
> >
> >
> >
> > Hey guys,
> >
> > Per discussion in MESOS-3370
> > , I'll start removing
> > the
> > external containerizer and cleaning up the relevant code.
> >
> > Please let me know if you have any concern. Thanks!
> >
> > - Jie
> >
> >
> >
>


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

2015-10-07 Thread Kapil Arya
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 <ka...@mesosphere.io> 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:
> <http://bugs.opensuse.org>.
>
> $ 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 <g...@mesosphere.io> 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] 

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

2015-10-07 Thread Kapil Arya
-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::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 warning in
> values test.") resolves this issue.
>
>
>
> On Wed, Oct 7, 2015 at 2:32 AM, Joris Van Remoortere 
> wrote:
>
> > +1 (binding)
> >
> > On Mon, Oct 5, 2015 at 11:12 PM, Niklas Nielsen 
> > wrote:
> >
> >> Hi all,
> >>
> >> Please vote on releasing the following candidate as Apache Mesos 0.25.0.
> >>
> >>
> >>
> >> 0.25.0 includes the following:
> >>
> >>
> >>
> 
> >>
> >>  * [MESOS-1474] - Experimental support for maintenance primitives.
> >>
> >>  * [MESOS-2600] - Added master endpoints /reserve and /unreserve for
> >> dynamic reservations.
> >>
> >>  * [MESOS-2044] - Extended Module APIs to enable IP per container
> >> assignment, isolation and resolution.
> >>
> >>
> >> ** Bug fixes
>