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

[Kevin Klues]

The list of patches to include in 0.28.0-rc2 are now being tracked by a JIRA:

https://issues.apache.org/jira/browse/MESOS-4915

On Thu, Mar 10, 2016 at 3:51 PM, Vinod Kone  wrote:
> I'll cut it first thing tomorrow. Whatever from kevin's list ablove gets in
> by tonight will get into rc2.
>
> On Thu, Mar 10, 2016 at 6:28 PM, Daniel Osborne <
> daniel.osbo...@metaswitch.com> wrote:
>
>> Kevin,
>>
>> When are you planning on cutting?
>>
>> I'm very keen to seeing 4370 get merged. It just needs some final fixes to
>> get past "Fix it, then ship it".
>>
>> Thanks,
>> Dan
>>
>>
>> -Original Message-
>> From: Kevin Klues [mailto:klue...@gmail.com]
>> Sent: Thursday, March 10, 2016 11:46 AM
>> To: user ; dev 
>> Subject: Re: [VOTE] Release Apache Mesos 0.28.0 (rc1)
>>
>> Updated list of patches to include in 0.28.0-rc2.  We are cutting the
>> release candidate today, so make sure your patches land soon if they
>> haven't already.
>>
>> Did I miss any?
>>
>> Committed:
>> Added documentation about container image support.
>> commit 7de8cdd4d8ed1d222fa03ea0d8fa6740c4a9f84b
>> https://reviews.apache.org/r/44414
>>
>> Fixed the logic for default docker cmd case.
>> commit e42f740ccb655c0478a3002c0b6fa90c1144f41c
>> https://reviews.apache.org/r/44468/
>>
>>
>> Still Under Review:
>> MESOS-4370 NetworkSettings.IPAddress field is deprectaed in Docker.
>> https://reviews.apache.org/r/43093/
>>
>> Fixed a bug that causes the task stuck in staging state.
>> https://reviews.apache.org/r/44435/
>>
>> Fixed http endpoint trigger two inverse offer calls.
>> https://reviews.apache.org/r/44258/
>>
>> Added support for "overlay" keyword.
>> https://reviews.apache.org/r/44421/
>>
>> Added document for overlayfs backend.
>> https://reviews.apache.org/r/44391/
>>
>> Add support for user-defined networks.
>> https://reviews.apache.org/r/42516/
>>
>> On Wed, Mar 9, 2016 at 5:50 PM, Guangya Liu  wrote:
>> > Tim,
>> >
>> > What about https://reviews.apache.org/r/42516/ for user-defined
>> > network in docker containerizer, the user defined network has been
>> > landed in docker for quite a while and it is better to enable mesos
>> > docker containerizer support this.
>> >
>> > Thanks,
>> >
>> > Guangya
>> >
>> > On Thu, Mar 10, 2016 at 2:00 AM, Kevin Klues  wrote:
>> >>
>> >> Tim,
>> >>
>> >> Is there a review other than the following for MESOS-4370?
>> >>
>> >> Restore Mesos' ability to extract Docker assigned IPs (still under
>> >> review):
>> >> https://reviews.apache.org/r/43093/
>> >>
>> >> If not, it was already on the list, but has not yet landed.
>> >>
>> >> On Wed, Mar 9, 2016 at 9:57 AM, Timothy Chen  wrote:
>> >> > Also like to include MESOS-4370 as it fixes IP Address look up
>> >> > logic and also unblocks users using custom Docker network.
>> >> >
>> >> > Tim
>> >> >
>> >> > On Wed, Mar 9, 2016 at 9:55 AM, Gilbert Song
>> >> > 
>> >> > wrote:
>> >> >> Hi Kevin,
>> >> >>
>> >> >> Please remove the the patch below from the list:
>> >> >> Implemented runtime isolator default cmd test (still under review).
>> >> >> https://reviews.apache.org/r/44469/
>> >> >>
>> >> >> Because the bug was fixed by patch #44468, the test should not be
>> >> >> considered as a block. I am updating MESOS-4888 and move the test
>> >> >> to a separate JIRA.
>> >> >>
>> >> >> Thanks,
>> >> >> Gilbert
>> >> >>
>> >> >> On Tue, Mar 8, 2016 at 2:43 PM, Kevin Klues 
>> wrote:
>> >> >>
>> >> >>> Here are the list of reviews/patches that have been called out in
>> >> >>> this thread for inclusion in 0.28.0-rc2.  Some of them are still
>> >> >>> under review and will need to land by Thursday to be included.
>> >> >>>
>> >> >>> Are there others?
>> >> >>>
>> >> >>> Jie's container image documentation (submitted):
>> >> >>> commit 7de8cdd4d8ed1d222fa03ea0d8fa6740c4a9f84b
>> >> >>> https://reviews.apache.org/r/44414
>> >> >>>
>> >> >>> Restore Mesos' ability to extract Docker assigned IPs (still
>> >> >>> under
>> >> >>> review):
>> >> >>> https://reviews.apache.org/r/43093/
>> >> >>>
>> >> >>> Fixed the logic for default docker cmd case (submitted).
>> >> >>> commit e42f740ccb655c0478a3002c0b6fa90c1144f41c
>> >> >>> https://reviews.apache.org/r/44468/
>> >> >>>
>> >> >>> Implemented runtime isolator default cmd test (still under review).
>> >> >>> https://reviews.apache.org/r/44469/
>> >> >>>
>> >> >>> Fixed a bug that causes the task stuck in staging state (still
>> >> >>> under review).
>> >> >>> https://reviews.apache.org/r/44435/
>> >> >>>
>> >> >>> On Tue, Mar 8, 2016 at 10:30 AM, Kevin Klues 
>> >> >>> wrote:
>> >> >>> > Yes, will do.
>> >> >>> >
>> >> >>> > On Tue, Mar 8, 2016 at 10:26 AM, Vinod Kone
>> >> >>> > 
>> >> >>> wrote:
>> >> >>> >> +kevin klues
>> >> >>> >>
>> >> >>> >> OK. I'm cancelling this vote since there are some show stopper
>> >> >>> >> issues
>> >> >>> that
>> >> >>> >> we need to cherry-pick. I'll cut another RC on Thursday.
>> >> >>> >>
>> >> >>> >> @shepherds: can you please make sure the blocker tickets are
>> >> >>> >>

Re: 0.27.2 RPMs

[Guillermo Rodriguez]

And the docker hub images? :)




 From: "Kapil Arya" 
Sent: Friday, March 11, 2016 11:30 AM
To: "user" 
Subject: Re: 0.27.2 RPMs
 Hi All,
 The 0.27.2 rpm/debian packages should now be in Mesosphere repositories.

 Best,
 Kapil

   On Thu, Mar 10, 2016 at 3:57 PM, Pradeep Chhetri 
 wrote:

Hello all,

I still don't see any Mesos 0.27.2 deb/rpm artifacts in the mesosphere 
repository. Is this expected ?

Thanks.On Mar 9, 2016 3:46 PM, "Rad Gruchalski"  
wrote:   Oh, cool, I was expecting some info here.
 Going to build one now :)







Kind regards,?
Radek Gruchalski
?   ra...@gruchalski.com?
de.linkedin.com/in/radgruchalski/

Confidentiality:
This communication is intended for the above-named person and may be 
confidential and/or legally privileged.
If it has come to you in error you must take no action based on it, nor must 
you copy or show it to anyone; please delete/destroy and inform the sender 
immediately.

On Wednesday, 9 March 2016 at 16:44, craig w wrote: I thought so based on 
the website: http://mesos.apache.org/blog/mesos-0-27-2-released/

Re: 0.27.2 RPMs

[Kapil Arya]

Hi All,

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

Best,
Kapil

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

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

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

[Vinod Kone]

I'll cut it first thing tomorrow. Whatever from kevin's list ablove gets in
by tonight will get into rc2.

On Thu, Mar 10, 2016 at 6:28 PM, Daniel Osborne <
daniel.osbo...@metaswitch.com> wrote:

> Kevin,
>
> When are you planning on cutting?
>
> I'm very keen to seeing 4370 get merged. It just needs some final fixes to
> get past "Fix it, then ship it".
>
> Thanks,
> Dan
>
>
> -Original Message-
> From: Kevin Klues [mailto:klue...@gmail.com]
> Sent: Thursday, March 10, 2016 11:46 AM
> To: user ; dev 
> Subject: Re: [VOTE] Release Apache Mesos 0.28.0 (rc1)
>
> Updated list of patches to include in 0.28.0-rc2.  We are cutting the
> release candidate today, so make sure your patches land soon if they
> haven't already.
>
> Did I miss any?
>
> Committed:
> Added documentation about container image support.
> commit 7de8cdd4d8ed1d222fa03ea0d8fa6740c4a9f84b
> https://reviews.apache.org/r/44414
>
> Fixed the logic for default docker cmd case.
> commit e42f740ccb655c0478a3002c0b6fa90c1144f41c
> https://reviews.apache.org/r/44468/
>
>
> Still Under Review:
> MESOS-4370 NetworkSettings.IPAddress field is deprectaed in Docker.
> https://reviews.apache.org/r/43093/
>
> Fixed a bug that causes the task stuck in staging state.
> https://reviews.apache.org/r/44435/
>
> Fixed http endpoint trigger two inverse offer calls.
> https://reviews.apache.org/r/44258/
>
> Added support for "overlay" keyword.
> https://reviews.apache.org/r/44421/
>
> Added document for overlayfs backend.
> https://reviews.apache.org/r/44391/
>
> Add support for user-defined networks.
> https://reviews.apache.org/r/42516/
>
> On Wed, Mar 9, 2016 at 5:50 PM, Guangya Liu  wrote:
> > Tim,
> >
> > What about https://reviews.apache.org/r/42516/ for user-defined
> > network in docker containerizer, the user defined network has been
> > landed in docker for quite a while and it is better to enable mesos
> > docker containerizer support this.
> >
> > Thanks,
> >
> > Guangya
> >
> > On Thu, Mar 10, 2016 at 2:00 AM, Kevin Klues  wrote:
> >>
> >> Tim,
> >>
> >> Is there a review other than the following for MESOS-4370?
> >>
> >> Restore Mesos' ability to extract Docker assigned IPs (still under
> >> review):
> >> https://reviews.apache.org/r/43093/
> >>
> >> If not, it was already on the list, but has not yet landed.
> >>
> >> On Wed, Mar 9, 2016 at 9:57 AM, Timothy Chen  wrote:
> >> > Also like to include MESOS-4370 as it fixes IP Address look up
> >> > logic and also unblocks users using custom Docker network.
> >> >
> >> > Tim
> >> >
> >> > On Wed, Mar 9, 2016 at 9:55 AM, Gilbert Song
> >> > 
> >> > wrote:
> >> >> Hi Kevin,
> >> >>
> >> >> Please remove the the patch below from the list:
> >> >> Implemented runtime isolator default cmd test (still under review).
> >> >> https://reviews.apache.org/r/44469/
> >> >>
> >> >> Because the bug was fixed by patch #44468, the test should not be
> >> >> considered as a block. I am updating MESOS-4888 and move the test
> >> >> to a separate JIRA.
> >> >>
> >> >> Thanks,
> >> >> Gilbert
> >> >>
> >> >> On Tue, Mar 8, 2016 at 2:43 PM, Kevin Klues 
> wrote:
> >> >>
> >> >>> Here are the list of reviews/patches that have been called out in
> >> >>> this thread for inclusion in 0.28.0-rc2.  Some of them are still
> >> >>> under review and will need to land by Thursday to be included.
> >> >>>
> >> >>> Are there others?
> >> >>>
> >> >>> Jie's container image documentation (submitted):
> >> >>> commit 7de8cdd4d8ed1d222fa03ea0d8fa6740c4a9f84b
> >> >>> https://reviews.apache.org/r/44414
> >> >>>
> >> >>> Restore Mesos' ability to extract Docker assigned IPs (still
> >> >>> under
> >> >>> review):
> >> >>> https://reviews.apache.org/r/43093/
> >> >>>
> >> >>> Fixed the logic for default docker cmd case (submitted).
> >> >>> commit e42f740ccb655c0478a3002c0b6fa90c1144f41c
> >> >>> https://reviews.apache.org/r/44468/
> >> >>>
> >> >>> Implemented runtime isolator default cmd test (still under review).
> >> >>> https://reviews.apache.org/r/44469/
> >> >>>
> >> >>> Fixed a bug that causes the task stuck in staging state (still
> >> >>> under review).
> >> >>> https://reviews.apache.org/r/44435/
> >> >>>
> >> >>> On Tue, Mar 8, 2016 at 10:30 AM, Kevin Klues 
> >> >>> wrote:
> >> >>> > Yes, will do.
> >> >>> >
> >> >>> > On Tue, Mar 8, 2016 at 10:26 AM, Vinod Kone
> >> >>> > 
> >> >>> wrote:
> >> >>> >> +kevin klues
> >> >>> >>
> >> >>> >> OK. I'm cancelling this vote since there are some show stopper
> >> >>> >> issues
> >> >>> that
> >> >>> >> we need to cherry-pick. I'll cut another RC on Thursday.
> >> >>> >>
> >> >>> >> @shepherds: can you please make sure the blocker tickets are
> >> >>> >> marked with fix version and that they land today or tomorrow?
> >> >>> >>
> >> >>> >> @kevin: since you have volunteered to help with the release,
> >> >>> >> can you
> >> >>> make
> >> >>> >> sure we have a list of commits to cherry pick for rc2?
> >> >>> >>
> >> >>> >> Thanks,
> >> >>> >>
> >> >>> >>
> >> >>> >> On Tue, Mar 8, 20

Re: 0.27.2 RPMs

[Guillermo Rodriguez]

Annoying right? I built my own and the result was a huge behemoth 3GB in size 
compared to the 580MB from mesosphere.

 A problem I'm noticing now is that the docker engine is restarting. May not be 
related at all.





 From: "Pradeep Chhetri" 
Sent: Friday, March 11, 2016 7:58 AM
To: user@mesos.apache.org
Subject: Re: 0.27.2 RPMs

Hello all,

I still don't see any Mesos 0.27.2 deb/rpm artifacts in the mesosphere 
repository. Is this expected ?

Thanks.  On Mar 9, 2016 3:46 PM, "Rad Gruchalski"  wrote: 
  Oh, cool, I was expecting some info here.
 Going to build one now :)







Kind regards,?
Radek Gruchalski
?   ra...@gruchalski.com?
de.linkedin.com/in/radgruchalski/

Confidentiality:
This communication is intended for the above-named person and may be 
confidential and/or legally privileged.
If it has come to you in error you must take no action based on it, nor must 
you copy or show it to anyone; please delete/destroy and inform the sender 
immediately.

On Wednesday, 9 March 2016 at 16:44, craig w wrote: I thought so based on 
the website: http://mesos.apache.org/blog/mesos-0-27-2-released/

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

[Daniel Osborne]

Kevin,

When are you planning on cutting?

I'm very keen to seeing 4370 get merged. It just needs some final fixes to get 
past "Fix it, then ship it".

Thanks,
Dan


-Original Message-
From: Kevin Klues [mailto:klue...@gmail.com] 
Sent: Thursday, March 10, 2016 11:46 AM
To: user ; dev 
Subject: Re: [VOTE] Release Apache Mesos 0.28.0 (rc1)

Updated list of patches to include in 0.28.0-rc2.  We are cutting the release 
candidate today, so make sure your patches land soon if they haven't already.

Did I miss any?

Committed:
Added documentation about container image support.
commit 7de8cdd4d8ed1d222fa03ea0d8fa6740c4a9f84b
https://reviews.apache.org/r/44414

Fixed the logic for default docker cmd case.
commit e42f740ccb655c0478a3002c0b6fa90c1144f41c
https://reviews.apache.org/r/44468/


Still Under Review:
MESOS-4370 NetworkSettings.IPAddress field is deprectaed in Docker.
https://reviews.apache.org/r/43093/

Fixed a bug that causes the task stuck in staging state.
https://reviews.apache.org/r/44435/

Fixed http endpoint trigger two inverse offer calls.
https://reviews.apache.org/r/44258/

Added support for "overlay" keyword.
https://reviews.apache.org/r/44421/

Added document for overlayfs backend.
https://reviews.apache.org/r/44391/

Add support for user-defined networks.
https://reviews.apache.org/r/42516/

On Wed, Mar 9, 2016 at 5:50 PM, Guangya Liu  wrote:
> Tim,
>
> What about https://reviews.apache.org/r/42516/ for user-defined 
> network in docker containerizer, the user defined network has been 
> landed in docker for quite a while and it is better to enable mesos 
> docker containerizer support this.
>
> Thanks,
>
> Guangya
>
> On Thu, Mar 10, 2016 at 2:00 AM, Kevin Klues  wrote:
>>
>> Tim,
>>
>> Is there a review other than the following for MESOS-4370?
>>
>> Restore Mesos' ability to extract Docker assigned IPs (still under
>> review):
>> https://reviews.apache.org/r/43093/
>>
>> If not, it was already on the list, but has not yet landed.
>>
>> On Wed, Mar 9, 2016 at 9:57 AM, Timothy Chen  wrote:
>> > Also like to include MESOS-4370 as it fixes IP Address look up 
>> > logic and also unblocks users using custom Docker network.
>> >
>> > Tim
>> >
>> > On Wed, Mar 9, 2016 at 9:55 AM, Gilbert Song 
>> > 
>> > wrote:
>> >> Hi Kevin,
>> >>
>> >> Please remove the the patch below from the list:
>> >> Implemented runtime isolator default cmd test (still under review).
>> >> https://reviews.apache.org/r/44469/
>> >>
>> >> Because the bug was fixed by patch #44468, the test should not be 
>> >> considered as a block. I am updating MESOS-4888 and move the test 
>> >> to a separate JIRA.
>> >>
>> >> Thanks,
>> >> Gilbert
>> >>
>> >> On Tue, Mar 8, 2016 at 2:43 PM, Kevin Klues  wrote:
>> >>
>> >>> Here are the list of reviews/patches that have been called out in 
>> >>> this thread for inclusion in 0.28.0-rc2.  Some of them are still 
>> >>> under review and will need to land by Thursday to be included.
>> >>>
>> >>> Are there others?
>> >>>
>> >>> Jie's container image documentation (submitted):
>> >>> commit 7de8cdd4d8ed1d222fa03ea0d8fa6740c4a9f84b
>> >>> https://reviews.apache.org/r/44414
>> >>>
>> >>> Restore Mesos' ability to extract Docker assigned IPs (still 
>> >>> under
>> >>> review):
>> >>> https://reviews.apache.org/r/43093/
>> >>>
>> >>> Fixed the logic for default docker cmd case (submitted).
>> >>> commit e42f740ccb655c0478a3002c0b6fa90c1144f41c
>> >>> https://reviews.apache.org/r/44468/
>> >>>
>> >>> Implemented runtime isolator default cmd test (still under review).
>> >>> https://reviews.apache.org/r/44469/
>> >>>
>> >>> Fixed a bug that causes the task stuck in staging state (still 
>> >>> under review).
>> >>> https://reviews.apache.org/r/44435/
>> >>>
>> >>> On Tue, Mar 8, 2016 at 10:30 AM, Kevin Klues 
>> >>> wrote:
>> >>> > Yes, will do.
>> >>> >
>> >>> > On Tue, Mar 8, 2016 at 10:26 AM, Vinod Kone 
>> >>> > 
>> >>> wrote:
>> >>> >> +kevin klues
>> >>> >>
>> >>> >> OK. I'm cancelling this vote since there are some show stopper 
>> >>> >> issues
>> >>> that
>> >>> >> we need to cherry-pick. I'll cut another RC on Thursday.
>> >>> >>
>> >>> >> @shepherds: can you please make sure the blocker tickets are 
>> >>> >> marked with fix version and that they land today or tomorrow?
>> >>> >>
>> >>> >> @kevin: since you have volunteered to help with the release, 
>> >>> >> can you
>> >>> make
>> >>> >> sure we have a list of commits to cherry pick for rc2?
>> >>> >>
>> >>> >> Thanks,
>> >>> >>
>> >>> >>
>> >>> >> On Tue, Mar 8, 2016 at 12:05 AM, Shuai Lin 
>> >>> >> 
>> >>> wrote:
>> >>> >>
>> >>> >>> Maybe also https://issues.apache.org/jira/browse/MESOS-4877 
>> >>> >>> and
>> >>> >>> https://issues.apache.org/jira/browse/MESOS-4878 ?
>> >>> >>>
>> >>> >>>
>> >>> >>> On Tue, Mar 8, 2016 at 9:13 AM, Jie Yu 
>> >>> >>> wrote:
>> >>> >>>
>> >>>  I'd like to fix 
>> >>>  https://issues.apache.org/jira/browse/MESOS-4888
>> >>>  as
>> >>> well
>> >>>  if you guys plan to cut a

Re: 0.27.2 RPMs

[Pradeep Chhetri]

Hello all,

I still don't see any Mesos 0.27.2 deb/rpm artifacts in the mesosphere
repository. Is this expected ?

Thanks.
On Mar 9, 2016 3:46 PM, "Rad Gruchalski"  wrote:

> Oh, cool, I was expecting some info here.
> Going to build one now :)
>
> Kind regards,
> Radek Gruchalski
> ra...@gruchalski.com 
> de.linkedin.com/in/radgruchalski/
>
>
> *Confidentiality:*This communication is intended for the above-named
> person and may be confidential and/or legally privileged.
> If it has come to you in error you must take no action based on it, nor
> must you copy or show it to anyone; please delete/destroy and inform the
> sender immediately.
>
> On Wednesday, 9 March 2016 at 16:44, craig w wrote:
>
> I thought so based on the website:
> http://mesos.apache.org/blog/mesos-0-27-2-released/
>
>
>

mesos.interface 0.27.2

[Rad Gruchalski]

Hi everyone,  

I have successfully upgraded my cluster to 0.27.2 but I have a couple of 
questions regarding mesos.interface python package.  
First, I do not see the 0.27.2 version in pypi: 
https://pypi.python.org/pypi/mesos.interface. Is that intentional?

Second, I thought it would be better to use the modules built with Mesos. I am 
building Mesos myself and package it using mesos-deb-packaging. After 
installation with apt, I see that the modules are installed in:

/usr/lib/python2.7/site-packages

I tried the following:

export PYTHONPATH=$PYTHONPATH:/usr/lib/python2.7/site-packages
/usr/local/lib/python2.7/dist-packages/mesos/native$ mesos-ps

But the result is:

Traceback (most recent call last):
  File "/usr/bin/mesos-ps", line 10, in 
from mesos import http
ImportError: cannot import name http


Am I missing some important step here?
Thanks for any pointers.










Kind regards,

Radek Gruchalski

ra...@gruchalski.com (mailto:ra...@gruchalski.com)
 
(mailto:ra...@gruchalski.com)
de.linkedin.com/in/radgruchalski/ (http://de.linkedin.com/in/radgruchalski/)

Confidentiality:
This communication is intended for the above-named person and may be 
confidential and/or legally privileged.
If it has come to you in error you must take no action based on it, nor must 
you copy or show it to anyone; please delete/destroy and inform the sender 
immediately.

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

[Kevin Klues]

Updated list of patches to include in 0.28.0-rc2.  We are cutting the
release candidate today, so make sure your patches land soon if they
haven't already.

Did I miss any?

Committed:
Added documentation about container image support.
commit 7de8cdd4d8ed1d222fa03ea0d8fa6740c4a9f84b
https://reviews.apache.org/r/44414

Fixed the logic for default docker cmd case.
commit e42f740ccb655c0478a3002c0b6fa90c1144f41c
https://reviews.apache.org/r/44468/


Still Under Review:
MESOS-4370 NetworkSettings.IPAddress field is deprectaed in Docker.
https://reviews.apache.org/r/43093/

Fixed a bug that causes the task stuck in staging state.
https://reviews.apache.org/r/44435/

Fixed http endpoint trigger two inverse offer calls.
https://reviews.apache.org/r/44258/

Added support for "overlay" keyword.
https://reviews.apache.org/r/44421/

Added document for overlayfs backend.
https://reviews.apache.org/r/44391/

Add support for user-defined networks.
https://reviews.apache.org/r/42516/

On Wed, Mar 9, 2016 at 5:50 PM, Guangya Liu  wrote:
> Tim,
>
> What about https://reviews.apache.org/r/42516/ for user-defined network in
> docker containerizer, the user defined network has been landed in docker for
> quite a while and it is better to enable mesos docker containerizer support
> this.
>
> Thanks,
>
> Guangya
>
> On Thu, Mar 10, 2016 at 2:00 AM, Kevin Klues  wrote:
>>
>> Tim,
>>
>> Is there a review other than the following for MESOS-4370?
>>
>> Restore Mesos' ability to extract Docker assigned IPs (still under
>> review):
>> https://reviews.apache.org/r/43093/
>>
>> If not, it was already on the list, but has not yet landed.
>>
>> On Wed, Mar 9, 2016 at 9:57 AM, Timothy Chen  wrote:
>> > Also like to include MESOS-4370 as it fixes IP Address look up logic
>> > and also unblocks users using custom Docker network.
>> >
>> > Tim
>> >
>> > On Wed, Mar 9, 2016 at 9:55 AM, Gilbert Song 
>> > wrote:
>> >> Hi Kevin,
>> >>
>> >> Please remove the the patch below from the list:
>> >> Implemented runtime isolator default cmd test (still under review).
>> >> https://reviews.apache.org/r/44469/
>> >>
>> >> Because the bug was fixed by patch #44468, the test should not be
>> >> considered as a block. I am updating MESOS-4888 and move the test to a
>> >> separate JIRA.
>> >>
>> >> Thanks,
>> >> Gilbert
>> >>
>> >> On Tue, Mar 8, 2016 at 2:43 PM, Kevin Klues  wrote:
>> >>
>> >>> Here are the list of reviews/patches that have been called out in this
>> >>> thread for inclusion in 0.28.0-rc2.  Some of them are still under
>> >>> review and will need to land by Thursday to be included.
>> >>>
>> >>> Are there others?
>> >>>
>> >>> Jie's container image documentation (submitted):
>> >>> commit 7de8cdd4d8ed1d222fa03ea0d8fa6740c4a9f84b
>> >>> https://reviews.apache.org/r/44414
>> >>>
>> >>> Restore Mesos' ability to extract Docker assigned IPs (still under
>> >>> review):
>> >>> https://reviews.apache.org/r/43093/
>> >>>
>> >>> Fixed the logic for default docker cmd case (submitted).
>> >>> commit e42f740ccb655c0478a3002c0b6fa90c1144f41c
>> >>> https://reviews.apache.org/r/44468/
>> >>>
>> >>> Implemented runtime isolator default cmd test (still under review).
>> >>> https://reviews.apache.org/r/44469/
>> >>>
>> >>> Fixed a bug that causes the task stuck in staging state (still under
>> >>> review).
>> >>> https://reviews.apache.org/r/44435/
>> >>>
>> >>> On Tue, Mar 8, 2016 at 10:30 AM, Kevin Klues 
>> >>> wrote:
>> >>> > Yes, will do.
>> >>> >
>> >>> > On Tue, Mar 8, 2016 at 10:26 AM, Vinod Kone 
>> >>> wrote:
>> >>> >> +kevin klues
>> >>> >>
>> >>> >> OK. I'm cancelling this vote since there are some show stopper
>> >>> >> issues
>> >>> that
>> >>> >> we need to cherry-pick. I'll cut another RC on Thursday.
>> >>> >>
>> >>> >> @shepherds: can you please make sure the blocker tickets are marked
>> >>> >> with
>> >>> >> fix version and that they land today or tomorrow?
>> >>> >>
>> >>> >> @kevin: since you have volunteered to help with the release, can
>> >>> >> you
>> >>> make
>> >>> >> sure we have a list of commits to cherry pick for rc2?
>> >>> >>
>> >>> >> Thanks,
>> >>> >>
>> >>> >>
>> >>> >> On Tue, Mar 8, 2016 at 12:05 AM, Shuai Lin 
>> >>> wrote:
>> >>> >>
>> >>> >>> Maybe also https://issues.apache.org/jira/browse/MESOS-4877 and
>> >>> >>> https://issues.apache.org/jira/browse/MESOS-4878 ?
>> >>> >>>
>> >>> >>>
>> >>> >>> On Tue, Mar 8, 2016 at 9:13 AM, Jie Yu 
>> >>> >>> wrote:
>> >>> >>>
>> >>>  I'd like to fix https://issues.apache.org/jira/browse/MESOS-4888
>> >>>  as
>> >>> well
>> >>>  if you guys plan to cut another RC
>> >>> 
>> >>>  On Mon, Mar 7, 2016 at 10:16 AM, Daniel Osborne <
>> >>>  daniel.osbo...@metaswitch.com> wrote:
>> >>> 
>> >>> > -1
>> >>> >
>> >>> > If it doesn’t cause too much pain, I'm hoping we can squeeze a
>> >>> > relatively small patch which restores Mesos' ability to extract
>> >>> Docker
>> >>> > assigned IPs. This has been broken with Docker 1.10's relea

Re: Executors no longer inherit environment variables from the agent

[Jie Yu]

Rodrick,

This is unfortunate we are using environment variables that get passed into
> the executors context such as
> CHRONOS_RESOURCE_MEM
> MARATHON_APP_RESOURCE_MEM
> What will be the workaround?


Those env vars are set when launching the agent? Can you use
--executor_environment_variables to explicitly set it?

- Jie

On Thu, Mar 10, 2016 at 10:38 AM, Rodrick Brown 
wrote:

> This is unfortunate we are using environment variables that get passed
> into the executors context such as
>
> CHRONOS_RESOURCE_MEM
> MARATHON_APP_RESOURCE_MEM
>
> What will be the workaround?
>
> --
>
> *Rodrick Brown* / Systems Engineer
>
> +1 917 445 6839 / rodr...@orchardplatform.com
> 
>
> *Orchard Platform*
>
> 101 5th Avenue, 4th Floor, New York, NY 10003
>
> http://www.orchardplatform.com
>
> Orchard Blog  | Marketplace Lending
> Meetup 
>
>> On Mar 8 2016, at 2:33 pm, Gilbert Song  wrote:
>>
>> Hi,
>>
>> TL;DR Executors will no longer inherit environment variables from the
>> agent by default in 0.30.
>>
>> Currently, executors are inheriting environment variables form the agent
>> in mesos containerizer by default. This is an unfortunate legacy behavior
>> and is insecure. If you do have environment variables that you want to pass
>> to the executors, you can set it explicitly by using the
>> `--executor_environment_variables` agent flag.
>>
>> Starting from 0.30, we will no longer allow executors to inherit
>> environment variables from the agent. In other words,
>> `--executor_environment_variables` will be set to “{}” by default. If you
>> do depend on the original behavior, please set
>> `--executor_environment_variables` flag explicitly.
>>
>> Let us know if you have any comments or concerns.
>>
>> Thanks,
>> Gilbert
>>
>
> *NOTICE TO RECIPIENTS*: This communication is confidential and intended
> for the use of the addressee only. If you are not an intended recipient of
> this communication, please delete it immediately and notify the sender by
> return email. Unauthorized reading, dissemination, distribution or copying
> of this communication is prohibited. This communication does not constitute
> an offer to sell or a solicitation of an indication of interest to purchase
> any loan, security or any other financial product or instrument, nor is it
> an offer to sell or a solicitation of an indication of interest to purchase
> any products or services to any persons who are prohibited from receiving
> such information under applicable law. The contents of this communication
> may not be accurate or complete and are subject to change without notice.
> As such, Orchard App, Inc. (including its subsidiaries and affiliates,
> "Orchard") makes no representation regarding the accuracy or completeness
> of the information contained herein. The intended recipient is advised to
> consult its own professional advisors, including those specializing in
> legal, tax and accounting matters. Orchard does not provide legal, tax or
> accounting advice.
>

Re: Executors no longer inherit environment variables from the agent

[Connor Doyle]

Rodrick, in your case those environment variables are set by the
framework as part of the TaskInfo, so those shouldn't be affected by
the change.

On Thu, Mar 10, 2016 at 10:38 AM, Rodrick Brown  wrote:
> This is unfortunate we are using environment variables that get passed into
> the executors context such as
>
> CHRONOS_RESOURCE_MEM
> MARATHON_APP_RESOURCE_MEM
>
> What will be the workaround?
>
> --
>
> Rodrick Brown / Systems Engineer
>
> +1 917 445 6839 / rodr...@orchardplatform.com
>
> Orchard Platform
>
> 101 5th Avenue, 4th Floor, New York, NY 10003
>
> http://www.orchardplatform.com
>
> Orchard Blog | Marketplace Lending Meetup
>>
>> On Mar 8 2016, at 2:33 pm, Gilbert Song  wrote:
>>
>> Hi,
>>
>>
>> TL;DR Executors will no longer inherit environment variables from the
>> agent by default in 0.30.
>>
>>
>> Currently, executors are inheriting environment variables form the agent
>> in mesos containerizer by default. This is an unfortunate legacy behavior
>> and is insecure. If you do have environment variables that you want to pass
>> to the executors, you can set it explicitly by using the
>> `--executor_environment_variables` agent flag.
>>
>>
>> Starting from 0.30, we will no longer allow executors to inherit
>> environment variables from the agent. In other words,
>> `--executor_environment_variables` will be set to “{}” by default. If you do
>> depend on the original behavior, please set
>> `--executor_environment_variables` flag explicitly.
>>
>>
>> Let us know if you have any comments or concerns.
>>
>>
>> Thanks,
>>
>> Gilbert
>
>
> NOTICE TO RECIPIENTS: This communication is confidential and intended for
> the use of the addressee only. If you are not an intended recipient of this
> communication, please delete it immediately and notify the sender by return
> email. Unauthorized reading, dissemination, distribution or copying of this
> communication is prohibited. This communication does not constitute an offer
> to sell or a solicitation of an indication of interest to purchase any loan,
> security or any other financial product or instrument, nor is it an offer to
> sell or a solicitation of an indication of interest to purchase any products
> or services to any persons who are prohibited from receiving such
> information under applicable law. The contents of this communication may not
> be accurate or complete and are subject to change without notice. As such,
> Orchard App, Inc. (including its subsidiaries and affiliates, "Orchard")
> makes no representation regarding the accuracy or completeness of the
> information contained herein. The intended recipient is advised to consult
> its own professional advisors, including those specializing in legal, tax
> and accounting matters. Orchard does not provide legal, tax or accounting
> advice.



-- 
connor

Re: Executors no longer inherit environment variables from the agent

[Rodrick Brown]

This is unfortunate we are using environment variables that get passed into
the executors context such as

  

CHRONOS_RESOURCE_MEM  

MARATHON_APP_RESOURCE_MEM

  

What will be the workaround?  

  

\--

**Rodrick Brown** / Systems Engineer 

+1 917 445 6839 /
[rodr...@orchardplatform.com](mailto:char...@orchardplatform.com)

**Orchard Platform** 

101 5th Avenue, 4th Floor, New York, NY 10003

[http://www.orchardplatform.com](http://www.orchardplatform.com/)

[Orchard Blog](http://www.orchardplatform.com/blog/) | [Marketplace Lending
Meetup](http://www.meetup.com/Peer-to-Peer-Lending-P2P/)

> On Mar 8 2016, at 2:33 pm, Gilbert Song  wrote:  

>

> Hi,

>

>  

>

> TL;DR Executors will no longer inherit environment variables from the agent
by default in 0.30.

>

>  

>

> Currently, executors are inheriting environment variables form the agent in
mesos containerizer by default. This is an unfortunate legacy behavior and is
insecure. If you do have environment variables that you want to pass to the
executors, you can set it explicitly by using the
`--executor_environment_variables` agent flag.

>

>  

>

> Starting from 0.30, we will no longer allow executors to inherit environment
variables from the agent. In other words, `--executor_environment_variables`
will be set to “{}” by default. If you do depend on the original behavior,
please set `--executor_environment_variables` flag explicitly.

>

>  

>

> Let us know if you have any comments or concerns.

>

>  

>

> Thanks,

>

> Gilbert  


-- 
*NOTICE TO RECIPIENTS*: This communication is confidential and intended for 
the use of the addressee only. If you are not an intended recipient of this 
communication, please delete it immediately and notify the sender by return 
email. Unauthorized reading, dissemination, distribution or copying of this 
communication is prohibited. This communication does not constitute an 
offer to sell or a solicitation of an indication of interest to purchase 
any loan, security or any other financial product or instrument, nor is it 
an offer to sell or a solicitation of an indication of interest to purchase 
any products or services to any persons who are prohibited from receiving 
such information under applicable law. The contents of this communication 
may not be accurate or complete and are subject to change without notice. 
As such, Orchard App, Inc. (including its subsidiaries and affiliates, 
"Orchard") makes no representation regarding the accuracy or completeness 
of the information contained herein. The intended recipient is advised to 
consult its own professional advisors, including those specializing in 
legal, tax and accounting matters. Orchard does not provide legal, tax or 
accounting advice.

Re: Cluster history wiped after master leader reelection

[Rodrick Brown]

Yes this is the intended behavior.  

  

\--

**Rodrick Brown** / Systems Engineer 

+1 917 445 6839 /
[rodr...@orchardplatform.com](mailto:char...@orchardplatform.com)

**Orchard Platform** 

101 5th Avenue, 4th Floor, New York, NY 10003

[http://www.orchardplatform.com](http://www.orchardplatform.com/)

[Orchard Blog](http://www.orchardplatform.com/blog/) | [Marketplace Lending
Meetup](http://www.meetup.com/Peer-to-Peer-Lending-P2P/)

> On Mar 10 2016, at 11:47 am, Geoffroy Jabouley
 wrote:  

>

> Hello

>

>  

>

> a leader re-election just occured on our cluster (0.25.0).

>

>  

>

> It goes fine except the entire cluster history has been lost.

>

>  

>

> All tasks counters have been resetted to 0, Completed tasks and Terminated
frameworks lists are empty.

>

>  

>

> Has anybody experienced this?

>

>  

>

> Regards

>

>  

>

>  

>

> PS: this is not a blocking problem, but it is important in our job to
sometimes show figures to our management, and such counters always makes good
impression ;)


-- 
*NOTICE TO RECIPIENTS*: This communication is confidential and intended for 
the use of the addressee only. If you are not an intended recipient of this 
communication, please delete it immediately and notify the sender by return 
email. Unauthorized reading, dissemination, distribution or copying of this 
communication is prohibited. This communication does not constitute an 
offer to sell or a solicitation of an indication of interest to purchase 
any loan, security or any other financial product or instrument, nor is it 
an offer to sell or a solicitation of an indication of interest to purchase 
any products or services to any persons who are prohibited from receiving 
such information under applicable law. The contents of this communication 
may not be accurate or complete and are subject to change without notice. 
As such, Orchard App, Inc. (including its subsidiaries and affiliates, 
"Orchard") makes no representation regarding the accuracy or completeness 
of the information contained herein. The intended recipient is advised to 
consult its own professional advisors, including those specializing in 
legal, tax and accounting matters. Orchard does not provide legal, tax or 
accounting advice.

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

[Greg Mann]

+1 (non-binding)

Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled.
All tests pass.

I was also able to successfully test a simple upgrade scenario from 0.23.1
to 0.24.2-rc2 using the script found here:
https://reviews.apache.org/r/44229/

Cheers,
Greg


On Tue, Mar 8, 2016 at 6:50 PM, Michael Park  wrote:

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

Re: Executors no longer inherit environment variables from the agent

[Jie Yu]

Alex,

See my response inlined:

First, does this change include the executor library? We currently use
> environment variables to propagate various config values from an agent to
> executors. If it does, what is the alternative?


Any environment variables generated by Mesos (i.e., MESOS_, LIBPROCESS_)
will not be affected.

Second, what will be the preferred way to pass config values to executors?
> It would be great to be able to do it uniformly for non-HTTP and HTTP
> executors. I can think of several possibilities: cmd flags, adding or
> overriding protobufs, extending Executor interface.


You can always use the Environments in ExecutorInfo.CommandInfo or
TaskInfo.CommandInfo to pass in environment variables to executors/tasks.

- Jie

On Thu, Mar 10, 2016 at 3:50 AM, Alex Rukletsov  wrote:

> I have two questions.
>
> First, does this change include the executor library? We currently use
> environment variables to propagate various config values from an agent to
> executors. If it does, what is the alternative?
>
> Second, what will be the preferred way to pass config values to executors?
> It would be great to be able to do it uniformly for non-HTTP and HTTP
> executors. I can think of several possibilities: cmd flags, adding or
> overriding protobufs, extending Executor interface.
>
> On Tue, Mar 8, 2016 at 9:21 PM, Gilbert Song 
> wrote:
>
>> Yes, `LIBPROCESS_IP` will be excepted from this change. We will still
>> have `LIBPROCESS_IP` set and passed to executors' environment, which is for
>> the case that DNS is not available on the slave.
>>
>> Gilbert
>>
>> On Tue, Mar 8, 2016 at 11:57 AM, Zhitao Li  wrote:
>>
>>> Is LIBPROCESS_IP going to be an exception to this? Some executors are
>>> using this variable as an alternative of implementing their own IP
>>> detection logic AFAIK so this behavior would break them.
>>>
>>> On Tue, Mar 8, 2016 at 11:33 AM, Gilbert Song 
>>> wrote:
>>>
 Hi,

 TL;DR Executors will no longer inherit environment variables from the
 agent by default in 0.30.

 Currently, executors are inheriting environment variables form the
 agent in mesos containerizer by default. This is an unfortunate legacy
 behavior and is insecure. If you do have environment variables that you
 want to pass to the executors, you can set it explicitly by using the
 `--executor_environment_variables` agent flag.

 Starting from 0.30, we will no longer allow executors to inherit
 environment variables from the agent. In other words,
 `--executor_environment_variables` will be set to “{}” by default. If you
 do depend on the original behavior, please set
 `--executor_environment_variables` flag explicitly.

 Let us know if you have any comments or concerns.

 Thanks,
 Gilbert

>>>
>>>
>>>
>>> --
>>> Cheers,
>>>
>>> Zhitao Li
>>>
>>
>>
>

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

[Michael Park]

Thanks Greg!

On 10 March 2016 at 12:34, Greg Mann  wrote:

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

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

[Michael Park]

Thanks Greg!

On 10 March 2016 at 12:32, Greg Mann  wrote:

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

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

[Greg Mann]

+1 (non-binding)

Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled.

The following tests failed during the first test run:
ContainerizerTest.ROOT_CGROUPS_BalloonFramework
MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery

but these all passed when re-run in isolation using the gtest filter.

I was also able to successfully test a simple upgrade scenario from
0.24.2-rc2 to 0.25.1-rc2 using the script found here:
https://reviews.apache.org/r/44229/

Cheers,
Greg


On Tue, Mar 8, 2016 at 7:29 PM, Michael Park  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 0.25.1.
>
>
> 0.25.1 includes the following:
>
> 
>
> The only diff with RC1 is the following: Fix CGROUPS_ROOT_* tests on
> systemd platforms.
> <
> https://github.com/apache/mesos/commit/253223b3288df85cb3b12fe3af5c7b0a7a262f1a
> >
> This patch is necessary in order to make the `systemd` integration work
> correctly.
> It was part of MESOS-4636
>  but
> was accidentally left out during the cherry-pick process.
>
> * Improvements
>   - `/state` endpoint performance
>   - `systemd` integration
>   - GLOG performance
>   - Configurable task/framework history
>   - Offer filter timeout fix for backlogged allocator
>
> * Bugs
>   - SSL
>   - Libevent
>   - Fixed point resources math
>   - HDFS
>   - Agent upgrade compatibility
>   - Health checks
>
> The CHANGELOG for the release is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.25.1-rc2
>
> 
>
> The candidate for Mesos 0.25.1 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc2/mesos-0.25.1.tar.gz
>
> The tag to be voted on is 0.25.1-rc2:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.25.1-rc2
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc2/mesos-0.25.1.tar.gz.md5
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.25.1-rc2/mesos-0.25.1.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
> The JAR is up in Maven in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1116
>
> Please vote on releasing this package as Apache Mesos 0.25.1!
>
> The vote is open until Fri Mar 11 23:59:59 EST 2016 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 0.25.1
> [ ] -1 Do not release this package because ...
>
> Thanks,
>
> MPark
>

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

[Greg Mann]

+1 (non-binding)

Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL enabled.
All tests pass.

I was also able to successfully test a simple upgrade scenario from
0.25.1-rc2 to 0.26.1-rc2 using the script found here:
https://reviews.apache.org/r/44229/

Cheers,
Greg


On Tue, Mar 8, 2016 at 7:48 PM, Michael Park  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 0.26.1.
>
>
> 0.26.1 includes the following:
>
> 
>
> The only diff with RC1 is the following: Fix CGROUPS_ROOT_* tests on
> systemd platforms.
> 
> This patch is necessary in order to make the `systemd` integration work
> correctly.
> It was part of MESOS-4636
>  but was accidentally
> left out during the cherry-pick process.
>
> * Improvements
>   - `/state` endpoint performance
>   - `systemd` integration
>   - GLOG performance
>   - Configurable task/framework history
>   - Offer filter timeout fix for backlogged allocator
>
> * Bugs
>   - SSL
>   - Libevent
>   - Fixed point resources math
>   - HDFS
>   - Agent upgrade compatibility
>
> The CHANGELOG for the release is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.26.1-rc2
>
> 
>
> The candidate for Mesos 0.26.1 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc2/mesos-0.26.1.tar.gz
>
> The tag to be voted on is 0.26.1-rc2:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.26.1-rc2
>
> The MD5 checksum of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc2/mesos-0.26.1.tar.gz.md5
>
> The signature of the tarball can be found at:
>
> https://dist.apache.org/repos/dist/dev/mesos/0.26.1-rc2/mesos-0.26.1.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
> The JAR is up in Maven in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1118
>
> Please vote on releasing this package as Apache Mesos 0.26.1!
>
> The vote is open until Fri Mar 11 23:59:59 EST 2016 and passes if a
> majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Mesos 0.26.1
> [ ] -1 Do not release this package because ...
>
> Thanks,
>
> MPark
>

Cluster history wiped after master leader reelection

[Geoffroy Jabouley]

Hello

a leader re-election just occured on our cluster (0.25.0).

It goes fine except the entire cluster history has been lost.

All tasks counters have been resetted to 0, Completed tasks and Terminated
frameworks lists are empty.

Has anybody experienced this?

Regards


PS: this is not a blocking problem, but it is important in our job to
sometimes show figures to our management, and such counters always makes
good impression ;)

Re: Alternative mesos-ui tasks

[Rodrick Brown]

Hey Alberto,

  

I think you guys did an amazing job on this UI, however I was wondering if
they're any plans to add a navigation link back to a frameworks sandbox dir to
get access to the logs like what's exposed in the default Apache Mesos UI?

  

If that feature was available we would probably deploy this on our cluster,
however as it is right now with no way to navigate back to the default sandbox
dir this is something my team is already use to :(

  

\--

**Rodrick Brown** / Systems Engineer 

+1 917 445 6839 /
[rodr...@orchardplatform.com](mailto:char...@orchardplatform.com)

**Orchard Platform** 

101 5th Avenue, 4th Floor, New York, NY 10003

[http://www.orchardplatform.com](http://www.orchardplatform.com/)

[Orchard Blog](http://www.orchardplatform.com/blog/) | [Marketplace Lending
Meetup](http://www.meetup.com/Peer-to-Peer-Lending-P2P/)

> On Mar 9 2016, at 5:56 pm, Alberto García Lamela
 wrote:  

>

> Hey Rodrik,

>

> thanks for feedback, the framework component is expecting the logo file to
exist here  so the frameworks you are running are
probably not in the list yet. Please feel free to raise an issue or a PR on
the repo with the list of your frameworks.

>

> Cheers,

>

> Alberto

>

>  

>

> * * *

>

> Date: Wed, 9 Mar 2016 14:47:08 -0800  
CC: user@mesos.apache.org  
To: user@mesos.apache.org  
From: rodr...@orchard-app.com  
Subject: Re: Alternative mesos-ui tasks  
  
Looks good,

>

>  

>

> Did a local install on my macbook pointing to my mesos cluster however, any
reason why all my frameworks running have a broken gif in the frameworks
screen?

>

>  

>

> Marathon's gif seems to be fine.

>

>  

>

> \--  

>

> **Rodrick Brown** / Systems Engineer

>

> +1 917 445 6839 /
[rodr...@orchardplatform.com](mailto:char...@orchardplatform.com)

>

> **Orchard Platform**

>

> 101 5th Avenue, 4th Floor, New York, NY 10003

>

> [http://www.orchardplatform.com](http://www.orchardplatform.com/)

>

> [Orchard Blog](http://www.orchardplatform.com/blog/) | [Marketplace Lending
Meetup](http://www.meetup.com/Peer-to-Peer-Lending-P2P/)

>

>> On Mar 9 2016, at 12:45 pm, Alberto García Lamela
 wrote:  

>>

>> Hi there,  
I though might be of interest to some people here. We just added very basic
support for tasks including a visualizer for this alternative UI for Mesos.  
  
  
Would be nice to get some feeback so it can be improved.  
Cheers,  
Alberto  

>

>  

>

> **NOTICE TO RECIPIENTS**: This communication is confidential and intended
for the use of the addressee only. If you are not an intended recipient of
this communication, please delete it immediately and notify the sender by
return email. Unauthorized reading, dissemination, distribution or copying of
this communication is prohibited. This communication does not constitute an
offer to sell or a solicitation of an indication of interest to purchase any
loan, security or any other financial product or instrument, nor is it an
offer to sell or a solicitation of an indication of interest to purchase any
products or services to any persons who are prohibited from receiving such
information under applicable law. The contents of this communication may not
be accurate or complete and are subject to change without notice. As such,
Orchard App, Inc. (including its subsidiaries and affiliates, "Orchard") makes
no representation regarding the accuracy or completeness of the information
contained herein. The intended recipient is advised to consult its own
professional advisors, including those specializing in legal, tax and
accounting matters. Orchard does not provide legal, tax or accounting advice.


-- 
*NOTICE TO RECIPIENTS*: This communication is confidential and intended for 
the use of the addressee only. If you are not an intended recipient of this 
communication, please delete it immediately and notify the sender by return 
email. Unauthorized reading, dissemination, distribution or copying of this 
communication is prohibited. This communication does not constitute an 
offer to sell or a solicitation of an indication of interest to purchase 
any loan, security or any other financial product or instrument, nor is it 
an offer to sell or a solicitation of an indication of interest to purchase 
any products or services to any persons who are prohibited from receiving 
such information under applicable law. The contents of this communication 
may not be accurate or complete and are subject to change without notice. 
As such, Orchard App, Inc. (including its subsidiaries and affiliates, 
"Orchard") makes no representation regarding the accuracy or completeness 
of the information contained herein. The intended recipient is advised to 
consult its own professional advisors, including those specializing in 
legal, tax and accounting matters. Orchard does not provide leg

Re: Executors no longer inherit environment variables from the agent

[Alexander Rojas]

Not that I know a lot about this project, but I think for the command executor 
we can use the `Environment` message. Perhaps we can extend the container info 
to have something similar?


> On 10 Mar 2016, at 12:50, Alex Rukletsov  wrote:
> 
> I have two questions.
> 
> First, does this change include the executor library? We currently use 
> environment variables to propagate various config values from an agent to 
> executors. If it does, what is the alternative?
> 
> Second, what will be the preferred way to pass config values to executors? It 
> would be great to be able to do it uniformly for non-HTTP and HTTP executors. 
> I can think of several possibilities: cmd flags, adding or overriding 
> protobufs, extending Executor interface.
> 
> On Tue, Mar 8, 2016 at 9:21 PM, Gilbert Song  > wrote:
> Yes, `LIBPROCESS_IP` will be excepted from this change. We will still have 
> `LIBPROCESS_IP` set and passed to executors' environment, which is for the 
> case that DNS is not available on the slave.
> 
> Gilbert
> 
> On Tue, Mar 8, 2016 at 11:57 AM, Zhitao Li  > wrote:
> Is LIBPROCESS_IP going to be an exception to this? Some executors are using 
> this variable as an alternative of implementing their own IP detection logic 
> AFAIK so this behavior would break them.
> 
> On Tue, Mar 8, 2016 at 11:33 AM, Gilbert Song  > wrote:
> Hi,
> 
> TL;DR Executors will no longer inherit environment variables from the agent 
> by default in 0.30.
> 
> Currently, executors are inheriting environment variables form the agent in 
> mesos containerizer by default. This is an unfortunate legacy behavior and is 
> insecure. If you do have environment variables that you want to pass to the 
> executors, you can set it explicitly by using the 
> `--executor_environment_variables` agent flag.
> 
> Starting from 0.30, we will no longer allow executors to inherit environment 
> variables from the agent. In other words, `--executor_environment_variables` 
> will be set to “{}” by default. If you do depend on the original behavior, 
> please set `--executor_environment_variables` flag explicitly.
> 
> Let us know if you have any comments or concerns.
> 
> Thanks,
> Gilbert
> 
> 
> 
> -- 
> Cheers,
> 
> Zhitao Li
> 
> 

Re: Executors no longer inherit environment variables from the agent

[Alex Rukletsov]

I have two questions.

First, does this change include the executor library? We currently use
environment variables to propagate various config values from an agent to
executors. If it does, what is the alternative?

Second, what will be the preferred way to pass config values to executors?
It would be great to be able to do it uniformly for non-HTTP and HTTP
executors. I can think of several possibilities: cmd flags, adding or
overriding protobufs, extending Executor interface.

On Tue, Mar 8, 2016 at 9:21 PM, Gilbert Song  wrote:

> Yes, `LIBPROCESS_IP` will be excepted from this change. We will still have
> `LIBPROCESS_IP` set and passed to executors' environment, which is for the
> case that DNS is not available on the slave.
>
> Gilbert
>
> On Tue, Mar 8, 2016 at 11:57 AM, Zhitao Li  wrote:
>
>> Is LIBPROCESS_IP going to be an exception to this? Some executors are
>> using this variable as an alternative of implementing their own IP
>> detection logic AFAIK so this behavior would break them.
>>
>> On Tue, Mar 8, 2016 at 11:33 AM, Gilbert Song 
>> wrote:
>>
>>> Hi,
>>>
>>> TL;DR Executors will no longer inherit environment variables from the
>>> agent by default in 0.30.
>>>
>>> Currently, executors are inheriting environment variables form the agent
>>> in mesos containerizer by default. This is an unfortunate legacy behavior
>>> and is insecure. If you do have environment variables that you want to pass
>>> to the executors, you can set it explicitly by using the
>>> `--executor_environment_variables` agent flag.
>>>
>>> Starting from 0.30, we will no longer allow executors to inherit
>>> environment variables from the agent. In other words,
>>> `--executor_environment_variables` will be set to “{}” by default. If you
>>> do depend on the original behavior, please set
>>> `--executor_environment_variables` flag explicitly.
>>>
>>> Let us know if you have any comments or concerns.
>>>
>>> Thanks,
>>> Gilbert
>>>
>>
>>
>>
>> --
>> Cheers,
>>
>> Zhitao Li
>>
>
>

Re: Alternative mesos-ui tasks

[Rene Moser]

nice work!

On 03/09/2016 06:45 PM, Alberto García Lamela wrote:
> Hi there,
> I though might be of interest to some people here. We just added very
> basic support for tasks including a visualizer for this alternative UI
> for Mesos.
> https://github.com/Capgemini/mesos-ui
> 
> Would be nice to get some feeback so it can be improved.
> Cheers,
> Alberto