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

[Vinod Kone]

Thanks Yan. I will release 1.0 and call out the known issues. We will start
the prep for a 1.0.1 later this week.

On Tue, Jul 26, 2016 at 7:32 PM, Yan Xu  wrote:

> I am OK with withdrawing -1 but I feel it's more prudent to go with 1b) or
> 2c) or the reason Jie mentioned. If we go with 1a) let's make sure we call
> out the known issue.
>
> > On Jul 26, 2016, at 7:09 PM, Adam Bordelon  wrote:
> >
> > I don't like the idea of 2) bypassing the 72 hour voting period, so I'd
> > suggest either we:
> > 1a) ask Yan to cancel his -1 so we can cut 1.0.0 today and blog about it,
> > then cut 1.0.1 soon after with this and other fixes.
> > 1b) cut an rc5 now and the blogs posted tomorrow mention the rc rather
> than
> > an official release. After 72hrs we can hopefully call rc5 the official
> 1.0
> > (or maybe more blockers come up). We could have more blogs/press then
> about
> > the official 1.0 release.
> > 1c) push the press releases and announcements out a few more days. Not
> sure
> > if this is possible at this point?
> > I'd prefer 1c) if possible, or a/b otherwise.
> >
> > On Tue, Jul 26, 2016 at 6:52 PM, Benjamin Hindman <
> > benjamin.hind...@gmail.com> wrote:
> >
> >> I agree with Vinod that we should go with option 1. I think redirect is
> a
> >> valuable feature but it's not imperative for the operation of the
> cluster.
> >>
> >> On Tue, Jul 26, 2016 at 5:39 PM, Vinod Kone 
> 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  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  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  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  wrote:
> 
>  +1 (binding)
> 
>  OpenSUSE Tumbleweed:
>    ./configure --disable-java --disable-python && make check
> 
>  On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li 
>  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  >
>  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 
> 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  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 
> 
>  wrote:
> 
> 
>  One can find t

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

[Yan Xu]

I am OK with withdrawing -1 but I feel it's more prudent to go with 1b) or 2c) 
or the reason Jie mentioned. If we go with 1a) let's make sure we call out the 
known issue.

> On Jul 26, 2016, at 7:09 PM, Adam Bordelon  wrote:
> 
> I don't like the idea of 2) bypassing the 72 hour voting period, so I'd
> suggest either we:
> 1a) ask Yan to cancel his -1 so we can cut 1.0.0 today and blog about it,
> then cut 1.0.1 soon after with this and other fixes.
> 1b) cut an rc5 now and the blogs posted tomorrow mention the rc rather than
> an official release. After 72hrs we can hopefully call rc5 the official 1.0
> (or maybe more blockers come up). We could have more blogs/press then about
> the official 1.0 release.
> 1c) push the press releases and announcements out a few more days. Not sure
> if this is possible at this point?
> I'd prefer 1c) if possible, or a/b otherwise.
> 
> On Tue, Jul 26, 2016 at 6:52 PM, Benjamin Hindman <
> benjamin.hind...@gmail.com> wrote:
> 
>> I agree with Vinod that we should go with option 1. I think redirect is a
>> valuable feature but it's not imperative for the operation of the cluster.
>> 
>> On Tue, Jul 26, 2016 at 5:39 PM, Vinod Kone  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  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  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  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  wrote:
 
 +1 (binding)
 
 OpenSUSE Tumbleweed:
   ./configure --disable-java --disable-python && make check
 
 On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li 
 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 
 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  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  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 
 
 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 
 
 wrote:
>

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

[Adam Bordelon]

I don't like the idea of 2) bypassing the 72 hour voting period, so I'd
suggest either we:
1a) ask Yan to cancel his -1 so we can cut 1.0.0 today and blog about it,
then cut 1.0.1 soon after with this and other fixes.
1b) cut an rc5 now and the blogs posted tomorrow mention the rc rather than
an official release. After 72hrs we can hopefully call rc5 the official 1.0
(or maybe more blockers come up). We could have more blogs/press then about
the official 1.0 release.
1c) push the press releases and announcements out a few more days. Not sure
if this is possible at this point?
I'd prefer 1c) if possible, or a/b otherwise.

On Tue, Jul 26, 2016 at 6:52 PM, Benjamin Hindman <
benjamin.hind...@gmail.com> wrote:

> I agree with Vinod that we should go with option 1. I think redirect is a
> valuable feature but it's not imperative for the operation of the cluster.
>
> On Tue, Jul 26, 2016 at 5:39 PM, Vinod Kone  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  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  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  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  wrote:
>>>
>>> +1 (binding)
>>>
>>> OpenSUSE Tumbleweed:
>>>./configure --disable-java --disable-python && make check
>>>
>>> On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li 
>>> 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 
>>> 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  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  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 
>>>
>>> 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 
>>>
>>> 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 v

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

[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  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  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  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  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  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  wrote:
>>
>> +1 (binding)
>>
>> OpenSUSE Tumbleweed:
>>./configure --disable-java --disable-python && make check
>>
>> On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li  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 
>> 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  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  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 
>>
>> 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 
>>
>> 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] - **Exper

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

[Jie Yu]

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  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  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  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  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  wrote:
 
 +1 (binding)
 
 OpenSUSE Tumbleweed:
./configure --disable-java --disable-python && make check
 
> On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li  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 
> 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  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  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 
>> 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 
> 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 ma

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

[Benjamin Hindman]

I agree with Vinod that we should go with option 1. I think redirect is a
valuable feature but it's not imperative for the operation of the cluster.

On Tue, Jul 26, 2016 at 5:39 PM, Vinod Kone  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  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  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  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  wrote:
>>
>> +1 (binding)
>>
>> OpenSUSE Tumbleweed:
>>./configure --disable-java --disable-python && make check
>>
>> On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li  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 
>> 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  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  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 
>>
>> 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 
>>
>> 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

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

[Vinod Kone]

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  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  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  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  wrote:
>
> +1 (binding)
>
> OpenSUSE Tumbleweed:
>./configure --disable-java --disable-python && make check
>
> On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li  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 
> 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  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  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 
>
> 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 
>
> 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
>

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

[Yan Xu]

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  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  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  wrote:
>> 
>> +1 (binding)
>> 
>> OpenSUSE Tumbleweed:
>>./configure --disable-java --disable-python && make check
>> 
>> On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li  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 
>>> 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  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  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 
 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 
>> 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.
 
 
 

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

[Jie Yu]

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  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  wrote:
>
> +1 (binding)
>
> OpenSUSE Tumbleweed:
> ./configure --disable-java --disable-python && make check
>
> On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li  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 
>> 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  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  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 
>>> 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 
>>> >> 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

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

[Yan Xu]

-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  wrote:
> 
> +1 (binding)
> 
> OpenSUSE Tumbleweed:
> ./configure --disable-java --disable-python && make check
> 
> On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li  > 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  > 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  > 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  > > 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  >> > 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  >> > >
> >> 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 

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

[Kapil Arya]

+1 (binding)

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

On Tue, Jul 26, 2016 at 4:44 PM, Zhitao Li  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 
> 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  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  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 
>> 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 
>> >> 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
>> >> > >
>

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

[Zhitao Li]

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

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

[Benjamin Mahler]

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

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

[Greg Mann]

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

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

[Jie Yu]

+1

sudo make check on CentOS 6/7, Debian 8, Fedora 23, Ubuntu 12/14/15/16

- Jie

On Tue, Jul 26, 2016 at 1:58 AM, haosdent  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  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  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 

Announcing the #MesosCon Europe Schedule!

[David Greenberg]

Join us August 31st-September 1st in the lovely Hilton Amsterdam (in
Amsterdam, if the name didn't clue you in) for #MesosCon Europe! Our
schedule is now available online:
http://events.linuxfoundation.org/events/mesoscon-europe/program/schedule

We've got 3 information-packed days about Mesos coming up:

- Hear from Vinod Kone about Mesos 1.0
- Learn about Netflix's experiences migrating to Mesos
- Understand how Apple scales Mesos

Plus dozens of other great talks!

After 2 full days of awesome talks, get ready for the Mesos hackathon!
Whether you're an experienced contributor or just getting started, you'll
be able to learn and hack on a project in a team of up to 4 people.
Projects can be anything related to Mesos--tutorials, documentation,
interesting integrations, or features you've been dying to see. As always,
plan on really cool prizes: in the past, we've had Apple Watches and Amazon
Echoes.

See you there!

David Greenberg, Kiersten Gaffney, Chris Schaefer
MesosCon Program Committee Chairs

Re: docker 'expose' integration

[haosdent]

You need to define `PortMapping` in your `ContainerInfo`
https://github.com/apache/mesos/blob/77f82510b3bbaf62e0b7d9d2eea20fdc3fd706b7/include/mesos/mesos.proto#L1894-L1901

On Tue, Jul 26, 2016 at 10:22 PM, Gogineni, Tarun 
wrote:

> Hi,
>
>
> Does the Docker integration support the EXPOSE directive in Dockerfiles?
>
>
> What must be done in order to network docker containers properly? (Esp.
> with the Aurora framework)
>
>
>
> Thank you!
>
>
>


-- 
Best Regards,
Haosdent Huang

docker 'expose' integration

[Gogineni, Tarun]

Hi,


Does the Docker integration support the EXPOSE directive in Dockerfiles?


What must be done in order to network docker containers properly? (Esp. with 
the Aurora framework)



Thank you!

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

[haosdent]

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