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

[haosdent]

Hi, I noted that we have not yet update mesos python packages in pip

```
pip show mesos
---
Metadata-Version: 1.0
Name: mesos
Version: 0.28.1
Summary: Python bindings for mesos
Home-page: http://pypi.python.org/pypi/mesos
Author: Apache Mesos
Author-email: me...@apache.com
License: Apache 2.0
Location: /usr/local/lib/python2.7/site-packages
Requires: mesos.interface, mesos.native
Classifiers:
```

On Fri, Jul 29, 2016 at 5:47 AM, Kapil Arya  wrote:

> PS: Please note that starting with this Mesos 1.0.0 release, the binary
> rpm/deb packages published at http://open.mesosphere.com/downloads/mesos
> (for the Mesosphere package repos hosted at: repo.mesosphere.com) are
> built with libevent+SSL and module dependency installation (i.e.
> `./configure --enable-libevent --enable-ssl --enable-install-module-
> dependencies`).
>
> All future 1.x.y releases will continue to be configured with SSL+libevent
>
> All older releases, i.e., 0.x.y, will continue to be configured _without_
> SSL+libevent.
>
> Best,
> Kapil
>
>
> On Wed, Jul 27, 2016 at 6:10 PM, Kapil Arya  wrote:
>
>> You can find the 1.0.0 rpm/deb packages at:
>>
>> http://open.mesosphere.com/downloads/mesos/#apache-mesos-1.0.0
>>
>>
>> And here are the corresponding docker images based off of Ubuntu 14.04:
>>
>> mesosphere/mesos:1.0.0
>> mesosphere/mesos-master:1.0.0
>> mesosphere/mesos-slave:1.0.0
>>
>> Kapil
>>
>> On Wed, Jul 27, 2016 at 2:52 PM, Jeff Schroeder <
>> jeffschroe...@computer.org> wrote:
>>
>>> Small nit but can you s/experimnental/experimental/ under the "Storage"
>>> header in the release post please?
>>>
>>> Great work otherwise everyone!
>>>
>>>
>>> On Wednesday, July 27, 2016, Vinod Kone  wrote:
>>>
 Hi all,

 The vote for Mesos 1.0.0 (rc4) has passed with the following votes.


 +1 (Binding)

 --

 Kapil Arya

 Jie Yu

 Benjamin Mahler


 +1 (Non-binding)

 --

 Haosdent

 Greg Mann

 Zhitao Li


 +0

 -

 Yan Xu


 There were no  -1 votes.


 *NOTE: There were a couple known issues [MESOS-5911
 , MESOS-5913
 ] that couldn't be fixed
 in time for the 1.0. We plan to do a patch release to fix these ASAP.*


 Please find the release at:

 https://dist.apache.org/repos/dist/release/mesos/1.0.0


 It is recommended to use a mirror to download the release:

 http://www.apache.org/dyn/closer.cgi


 The CHANGELOG for the release is available at:

 https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_
 plain;f=CHANGELOG;hb=1.0.0


 The mesos-1.0.0.jar has been released to:

 https://repository.apache.org


 The website (http://mesos.apache.org) will be updated shortly to
 reflect this release.


 Thanks,

 On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone 
 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 Inte

Deactivationg framework unexpectly

[志昌 余]

Hi,

I recently faced a wired problem. I'm running mesos + chronos. Chronos 
often (once every several days) stops scheduling tasks due to mesos deactived 
the framework.

As following is the log of mesos master leader:


# grep -iP "activat|disconnected" /var/log/mesos/mesos-master.INFO
I0806 13:40:33.14365830 master.cpp:2551] Deactivating framework 
90a6a7dc-7256-4e55-bd7e-573233c5df74- (chronos-2.5.0-SNAPSHOT) at 
scheduler-86a64d22-5201-4bb0-8a2c-70d3e97afae6@10.8.139.246:34544
I0806 13:40:33.14390823 hierarchical.cpp:375] Deactivated framework 
90a6a7dc-7256-4e55-bd7e-573233c5df74-

The fix is to manually reboot the chronos leader.


My env:

There are 3 physical machines, on each are running containerized mesos master 
and chronos. When the issue occurred,  the mesos leader and chronos leader were 
both running on the same machine.


Software Version:

mesos-master:0.28.0-2.0.16.ubuntu1404

chronos:2.5.0-ce4469d.ubuntu1404-mesos-0.28.0-2.0.16.ubuntu1404

Can anyone give insight for this problem?
Thanks,
Zhichang Yu

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

[haosdent]

Oh, it is because Homebrew still using Mesos 0.28.1. Open a pull request to
update it to Mesos 1.0.0 just now.
https://github.com/Homebrew/homebrew-core/pull/3704 Sorry for noise.

On Mon, Aug 8, 2016 at 6:15 PM, haosdent  wrote:

> Hi, I noted that we have not yet update mesos python packages in pip
>
> ```
> pip show mesos
> ---
> Metadata-Version: 1.0
> Name: mesos
> Version: 0.28.1
> Summary: Python bindings for mesos
> Home-page: http://pypi.python.org/pypi/mesos
> Author: Apache Mesos
> Author-email: me...@apache.com
> License: Apache 2.0
> Location: /usr/local/lib/python2.7/site-packages
> Requires: mesos.interface, mesos.native
> Classifiers:
> ```
>
> On Fri, Jul 29, 2016 at 5:47 AM, Kapil Arya  wrote:
>
>> PS: Please note that starting with this Mesos 1.0.0 release, the binary
>> rpm/deb packages published at http://open.mesosphere.com/downloads/mesos
>> (for the Mesosphere package repos hosted at: repo.mesosphere.com) are
>> built with libevent+SSL and module dependency installation (i.e.
>> `./configure --enable-libevent --enable-ssl --enable-install-module-
>> dependencies`).
>>
>> All future 1.x.y releases will continue to be configured with SSL+libevent
>>
>> All older releases, i.e., 0.x.y, will continue to be configured _without_
>> SSL+libevent.
>>
>> Best,
>> Kapil
>>
>>
>> On Wed, Jul 27, 2016 at 6:10 PM, Kapil Arya  wrote:
>>
>>> You can find the 1.0.0 rpm/deb packages at:
>>>
>>> http://open.mesosphere.com/downloads/mesos/#apache-mesos-1.0.0
>>>
>>>
>>> And here are the corresponding docker images based off of Ubuntu 14.04:
>>>
>>> mesosphere/mesos:1.0.0
>>> mesosphere/mesos-master:1.0.0
>>> mesosphere/mesos-slave:1.0.0
>>>
>>> Kapil
>>>
>>> On Wed, Jul 27, 2016 at 2:52 PM, Jeff Schroeder <
>>> jeffschroe...@computer.org> wrote:
>>>
 Small nit but can you s/experimnental/experimental/ under the "Storage"
 header in the release post please?

 Great work otherwise everyone!


 On Wednesday, July 27, 2016, Vinod Kone  wrote:

> Hi all,
>
> The vote for Mesos 1.0.0 (rc4) has passed with the following votes.
>
>
> +1 (Binding)
>
> --
>
> Kapil Arya
>
> Jie Yu
>
> Benjamin Mahler
>
>
> +1 (Non-binding)
>
> --
>
> Haosdent
>
> Greg Mann
>
> Zhitao Li
>
>
> +0
>
> -
>
> Yan Xu
>
>
> There were no  -1 votes.
>
>
> *NOTE: There were a couple known issues [MESOS-5911
> , MESOS-5913
> ] that couldn't be fixed
> in time for the 1.0. We plan to do a patch release to fix these ASAP.*
>
>
> Please find the release at:
>
> https://dist.apache.org/repos/dist/release/mesos/1.0.0
>
>
> It is recommended to use a mirror to download the release:
>
> http://www.apache.org/dyn/closer.cgi
>
>
> The CHANGELOG for the release is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_p
> lain;f=CHANGELOG;hb=1.0.0
>
>
> The mesos-1.0.0.jar has been released to:
>
> https://repository.apache.org
>
>
> The website (http://mesos.apache.org) will be updated shortly to
> reflect this release.
>
>
> Thanks,
>
> On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone 
> 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
>>

Re: Deactivationg framework unexpectly

[Anindya Sinha]

Looks like your framework (chronos) is sending a DeactivateFrameworkMessage 
message to the master. The scheduler driver would also send a 
DeativateFramework message if it is aborted 
(https://github.com/apache/mesos/blob/master/src/sched/sched.cpp#L1224 
).

Also, master can deactivate your framework if your framework disconnects or 
fails over. Please check logs in master or see if your framework received a 
FrameworkErrorMessage.

Thanks
Anindya 

> On Aug 8, 2016, at 3:35 AM, 志昌 余  wrote:
> 
> Hi,
> I recently faced a wired problem. I'm running mesos + chronos. Chronos 
> often (once every several days) stops scheduling tasks due to mesos deactived 
> the framework.
> As following is the log of mesos master leader:
> 
> # grep -iP "activat|disconnected" /var/log/mesos/mesos-master.INFO 
> I0806 13:40:33.14365830 master.cpp:2551] Deactivating framework 
> 90a6a7dc-7256-4e55-bd7e-573233c5df74- (chronos-2.5.0-SNAPSHOT) at 
> scheduler-86a64d22-5201-4bb0-8a2c-70d3e97afae6@10.8.139.246 
> :34544
> I0806 13:40:33.14390823 hierarchical.cpp:375] Deactivated framework 
> 90a6a7dc-7256-4e55-bd7e-573233c5df74-
> 
> The fix is to manually reboot the chronos leader.
> 
> My env:
> There are 3 physical machines, on each are running containerized mesos master 
> and chronos. When the issue occurred,  the mesos leader and chronos leader 
> were both running on the same machine.
> 
> Software Version:
> mesos-master:0.28.0-2.0.16.ubuntu1404
> chronos:2.5.0-ce4469d.ubuntu1404-mesos-0.28.0-2.0.16.ubuntu1404
> 
> Can anyone give insight for this problem?
> Thanks,
> Zhichang Yu

Mesos logging

[Hendrik Haddorp]

Hi,

the Mesos code contains log statements using LOG(INFO) and VLOG(1), for
example. So far I found that Mesos is using the Google Logging Library.
Looking in the logs I only seem to be able to find output from VLOG
statements. What do I need to do to get the output from the LOG
statements? Where would I typically find the output? I'm using CentOS
7.2 and found the output so far in the files below /var/log/mesos.

thanks,
Hendrik

Support for tasks groups aka pods in Mesos

[Vinod Kone]

Hi folks,

One of the most requested features in Mesos has been first class support
for managing pod like containers. We finally have some time to focus and
shepherd this work.

The epic tracking this work is :
https://issues.apache.org/jira/browse/MESOS-2449

Design doc: https://issues.apache.org/jira/browse/MESOS-2449

Your feedback on the design will be most welcome. Once we get agreement on
the design, we can start breaking down the epic into tickets.

Thanks,
Vinod & Jie

Re: Support for tasks groups aka pods in Mesos

[Vinod Kone]

Sorry, sent the wrong link earlier for design doc.

Design doc: https://issues.apache.org/jira/browse/MESOS-6009
>

Direct link:
https://docs.google.com/document/d/1FtcyQkDfGp-bPHTW4pUoqQCgVlPde936bo-IIENO_ho/edit#heading=h.ip4t59nlogfz

what's the pronunciation of "MESOS"?

[Yu Wei]

Thx,

Jared, (??)
Software developer
Interested in open source software, big data, Linux

Re: what's the pronunciation of "MESOS"?

[Joseph Jacks]

"MAY-zoss" is most common and correct. 

"MEH-zoss" is second most common and also correct, I think. 

"MEE-zoss" is third most common, but incorrect.

JJ.

> On Aug 8, 2016, at 10:48 PM, Yu Wei  wrote:
> 
> 
> Thx,
> 
> Jared, (韦煜）
> Software developer
> Interested in open source software, big data, Linux

Re: Mesos logging

[Charles Allen]

Which glog are you trying to capture? You can set the verbosity level with
the environment variable GLOG_v

And you can also set it through things like Spark. So if you want a lot of
ZK chatter at the mesos level in your spark logs, add

spark.executorEnv.GLOG_v=9

to your spark context

On Mon, Aug 8, 2016 at 2:53 PM Hendrik Haddorp 
wrote:

> Hi,
>
> the Mesos code contains log statements using LOG(INFO) and VLOG(1), for
> example. So far I found that Mesos is using the Google Logging Library.
> Looking in the logs I only seem to be able to find output from VLOG
> statements. What do I need to do to get the output from the LOG
> statements? Where would I typically find the output? I'm using CentOS
> 7.2 and found the output so far in the files below /var/log/mesos.
>
> thanks,
> Hendrik
>

Re: what's the pronunciation of "MESOS"?

[Yu Wei]

Thanks Joe.

It's really interesting.


Jared, (??)
Software developer
Interested in open source software, big data, Linux



From: Joseph Jacks 
Sent: Tuesday, August 9, 2016 10:53 AM
To: user@mesos.apache.org
Subject: Re: what's the pronunciation of "MESOS"?

"MAY-zoss" is most common and correct.

"MEH-zoss" is second most common and also correct, I think.

"MEE-zoss" is third most common, but incorrect.

JJ.

On Aug 8, 2016, at 10:48 PM, Yu Wei 
mailto:yu20...@hotmail.com>> wrote:



Thx,

Jared, (??)
Software developer
Interested in open source software, big data, Linux

Re: Mesos logging

[Hendrik Haddorp]

I would like to see the "docker run" trace from
https://github.com/apache/mesos/blob/master/src/docker/docker.cpp line 811.
What verbosity level does INFO map to?

On 09/08/16 05:06, Charles Allen wrote:
> Which glog are you trying to capture? You can set the verbosity level
> with the environment variable GLOG_v
>
> And you can also set it through things like Spark. So if you want a
> lot of ZK chatter at the mesos level in your spark logs, add 
>
> spark.executorEnv.GLOG_v=9
>
> to your spark context
>
> On Mon, Aug 8, 2016 at 2:53 PM Hendrik Haddorp
> mailto:hendrik.hadd...@gmx.net>> wrote:
>
> Hi,
>
> the Mesos code contains log statements using LOG(INFO) and
> VLOG(1), for
> example. So far I found that Mesos is using the Google Logging
> Library.
> Looking in the logs I only seem to be able to find output from VLOG
> statements. What do I need to do to get the output from the LOG
> statements? Where would I typically find the output? I'm using CentOS
> 7.2 and found the output so far in the files below /var/log/mesos.
>
> thanks,
> Hendrik
>