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

2016-03-04 Thread Avinash Sridharan 
Sorry,
Forgot to mention the platform details. Seeing the crash on Debian 8
dmin@ip-172-31-26-151:~/mesos/build$ cat /etc/issue
Debian GNU/Linux 8 \n \l

admin@ip-172-31-26-151:~/mesos/build$ uname -a
Linux ip-172-31-26-151 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3
(2016-01-17) x86_64 GNU/Linux

On Fri, Mar 4, 2016 at 6:49 PM, Avinash Sridharan 
wrote:

> I am seeing the following crash when I run mesos build of 0.28.0-rc1 `sudo
> bin/mesos-tests.sh` :
> [ RUN  ] MemIsolatorTest/1.MemUsage
> F0305 02:43:01.791003 32494 isolator_tests.cpp:905] CHECK_SOME(isolator):
> Failed to create memory cgroup: Failed to mount cg
> roups hierarchy at '/sys/fs/cgroup/memory': 'memory' is not enabled by the
> kernel
> *** Check failure stack trace: ***
> @ 0x7fc4630a025d  google::LogMessage::Fail()
> @ 0x7fc46309f63e  google::LogMessage::SendToLog()
> @ 0x7fc46309ff1d  google::LogMessage::Flush()
> @ 0x7fc4630a3388  google::LogMessageFatal::~LogMessageFatal()
> @   0x8bed57  _CheckFatal::~_CheckFatal()
> @  0x17c0ab7
>  mesos::internal::tests::MemIsolatorTest_MemUsage_Test<>::TestBody()
> @  0x1985243
>  testing::internal::HandleSehExceptionsInMethodIfSupported<>()
> @  0x1971d31
>  testing::internal::HandleExceptionsInMethodIfSupported<>()
> @  0x1952a55  testing::Test::Run()
> @  0x19536cb  testing::TestInfo::Run()
> @  0x1953dd7  testing::TestCase::Run()
> @  0x195b4ce  testing::internal::UnitTestImpl::RunAllTests()
> @  0x19825d3
>  testing::internal::HandleSehExceptionsInMethodIfSupported<>()
> @  0x1973d01
>  testing::internal::HandleExceptionsInMethodIfSupported<>()
> @  0x195b18b  testing::UnitTest::Run()
> @   0xe43611  RUN_ALL_TESTS()
> @   0xe424dc  main
> @ 0x7fc45e147b45  (unknown)
> @   0x8a0bbc  (unknown)
>
>
> Looks like the memory cgroup memory is disabled:
>
> admin@ip-172-31-26-151:~/mesos/build$ cat /proc/cgroups
> #subsys_namehierarchy   num_cgroups enabled
> cpuset  2   1   1
> cpu 3   2   1
> cpuacct 3   2   1
> memory  0   1   0
> devices 4   1   1
> freezer 5   2   1
> net_cls 6   1   1
>
> But I thought the test filters should have caught this ?
>
> On Fri, Mar 4, 2016 at 1:52 PM, Kapil Arya  wrote:
>
>> +1 (Binding)
>>
>> Successful CI builds for the following distros:
>>
>> amd64/centos/6
>> amd64/centos/7
>> amd64/debian/jessie
>> amd64/ubuntu/precise
>> amd64/ubuntu/trusty
>> amd64/ubuntu/vivid
>>
>>
>> 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.
>>> >>
>>> >
>>> >
>>>
>>
>>
>
>
> --
> Avinash Sridharan, Mesosphere
> +1 (323) 702 5245
>



-- 
Avinash Sridharan, Mesosphere
+1 (323) 702 5245

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

2016-03-04 Thread Avinash Sridharan 
I am seeing the following crash when I run mesos build of 0.28.0-rc1 `sudo
bin/mesos-tests.sh` :
[ RUN  ] MemIsolatorTest/1.MemUsage
F0305 02:43:01.791003 32494 isolator_tests.cpp:905] CHECK_SOME(isolator):
Failed to create memory cgroup: Failed to mount cg
roups hierarchy at '/sys/fs/cgroup/memory': 'memory' is not enabled by the
kernel
*** Check failure stack trace: ***
@ 0x7fc4630a025d  google::LogMessage::Fail()
@ 0x7fc46309f63e  google::LogMessage::SendToLog()
@ 0x7fc46309ff1d  google::LogMessage::Flush()
@ 0x7fc4630a3388  google::LogMessageFatal::~LogMessageFatal()
@   0x8bed57  _CheckFatal::~_CheckFatal()
@  0x17c0ab7
 mesos::internal::tests::MemIsolatorTest_MemUsage_Test<>::TestBody()
@  0x1985243
 testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@  0x1971d31
 testing::internal::HandleExceptionsInMethodIfSupported<>()
@  0x1952a55  testing::Test::Run()
@  0x19536cb  testing::TestInfo::Run()
@  0x1953dd7  testing::TestCase::Run()
@  0x195b4ce  testing::internal::UnitTestImpl::RunAllTests()
@  0x19825d3
 testing::internal::HandleSehExceptionsInMethodIfSupported<>()
@  0x1973d01
 testing::internal::HandleExceptionsInMethodIfSupported<>()
@  0x195b18b  testing::UnitTest::Run()
@   0xe43611  RUN_ALL_TESTS()
@   0xe424dc  main
@ 0x7fc45e147b45  (unknown)
@   0x8a0bbc  (unknown)


Looks like the memory cgroup memory is disabled:

admin@ip-172-31-26-151:~/mesos/build$ cat /proc/cgroups
#subsys_namehierarchy   num_cgroups enabled
cpuset  2   1   1
cpu 3   2   1
cpuacct 3   2   1
memory  0   1   0
devices 4   1   1
freezer 5   2   1
net_cls 6   1   1

But I thought the test filters should have caught this ?

On Fri, Mar 4, 2016 at 1:52 PM, Kapil Arya  wrote:

> +1 (Binding)
>
> Successful CI builds for the following distros:
>
> amd64/centos/6
> amd64/centos/7
> amd64/debian/jessie
> amd64/ubuntu/precise
> amd64/ubuntu/trusty
> amd64/ubuntu/vivid
>
>
> 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.
>> >>
>> >
>> >
>>
>
>


-- 
Avinash Sridharan, Mesosphere
+1 (323) 702 5245

NYC Meetup on Mar 9th

2016-03-04 Thread Vinod Kone 
Hi,

If you are in the NYC area and are a Mesos enthusiast, you might be
interested in the upcoming meetup in NYC.

Please visit http://www.meetup.com/Apache-Mesos-NYC-Meetup/events/229086077/
for more details.

Looking forward to the meetup,
Vinod

P.S: @MPark, can you please add this to our events calendar?

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-03-04 Thread Joris Van Remoortere 
+1 (binding)

On Mon, Feb 29, 2016 at 3:24 PM, Greg Mann  wrote:

> +1 (non-binding)
>
> `sudo make check` on Ubuntu 14.04, using gcc with libevent and SSL enabled.
> All tests pass except MemoryPressureMesosTest.CGROUPS_ROOT_Statistics,
> which is a known failure in 0.24.
>
> Cheers,
> Greg
>
>
> On Mon, Feb 29, 2016 at 11:20 AM, Kapil Arya  wrote:
>
> > +1 (binding)
> >
> > Successful CI builds for the following distros:
> >
> > amd64/centos/6
> > amd64/centos/7
> > amd64/debian/jessie
> > amd64/ubuntu/precise
> > amd64/ubuntu/trusty
> > amd64/ubuntu/vivid
> >
> > Kapil
> >
> > On Sat, Feb 27, 2016 at 1:12 AM, Michael Park  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-03-04 Thread Joris Van Remoortere 
+1 (binding)
Greg's upgrade scripts & CI results

On Fri, Mar 4, 2016 at 11:30 AM, Vinod Kone  wrote:

> +1 (binding)
>
> On Tue, Mar 1, 2016 at 5:03 PM, Kevin Klues  wrote:
>
> > I committed a fix for this in:
> >
> >
> https://github.com/apache/mesos/commit/42f746937233349660c687ea7a66cc0a78871663
> >
> > Looks like that's post 0.26 though, so maybe it should be included in the
> > .1 rc
> >
> > On Mon, Feb 29, 2016 at 2:27 PM, Vinod Kone 
> wrote:
> >
> >> Looks like the ASF CI builds for CentOS7 are failing because they are
> >> unable to find JAVA_HOME. Couldn't tell if it's an issue with the docker
> >> build script or something in the configure script.
> >>
> >>
> >> checking for svn_txdelta in -lsvn_delta-1... yes
> >> checking for sasl_done in -lsasl2... yes
> >> checking SASL CRAM-MD5 support... yes
> >> checking for javac... /usr/bin/javac
> >> checking for java... /usr/bin/java
> >> checking value of Java system property 'java.home'...
> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.71-2.b15.el7_2.x86_64/jre
> >> configure: error: could not guess JAVA_HOME
> >>
> >>
> >>
> >> *Revision*: a05261dbed1c2577676b11235380de95d586aeeb
> >>
> >>- refs/tags/0.26.1-rc1
> >>
> >> Configuration Matrix gcc clang
> >> centos:7 --verbose --enable-libevent --enable-ssl
> >> [image: Failed]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/8/COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,OS=centos%3A7,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/
> >
> >> [image: Not run]
> >> --verbose
> >> [image: Failed]
> >> <
> https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/8/COMPILER=gcc,CONFIGURATION=--verbose,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/8/COMPILER=gcc,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,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/8/COMPILER=clang,CONFIGURATION=--verbose%20--enable-libevent%20--enable-ssl,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/8/COMPILER=gcc,CONFIGURATION=--verbose,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/8/COMPILER=clang,CONFIGURATION=--verbose,OS=ubuntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)/
> >
> >>
> >> On Mon, Feb 29, 2016 at 11:21 AM, Kapil Arya 
> wrote:
> >>
> >>> +1 (binding)
> >>>
> >>> Successful CI builds for the following distros:
> >>>
> >>> amd64/centos/6
> >>> amd64/centos/7
> >>> amd64/debian/jessie
> >>> amd64/ubuntu/precise
> >>> amd64/ubuntu/trusty
> >>> amd64/ubuntu/vivid
> >>>
> >>> Kapil
> >>>
> >>> On Sat, Feb 27, 2016 at 12: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
>

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

2016-03-04 Thread Vinod Kone 
+1 (binding)

On Tue, Mar 1, 2016 at 5:03 PM, Kevin Klues  wrote:

> I committed a fix for this in:
>
> https://github.com/apache/mesos/commit/42f746937233349660c687ea7a66cc0a78871663
>
> Looks like that's post 0.26 though, so maybe it should be included in the
> .1 rc
>
> On Mon, Feb 29, 2016 at 2:27 PM, Vinod Kone  wrote:
>
>> Looks like the ASF CI builds for CentOS7 are failing because they are
>> unable to find JAVA_HOME. Couldn't tell if it's an issue with the docker
>> build script or something in the configure script.
>>
>>
>> checking for svn_txdelta in -lsvn_delta-1... yes
>> checking for sasl_done in -lsasl2... yes
>> checking SASL CRAM-MD5 support... yes
>> checking for javac... /usr/bin/javac
>> checking for java... /usr/bin/java
>> checking value of Java system property 'java.home'... 
>> /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.71-2.b15.el7_2.x86_64/jre
>> configure: error: could not guess JAVA_HOME
>>
>>
>>
>> *Revision*: a05261dbed1c2577676b11235380de95d586aeeb
>>
>>- refs/tags/0.26.1-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, Feb 29, 2016 at 11:21 AM, Kapil Arya  wrote:
>>
>>> +1 (binding)
>>>
>>> Successful CI builds for the following distros:
>>>
>>> amd64/centos/6
>>> amd64/centos/7
>>> amd64/debian/jessie
>>> amd64/ubuntu/precise
>>> amd64/ubuntu/trusty
>>> amd64/ubuntu/vivid
>>>
>>> Kapil
>>>
>>> On Sat, Feb 27, 2016 at 12: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

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

2016-03-04 Thread Jie Yu 
I will rename mesos-provisioner.md -> container-image.md, and do some
re-writing.

- Jie

On Fri, Mar 4, 2016 at 10:35 AM, Jie Yu  wrote:

> I am writing that as you speaking
>
> On Fri, Mar 4, 2016 at 10:34 AM, Vinod Kone  wrote:
>
>> I think this was supposed to refer to
>> https://github.com/apache/mesos/blob/master/docs/mesos-containerizer.md
>>
>> @Jie ^^ ?
>>
>> On Fri, Mar 4, 2016 at 10:29 AM, Steven Schlansker <
>> sschlans...@opentable.com> wrote:
>>
>>>
>>> > On Mar 3, 2016, at 5:43 PM, Vinod Kone  wrote:
>>> >
>>> > Hi all,
>>> > Please vote on releasing the following candidate as Apache Mesos
>>> 0.28.0.
>>> > 0.28.0 includes the following:
>>> > ...
>>> >   * [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.
>>>
>>> As of commit 46dcae5, there doesn't seem to be any such documentation?
>>> I'm excited to try this feature out :)
>>>
>>> https://github.com/apache/mesos/blob/master/docs/container-image.md
>>> (404)
>>>
>>>
>>
>

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

2016-03-04 Thread Jie Yu 
I am writing that as you speaking

On Fri, Mar 4, 2016 at 10:34 AM, Vinod Kone  wrote:

> I think this was supposed to refer to
> https://github.com/apache/mesos/blob/master/docs/mesos-containerizer.md
>
> @Jie ^^ ?
>
> On Fri, Mar 4, 2016 at 10:29 AM, Steven Schlansker <
> sschlans...@opentable.com> wrote:
>
>>
>> > On Mar 3, 2016, at 5:43 PM, Vinod Kone  wrote:
>> >
>> > Hi all,
>> > Please vote on releasing the following candidate as Apache Mesos 0.28.0.
>> > 0.28.0 includes the following:
>> > ...
>> >   * [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.
>>
>> As of commit 46dcae5, there doesn't seem to be any such documentation?
>> I'm excited to try this feature out :)
>>
>> https://github.com/apache/mesos/blob/master/docs/container-image.md (404)
>>
>>
>

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

2016-03-04 Thread Vinod Kone 
I think this was supposed to refer to
https://github.com/apache/mesos/blob/master/docs/mesos-containerizer.md

@Jie ^^ ?

On Fri, Mar 4, 2016 at 10:29 AM, Steven Schlansker <
sschlans...@opentable.com> wrote:

>
> > On Mar 3, 2016, at 5:43 PM, Vinod Kone  wrote:
> >
> > Hi all,
> > Please vote on releasing the following candidate as Apache Mesos 0.28.0.
> > 0.28.0 includes the following:
> > ...
> >   * [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.
>
> As of commit 46dcae5, there doesn't seem to be any such documentation?
> I'm excited to try this feature out :)
>
> https://github.com/apache/mesos/blob/master/docs/container-image.md (404)
>
>

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

2016-03-04 Thread Steven Schlansker 

> On Mar 3, 2016, at 5:43 PM, Vinod Kone  wrote:
> 
> Hi all,
> Please vote on releasing the following candidate as Apache Mesos 0.28.0.
> 0.28.0 includes the following:
> ...
>   * [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.

As of commit 46dcae5, there doesn't seem to be any such documentation?
I'm excited to try this feature out :)

https://github.com/apache/mesos/blob/master/docs/container-image.md (404)



signature.asc
Description: Message signed with OpenPGP using GPGMail

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

2016-03-04 Thread Vinod Kone 
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: Run mesos slave on coreos

2016-03-04 Thread Taylor, Graham 
Check this out 
https://github.com/Capgemini/Apollo/blob/devel/roles/mesos/templates/mesos-slave.service.j2

We run our stack on CoreOS.

Thanks,
Graham.

On 4 Mar 2016, at 12:00, Krish 
> wrote:

Hi,
I am trying to run mesos slave in a docker container on coreos and am stuck at 
libsasl2 dependency.
When I run an aurora job on it, I get this stacktrace in the sandbox stderr:

Traceback (most recent call last):
  File "apache/aurora/executor/bin/thermos_executor_main.py", line 45, in 

from mesos.native import MesosExecutorDriver
  File 
"/root/.pex/install/mesos.native-0.24.1-py2.7-linux-x86_64.egg.c2a926cdb8d599d35c7a569171311edaebda9341/mesos.native-0.24.1-py2.7-linux-x86_64.egg/mesos/native/__init__.py",
 line 17, in 
from ._mesos import MesosExecutorDriverImpl
ImportError: libsasl2.so.2: cannot open shared object file: No such file or 
directory


Any help on how to get this dependency satisfied?
I tried installing libsasl2-dev inside the slave container. I am exposing the 
coreOS host docker socket to the slave for running this.


Also, I just stumbled upon this link by Alex from Mesosphere, where he mentions 
that one can run mesos-slave natively on coreos.
Ref: 
https://mail-archives.apache.org/mod_mbox/mesos-user/201503.mbox/%3CCACzFoUvRqNsVXVOFXnPzNM-QFu31BTTQaLTBGNcTtd=-opc...@mail.gmail.com%3E

Has anyone done that? Is there a document or can I get guidance as to how to 
get it done?
Which would be the recommended method - run slave as a container or natively in 
such a case?

Thanks.

--
κρισhναν



Capgemini is a trading name used by the Capgemini Group of companies which 
includes Capgemini UK plc, a company registered in England and Wales (number 
943935) whose registered office is at No. 1, Forge End, Woking, Surrey, GU21 
6DB.
This message contains information that may be privileged or confidential and is 
the property of the Capgemini Group. It is intended only for the person to whom 
it is addressed. If you are not the intended recipient, you are not authorized 
to read, print, retain, copy, disseminate, distribute, or use this message or 
any part thereof. If you receive this message in error, please notify the 
sender immediately and delete all copies of this message.

Re: Run mesos slave on coreos

2016-03-04 Thread Krish 
I hit this bug now: https://issues.apache.org/jira/browse/MESOS-3553
Even though I am exporting the LIBPROCESS_IP, my task fails the DNS
resolution and bails out.
Any chance this will be ported to 0.24.1?
In the meantime, any workarounds for this?



--
κρισhναν

On Fri, Mar 4, 2016 at 5:47 PM, Krish  wrote:

> Thanks Stephen! I did just that.
> Can you please let me know why is it needed in both containers - the slave
> container and the job container?
>
>
>
>
> --
> κρισhναν
>
> On Fri, Mar 4, 2016 at 5:30 PM, Erb, Stephan 
> wrote:
>
>> ​The Aurora executor runs within the container you want to launch. You
>> have to install libsasl in there and not just within the container running
>> the slave.
>>
>>
>> Regards,
>> Stephan
>> --
>> *From:* Krish 
>> *Sent:* Friday, March 4, 2016 12:57
>> *To:* user@mesos.apache.org
>> *Subject:* Run mesos slave on coreos
>>
>> Hi,
>> I am trying to run mesos slave in a docker container on coreos and am
>> stuck at libsasl2 dependency.
>> When I run an aurora job on it, I get this stacktrace in the sandbox
>> stderr:
>>
>> Traceback (most recent call last):
>>   File "apache/aurora/executor/bin/thermos_executor_main.py", line 45, in
>> 
>> from mesos.native import MesosExecutorDriver
>>   File
>> "/root/.pex/install/mesos.native-0.24.1-py2.7-linux-x86_64.egg.c2a926cdb8d599d35c7a569171311edaebda9341/mesos.native-0.24.1-py2.7-linux-x86_64.egg/mesos/native/__init__.py",
>> line 17, in 
>> from ._mesos import MesosExecutorDriverImpl
>> ImportError: libsasl2.so.2: cannot open shared object file: No such file
>> or directory
>>
>>
>> Any help on how to get this dependency satisfied?
>> I tried installing libsasl2-dev inside the slave container. I am exposing
>> the coreOS host docker socket to the slave for running this.
>>
>>
>> Also, I just stumbled upon this link by Alex from Mesosphere, where he
>> mentions that one can run mesos-slave natively on coreos.
>> Ref:
>> https://mail-archives.apache.org/mod_mbox/mesos-user/201503.mbox/%3CCACzFoUvRqNsVXVOFXnPzNM-QFu31BTTQaLTBGNcTtd=-opc...@mail.gmail.com%3E
>>
>> Has anyone done that? Is there a document or can I get guidance as to how
>> to get it done?
>> Which would be the recommended method - run slave as a container or
>> natively in such a case?
>>
>> Thanks.
>>
>> --
>> κρισhναν
>>
>
>

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

2016-03-04 Thread Shuai Lin 
>
>   * [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.
>