You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Benjamin Mahler <be...@gmail.com> on 2014/05/30 18:48:50 UTC
0.19.0 Testing
Hi All,
I've pushed a tag for the first release candidate for 0.19.0: 0.19.0-rc1
I would like to ask others to assist in testing this candidate so that we can catch anything obvious before the vote!
Thanks,
Ben
Re: 0.19.0 Testing
Posted by Ian Downes <id...@twitter.com.INVALID>.
I just discovered a bug when using the recently added --slave_subsystems flag which erroneously tries to destroy the slave cgroup during recovery. It affects both the MesosContainerizer and the ExternalContainerizer. The fix should be considered for cherry picking onto 0.19.0. See MESOS-1449.
On Jun 2, 2014, at 11:54 AM, Benjamin Mahler <be...@gmail.com> wrote:
> The target of the end of this week is nice because we can have the new
> release out by the start of dockercon. I will make sure this is tested in a
> production environment at least at Twitter before calling the vote. Would
> appreciate others pitching in as well.
>
> If there is anyone that would like to have more time to vet this release
> please chime in! For External Containerizer related bugs, I would prefer to
> follow up with 0.19.x bug fix releases through Till or Niklas.
Re: 0.19.0 Testing
Posted by Benjamin Mahler <be...@gmail.com>.
Tagging 0.19.0-rc3 with the following three trivial cherry-picks off master:
* 4feeb9e Ignore slave cgroup during isolator recovery.
* ff8f287 Fixed a segfault in libprocess.
* aa5d491 Updated CHANGELOG for 0.19.0.
Here's what it looks like off of rc2:
* 51e0475 (HEAD) Updated CHANGELOG for 0.19.0.
* 8dfabce Fixed a segfault in libprocess.
* 83e2459 Ignore slave cgroup during isolator recovery.
* 96ffd0a (tag: 0.19.0-rc2) Updated the upgrades document for 0.19.0.
On Wed, Jun 4, 2014 at 1:23 PM, Benjamin Mahler <be...@gmail.com>
wrote:
> There's also a regression in libprocess that I'll get fixed:
> https://issues.apache.org/jira/browse/MESOS-1455
>
>
> On Mon, Jun 2, 2014 at 12:03 PM, Tom Arnfeld <to...@duedil.com> wrote:
>
>> That's exciting! I'd also love if anyone could try out the Docker
>> Containerizer I've been working on...
>> https://github.com/duedil-ltd/mesos-docker-containerizer (The deimos
>> project from mesosphere isn't compatible with the EC release
>> candidate, or not any version I could find).
>>
>> I'm in the process of deploying it to a pre-production cluster here at
>> DueDil (pretty small scale though, 156cpus) to test it out.
>>
>> Looking forward to the release!
>>
>> Tom.
>>
>> > On 2 Jun 2014, at 19:55, Benjamin Mahler <be...@gmail.com>
>> wrote:
>> >
>> > The target of the end of this week is nice because we can have the new
>> > release out by the start of dockercon. I will make sure this is tested
>> in a
>> > production environment at least at Twitter before calling the vote.
>> Would
>> > appreciate others pitching in as well.
>> >
>> > If there is anyone that would like to have more time to vet this release
>> > please chime in! For External Containerizer related bugs, I would
>> prefer to
>> > follow up with 0.19.x bug fix releases through Till or Niklas.
>>
>
>
Re: 0.19.0 Testing
Posted by Benjamin Mahler <be...@gmail.com>.
There's also a regression in libprocess that I'll get fixed:
https://issues.apache.org/jira/browse/MESOS-1455
On Mon, Jun 2, 2014 at 12:03 PM, Tom Arnfeld <to...@duedil.com> wrote:
> That's exciting! I'd also love if anyone could try out the Docker
> Containerizer I've been working on...
> https://github.com/duedil-ltd/mesos-docker-containerizer (The deimos
> project from mesosphere isn't compatible with the EC release
> candidate, or not any version I could find).
>
> I'm in the process of deploying it to a pre-production cluster here at
> DueDil (pretty small scale though, 156cpus) to test it out.
>
> Looking forward to the release!
>
> Tom.
>
> > On 2 Jun 2014, at 19:55, Benjamin Mahler <be...@gmail.com>
> wrote:
> >
> > The target of the end of this week is nice because we can have the new
> > release out by the start of dockercon. I will make sure this is tested
> in a
> > production environment at least at Twitter before calling the vote. Would
> > appreciate others pitching in as well.
> >
> > If there is anyone that would like to have more time to vet this release
> > please chime in! For External Containerizer related bugs, I would prefer
> to
> > follow up with 0.19.x bug fix releases through Till or Niklas.
>
Re: 0.19.0 Testing
Posted by Tom Arnfeld <to...@duedil.com>.
That's exciting! I'd also love if anyone could try out the Docker
Containerizer I've been working on...
https://github.com/duedil-ltd/mesos-docker-containerizer (The deimos
project from mesosphere isn't compatible with the EC release
candidate, or not any version I could find).
I'm in the process of deploying it to a pre-production cluster here at
DueDil (pretty small scale though, 156cpus) to test it out.
Looking forward to the release!
Tom.
> On 2 Jun 2014, at 19:55, Benjamin Mahler <be...@gmail.com> wrote:
>
> The target of the end of this week is nice because we can have the new
> release out by the start of dockercon. I will make sure this is tested in a
> production environment at least at Twitter before calling the vote. Would
> appreciate others pitching in as well.
>
> If there is anyone that would like to have more time to vet this release
> please chime in! For External Containerizer related bugs, I would prefer to
> follow up with 0.19.x bug fix releases through Till or Niklas.
Re: 0.19.0 Testing
Posted by Benjamin Mahler <be...@gmail.com>.
The target of the end of this week is nice because we can have the new
release out by the start of dockercon. I will make sure this is tested in a
production environment at least at Twitter before calling the vote. Would
appreciate others pitching in as well.
If there is anyone that would like to have more time to vet this release
please chime in! For External Containerizer related bugs, I would prefer to
follow up with 0.19.x bug fix releases through Till or Niklas.
Re: 0.19.0 Testing
Posted by Dave Lester <da...@gmail.com>.
Is it possible that we're rushing a release here? Could we offer a few
additional business days of testing before voting on this RC?
It seems that in the past, bugs in release candidates have been caught
shortly after voting. It'd be nice to either: extend the voting period to
accomodate testing within that period, or offer a standard period of
testing (measured in business days) prior to a vote.
Best,
Dave
On Fri, May 30, 2014 at 6:02 PM, Benjamin Mahler <be...@gmail.com>
wrote:
> Pushed the tag for 0.19.0-rc2 with the above changes, note that for bug
> finding purposes it is functionally equivalent.
>
>
> On Fri, May 30, 2014 at 5:55 PM, Benjamin Mahler <
> benjamin.mahler@gmail.com>
> wrote:
>
> > There's going to at least be a second release candidate to capture the
> > following:
> >
> > 1. configure.ac actually had 0.20.0 instead of 0.19.0 on the cut (thanks
> > Adam!)
> > 2. CHANGELOG and upgrade document for 0.19.0.
> > 3. cherry-pick of d903e7d to disable the no-op acl flag.
> >
> > But semantically, you can continue to test out 0.19.0-rc1 for bugs since
> > these changes do not affect functionality.
> >
> >
> > On Fri, May 30, 2014 at 2:56 PM, Benjamin Mahler <
> > benjamin.mahler@gmail.com> wrote:
> >
> >> Hey Tom,
> >>
> >> I would like to aim for the release to be published by the end of next
> >> week. This will give us time to make sure the rc is stable. I'll be
> calling
> >> a vote early next week.
> >>
> >> For the external containerizer (EC) (+ Deimos), since it is an 'alpha'
> >> feature, we'll likely want to follow up with bugfix releases there
> (0.19.1,
> >> ...).
> >>
> >>
> >> On Fri, May 30, 2014 at 9:50 AM, Tom Arnfeld <to...@duedil.com> wrote:
> >>
> >>> Hey Ben,
> >>>
> >>> When’s the vote going out? I’m in the process of deploying 0.19.0-rc1
> >>> (and testing with Deimos) to our pre-production cluster to see how it
> goes…
> >>> will report back if I find anything odd.
> >>>
> >>> Tom.
> >>>
> >>> On 30 May 2014, at 17:48, Benjamin Mahler <be...@gmail.com>
> >>> wrote:
> >>>
> >>> > Hi All,
> >>> >
> >>> > I've pushed a tag for the first release candidate for 0.19.0:
> >>> 0.19.0-rc1
> >>> >
> >>> > I would like to ask others to assist in testing this candidate so
> that
> >>> we can catch anything obvious before the vote!
> >>> >
> >>> > Thanks,
> >>> > Ben
> >>>
> >>>
> >>
> >
>
Re: 0.19.0 Testing
Posted by Benjamin Mahler <be...@gmail.com>.
Pushed the tag for 0.19.0-rc2 with the above changes, note that for bug
finding purposes it is functionally equivalent.
On Fri, May 30, 2014 at 5:55 PM, Benjamin Mahler <be...@gmail.com>
wrote:
> There's going to at least be a second release candidate to capture the
> following:
>
> 1. configure.ac actually had 0.20.0 instead of 0.19.0 on the cut (thanks
> Adam!)
> 2. CHANGELOG and upgrade document for 0.19.0.
> 3. cherry-pick of d903e7d to disable the no-op acl flag.
>
> But semantically, you can continue to test out 0.19.0-rc1 for bugs since
> these changes do not affect functionality.
>
>
> On Fri, May 30, 2014 at 2:56 PM, Benjamin Mahler <
> benjamin.mahler@gmail.com> wrote:
>
>> Hey Tom,
>>
>> I would like to aim for the release to be published by the end of next
>> week. This will give us time to make sure the rc is stable. I'll be calling
>> a vote early next week.
>>
>> For the external containerizer (EC) (+ Deimos), since it is an 'alpha'
>> feature, we'll likely want to follow up with bugfix releases there (0.19.1,
>> ...).
>>
>>
>> On Fri, May 30, 2014 at 9:50 AM, Tom Arnfeld <to...@duedil.com> wrote:
>>
>>> Hey Ben,
>>>
>>> When’s the vote going out? I’m in the process of deploying 0.19.0-rc1
>>> (and testing with Deimos) to our pre-production cluster to see how it goes…
>>> will report back if I find anything odd.
>>>
>>> Tom.
>>>
>>> On 30 May 2014, at 17:48, Benjamin Mahler <be...@gmail.com>
>>> wrote:
>>>
>>> > Hi All,
>>> >
>>> > I've pushed a tag for the first release candidate for 0.19.0:
>>> 0.19.0-rc1
>>> >
>>> > I would like to ask others to assist in testing this candidate so that
>>> we can catch anything obvious before the vote!
>>> >
>>> > Thanks,
>>> > Ben
>>>
>>>
>>
>
Re: 0.19.0 Testing
Posted by Benjamin Mahler <be...@gmail.com>.
There's going to at least be a second release candidate to capture the
following:
1. configure.ac actually had 0.20.0 instead of 0.19.0 on the cut (thanks
Adam!)
2. CHANGELOG and upgrade document for 0.19.0.
3. cherry-pick of d903e7d to disable the no-op acl flag.
But semantically, you can continue to test out 0.19.0-rc1 for bugs since
these changes do not affect functionality.
On Fri, May 30, 2014 at 2:56 PM, Benjamin Mahler <be...@gmail.com>
wrote:
> Hey Tom,
>
> I would like to aim for the release to be published by the end of next
> week. This will give us time to make sure the rc is stable. I'll be calling
> a vote early next week.
>
> For the external containerizer (EC) (+ Deimos), since it is an 'alpha'
> feature, we'll likely want to follow up with bugfix releases there (0.19.1,
> ...).
>
>
> On Fri, May 30, 2014 at 9:50 AM, Tom Arnfeld <to...@duedil.com> wrote:
>
>> Hey Ben,
>>
>> When’s the vote going out? I’m in the process of deploying 0.19.0-rc1
>> (and testing with Deimos) to our pre-production cluster to see how it goes…
>> will report back if I find anything odd.
>>
>> Tom.
>>
>> On 30 May 2014, at 17:48, Benjamin Mahler <be...@gmail.com>
>> wrote:
>>
>> > Hi All,
>> >
>> > I've pushed a tag for the first release candidate for 0.19.0: 0.19.0-rc1
>> >
>> > I would like to ask others to assist in testing this candidate so that
>> we can catch anything obvious before the vote!
>> >
>> > Thanks,
>> > Ben
>>
>>
>
Re: 0.19.0 Testing
Posted by Benjamin Mahler <be...@gmail.com>.
Hey Tom,
I would like to aim for the release to be published by the end of next
week. This will give us time to make sure the rc is stable. I'll be calling
a vote early next week.
For the external containerizer (EC) (+ Deimos), since it is an 'alpha'
feature, we'll likely want to follow up with bugfix releases there (0.19.1,
...).
On Fri, May 30, 2014 at 9:50 AM, Tom Arnfeld <to...@duedil.com> wrote:
> Hey Ben,
>
> When’s the vote going out? I’m in the process of deploying 0.19.0-rc1 (and
> testing with Deimos) to our pre-production cluster to see how it goes… will
> report back if I find anything odd.
>
> Tom.
>
> On 30 May 2014, at 17:48, Benjamin Mahler <be...@gmail.com>
> wrote:
>
> > Hi All,
> >
> > I've pushed a tag for the first release candidate for 0.19.0: 0.19.0-rc1
> >
> > I would like to ask others to assist in testing this candidate so that
> we can catch anything obvious before the vote!
> >
> > Thanks,
> > Ben
>
>
Re: 0.19.0 Testing
Posted by Vinod Kone <vi...@gmail.com>.
just cherry pick this commit instead.
d903e7d32040f5be070f158e21c674deb6230540
On Fri, May 30, 2014 at 1:41 PM, Benjamin Hindman <be...@eecs.berkeley.edu>
wrote:
> In general, I think it's okay to ship some features that are 'alpha' or
> even incomplete. Rather than reverting the commit I wonder if it would be
> better just to call out these features as such.
>
>
> On Fri, May 30, 2014 at 12:46 PM, Vinod Kone <vi...@gmail.com> wrote:
>
> > Lets revert the following commit because authorization is not ready yet
> and
> > exposing the "acls" flag will be misleading.
> >
> > commit 0dda8220396fbb788f25a0f08dd3ab39e6879bd9
> >
> > Author: Vinod Kone <vi...@twitter.com>
> >
> > Date: Fri May 16 14:37:28 2014 -0700
> >
> >
> > Integrate Authorizer into Master.
> >
> >
> >
> > Review: https://reviews.apache.org/r/21723
> >
> >
> > On Fri, May 30, 2014 at 9:50 AM, Tom Arnfeld <to...@duedil.com> wrote:
> >
> > > Hey Ben,
> > >
> > > When’s the vote going out? I’m in the process of deploying 0.19.0-rc1
> > (and
> > > testing with Deimos) to our pre-production cluster to see how it goes…
> > will
> > > report back if I find anything odd.
> > >
> > > Tom.
> > >
> > > On 30 May 2014, at 17:48, Benjamin Mahler <be...@gmail.com>
> > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > I've pushed a tag for the first release candidate for 0.19.0:
> > 0.19.0-rc1
> > > >
> > > > I would like to ask others to assist in testing this candidate so
> that
> > > we can catch anything obvious before the vote!
> > > >
> > > > Thanks,
> > > > Ben
> > >
> > >
> >
>
Re: 0.19.0 Testing
Posted by Benjamin Hindman <be...@eecs.berkeley.edu>.
In general, I think it's okay to ship some features that are 'alpha' or
even incomplete. Rather than reverting the commit I wonder if it would be
better just to call out these features as such.
On Fri, May 30, 2014 at 12:46 PM, Vinod Kone <vi...@gmail.com> wrote:
> Lets revert the following commit because authorization is not ready yet and
> exposing the "acls" flag will be misleading.
>
> commit 0dda8220396fbb788f25a0f08dd3ab39e6879bd9
>
> Author: Vinod Kone <vi...@twitter.com>
>
> Date: Fri May 16 14:37:28 2014 -0700
>
>
> Integrate Authorizer into Master.
>
>
>
> Review: https://reviews.apache.org/r/21723
>
>
> On Fri, May 30, 2014 at 9:50 AM, Tom Arnfeld <to...@duedil.com> wrote:
>
> > Hey Ben,
> >
> > When’s the vote going out? I’m in the process of deploying 0.19.0-rc1
> (and
> > testing with Deimos) to our pre-production cluster to see how it goes…
> will
> > report back if I find anything odd.
> >
> > Tom.
> >
> > On 30 May 2014, at 17:48, Benjamin Mahler <be...@gmail.com>
> > wrote:
> >
> > > Hi All,
> > >
> > > I've pushed a tag for the first release candidate for 0.19.0:
> 0.19.0-rc1
> > >
> > > I would like to ask others to assist in testing this candidate so that
> > we can catch anything obvious before the vote!
> > >
> > > Thanks,
> > > Ben
> >
> >
>
Re: 0.19.0 Testing
Posted by Vinod Kone <vi...@gmail.com>.
Lets revert the following commit because authorization is not ready yet and
exposing the "acls" flag will be misleading.
commit 0dda8220396fbb788f25a0f08dd3ab39e6879bd9
Author: Vinod Kone <vi...@twitter.com>
Date: Fri May 16 14:37:28 2014 -0700
Integrate Authorizer into Master.
Review: https://reviews.apache.org/r/21723
On Fri, May 30, 2014 at 9:50 AM, Tom Arnfeld <to...@duedil.com> wrote:
> Hey Ben,
>
> When’s the vote going out? I’m in the process of deploying 0.19.0-rc1 (and
> testing with Deimos) to our pre-production cluster to see how it goes… will
> report back if I find anything odd.
>
> Tom.
>
> On 30 May 2014, at 17:48, Benjamin Mahler <be...@gmail.com>
> wrote:
>
> > Hi All,
> >
> > I've pushed a tag for the first release candidate for 0.19.0: 0.19.0-rc1
> >
> > I would like to ask others to assist in testing this candidate so that
> we can catch anything obvious before the vote!
> >
> > Thanks,
> > Ben
>
>
Re: 0.19.0 Testing
Posted by Tom Arnfeld <to...@duedil.com>.
Hey Ben,
When’s the vote going out? I’m in the process of deploying 0.19.0-rc1 (and testing with Deimos) to our pre-production cluster to see how it goes… will report back if I find anything odd.
Tom.
On 30 May 2014, at 17:48, Benjamin Mahler <be...@gmail.com> wrote:
> Hi All,
>
> I've pushed a tag for the first release candidate for 0.19.0: 0.19.0-rc1
>
> I would like to ask others to assist in testing this candidate so that we can catch anything obvious before the vote!
>
> Thanks,
> Ben