Re: Welcome Greg Mann as a new committer and PMC member!

[Jay Guo]

Congrats!! Well deserved!!

- Jay
On Wed, 14 Jun 2017 at 08:43 tommy xiao  wrote:

> Congrats Greg!
>
> 2017-06-14 8:05 GMT+08:00 Qian Zhang :
>
>> Congrats Greg!
>>
>>
>> Regards,
>> Qian Zhang
>>
>> On Wed, Jun 14, 2017 at 7:24 AM, Guang Ya Liu  wrote:
>>
>>> Congrats Greg!!! Very well deserved
>>>
>>> On Wed, Jun 14, 2017 at 7:04 AM, Klaus Ma 
>>> wrote:
>>>
>>> > Congrats!
>>> >
>>> >
>>> > On 14 Jun 2017, at 06:29, Ben Lin  wrote:
>>> >
>>> > Congrats Greg, well deserved!
>>> >
>>> > --
>>> > *From:* Jie Yu 
>>> > *Sent:* Wednesday, June 14, 2017 5:54:48 AM
>>> > *To:* user
>>> > *Cc:* dev
>>> > *Subject:* Re: Welcome Greg Mann as a new committer and PMC member!
>>> >
>>> > Congrats Greg!
>>> >
>>> > On Tue, Jun 13, 2017 at 2:42 PM, Vinod Kone 
>>> wrote:
>>> >
>>> >> Hi folks,
>>> >>
>>> >> Please welcome Greg Mann as the newest committer and PMC member of the
>>> >> Apache Mesos project.
>>> >>
>>> >> Greg has been an active contributor to the Mesos project for close to
>>> 2
>>> >> years now and has made many solid contributions. His biggest source
>>> code
>>> >> contribution to the project has been around adding authentication
>>> support
>>> >> for default executor. This was a major new feature that involved
>>> quite a
>>> >> few moving parts. Additionally, he also worked on improving the
>>> >> scheduler and executor APIs.
>>> >>
>>> >> Here is his more formal checklist for your perusal.
>>> >>
>>> >> https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_R
>>> >> 8JYRRc5spV0yKrpsGBw/edit
>>> >>
>>> >> Thanks,
>>> >> Vinod
>>> >>
>>> >>
>>> >
>>> >
>>>
>>
>>
>
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
>

Re: Welcome Greg Mann as a new committer and PMC member!

[tommy xiao]

Congrats Greg!

2017-06-14 8:05 GMT+08:00 Qian Zhang :

> Congrats Greg!
>
>
> Regards,
> Qian Zhang
>
> On Wed, Jun 14, 2017 at 7:24 AM, Guang Ya Liu  wrote:
>
>> Congrats Greg!!! Very well deserved
>>
>> On Wed, Jun 14, 2017 at 7:04 AM, Klaus Ma  wrote:
>>
>> > Congrats!
>> >
>> >
>> > On 14 Jun 2017, at 06:29, Ben Lin  wrote:
>> >
>> > Congrats Greg, well deserved!
>> >
>> > --
>> > *From:* Jie Yu 
>> > *Sent:* Wednesday, June 14, 2017 5:54:48 AM
>> > *To:* user
>> > *Cc:* dev
>> > *Subject:* Re: Welcome Greg Mann as a new committer and PMC member!
>> >
>> > Congrats Greg!
>> >
>> > On Tue, Jun 13, 2017 at 2:42 PM, Vinod Kone 
>> wrote:
>> >
>> >> Hi folks,
>> >>
>> >> Please welcome Greg Mann as the newest committer and PMC member of the
>> >> Apache Mesos project.
>> >>
>> >> Greg has been an active contributor to the Mesos project for close to 2
>> >> years now and has made many solid contributions. His biggest source
>> code
>> >> contribution to the project has been around adding authentication
>> support
>> >> for default executor. This was a major new feature that involved quite
>> a
>> >> few moving parts. Additionally, he also worked on improving the
>> >> scheduler and executor APIs.
>> >>
>> >> Here is his more formal checklist for your perusal.
>> >>
>> >> https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_R
>> >> 8JYRRc5spV0yKrpsGBw/edit
>> >>
>> >> Thanks,
>> >> Vinod
>> >>
>> >>
>> >
>> >
>>
>
>


-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

Re: Welcome Greg Mann as a new committer and PMC member!

[Qian Zhang]

Congrats Greg!


Regards,
Qian Zhang

On Wed, Jun 14, 2017 at 7:24 AM, Guang Ya Liu  wrote:

> Congrats Greg!!! Very well deserved
>
> On Wed, Jun 14, 2017 at 7:04 AM, Klaus Ma  wrote:
>
> > Congrats!
> >
> >
> > On 14 Jun 2017, at 06:29, Ben Lin  wrote:
> >
> > Congrats Greg, well deserved!
> >
> > --
> > *From:* Jie Yu 
> > *Sent:* Wednesday, June 14, 2017 5:54:48 AM
> > *To:* user
> > *Cc:* dev
> > *Subject:* Re: Welcome Greg Mann as a new committer and PMC member!
> >
> > Congrats Greg!
> >
> > On Tue, Jun 13, 2017 at 2:42 PM, Vinod Kone 
> wrote:
> >
> >> Hi folks,
> >>
> >> Please welcome Greg Mann as the newest committer and PMC member of the
> >> Apache Mesos project.
> >>
> >> Greg has been an active contributor to the Mesos project for close to 2
> >> years now and has made many solid contributions. His biggest source code
> >> contribution to the project has been around adding authentication
> support
> >> for default executor. This was a major new feature that involved quite a
> >> few moving parts. Additionally, he also worked on improving the
> >> scheduler and executor APIs.
> >>
> >> Here is his more formal checklist for your perusal.
> >>
> >> https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_R
> >> 8JYRRc5spV0yKrpsGBw/edit
> >>
> >> Thanks,
> >> Vinod
> >>
> >>
> >
> >
>

Re: Welcome Greg Mann as a new committer and PMC member!

[Guang Ya Liu]

Congrats Greg!!! Very well deserved

On Wed, Jun 14, 2017 at 7:04 AM, Klaus Ma  wrote:

> Congrats!
>
>
> On 14 Jun 2017, at 06:29, Ben Lin  wrote:
>
> Congrats Greg, well deserved!
>
> --
> *From:* Jie Yu 
> *Sent:* Wednesday, June 14, 2017 5:54:48 AM
> *To:* user
> *Cc:* dev
> *Subject:* Re: Welcome Greg Mann as a new committer and PMC member!
>
> Congrats Greg!
>
> On Tue, Jun 13, 2017 at 2:42 PM, Vinod Kone  wrote:
>
>> Hi folks,
>>
>> Please welcome Greg Mann as the newest committer and PMC member of the
>> Apache Mesos project.
>>
>> Greg has been an active contributor to the Mesos project for close to 2
>> years now and has made many solid contributions. His biggest source code
>> contribution to the project has been around adding authentication support
>> for default executor. This was a major new feature that involved quite a
>> few moving parts. Additionally, he also worked on improving the
>> scheduler and executor APIs.
>>
>> Here is his more formal checklist for your perusal.
>>
>> https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_R
>> 8JYRRc5spV0yKrpsGBw/edit
>>
>> Thanks,
>> Vinod
>>
>>
>
>

Re: Welcome Greg Mann as a new committer and PMC member!

[Klaus Ma]

Congrats!


> On 14 Jun 2017, at 06:29, Ben Lin  wrote:
> 
> Congrats Greg, well deserved!
> 
> From: Jie Yu 
> Sent: Wednesday, June 14, 2017 5:54:48 AM
> To: user
> Cc: dev
> Subject: Re: Welcome Greg Mann as a new committer and PMC member!
>  
> Congrats Greg!
> 
> On Tue, Jun 13, 2017 at 2:42 PM, Vinod Kone  > wrote:
> Hi folks,
> 
> Please welcome Greg Mann as the newest committer and PMC member of the Apache 
> Mesos project.
> 
> Greg has been an active contributor to the Mesos project for close to 2 years 
> now and has made many solid contributions. His biggest source code 
> contribution to the project has been around adding authentication support for 
> default executor. This was a major new feature that involved quite a few 
> moving parts. Additionally, he also worked on improving the scheduler and 
> executor APIs.
> 
> Here is his more formal checklist for your perusal.
> 
> https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_R8JYRRc5spV0yKrpsGBw/edit
>  
> 
> 
> Thanks,
> Vinod
> 
> 

Re: Welcome Greg Mann as a new committer and PMC member!

[Jie Yu]

Congrats Greg!

On Tue, Jun 13, 2017 at 2:42 PM, Vinod Kone  wrote:

> Hi folks,
>
> Please welcome Greg Mann as the newest committer and PMC member of the
> Apache Mesos project.
>
> Greg has been an active contributor to the Mesos project for close to 2
> years now and has made many solid contributions. His biggest source code
> contribution to the project has been around adding authentication support
> for default executor. This was a major new feature that involved quite a
> few moving parts. Additionally, he also worked on improving the scheduler
> and executor APIs.
>
> Here is his more formal checklist for your perusal.
>
> https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_
> R8JYRRc5spV0yKrpsGBw/edit
>
> Thanks,
> Vinod
>
>

Re: Welcome Greg Mann as a new committer and PMC member!

[Avinash Sridharan]

Awesome !! Congrats Greg !!

On Tue, Jun 13, 2017 at 2:44 PM, Neil Conway  wrote:

> Congratulations, Greg!! Very well-deserved. Looking forward to
> continuing to work with you on the project.
>
> Neil
>
>
> On Tue, Jun 13, 2017 at 2:42 PM, Vinod Kone  wrote:
> > Hi folks,
> >
> > Please welcome Greg Mann as the newest committer and PMC member of the
> > Apache Mesos project.
> >
> > Greg has been an active contributor to the Mesos project for close to 2
> > years now and has made many solid contributions. His biggest source code
> > contribution to the project has been around adding authentication support
> > for default executor. This was a major new feature that involved quite a
> few
> > moving parts. Additionally, he also worked on improving the scheduler and
> > executor APIs.
> >
> > Here is his more formal checklist for your perusal.
> >
> > https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_
> R8JYRRc5spV0yKrpsGBw/edit
> >
> > Thanks,
> > Vinod
> >
>



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

Welcome Greg Mann as a new committer and PMC member!

[Vinod Kone]

Hi folks,

Please welcome Greg Mann as the newest committer and PMC member of the
Apache Mesos project.

Greg has been an active contributor to the Mesos project for close to 2
years now and has made many solid contributions. His biggest source code
contribution to the project has been around adding authentication support
for default executor. This was a major new feature that involved quite a
few moving parts. Additionally, he also worked on improving the scheduler
and executor APIs.

Here is his more formal checklist for your perusal.

https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_R8JYRRc5spV0yKrpsGBw/edit

Thanks,
Vinod

Re: Confusion about the two different approaches of implementing a scheduler

[Wenzhao Zhang]

Hi, Vinod:
Thanks for the quick response.

For both approaches, the client creates the scheduler locally, via
self-defined call-back functions, and uses the scheduler locally.
I'm wondering if this is a fixed pattern?

My boss talks about creating some kind of a "remote" scheduler, interacting
with both the master and the client via remove calls.  I think it should be
started independently, rather than by a client.
Is there any existing case for this idea?

Thanks
Wenzhao


On Tue, Jun 13, 2017 at 2:29 PM, Vinod Kone  wrote:

> Hi WenZhao,
>
> v1 is definitely the recommended way to go if you are building a new
> scheduler today. v0 will be deprecated at some point. Since v0 API has been
> around much longer than v1, it is not surprising that most online
> tutorials/docs reference that.
>
> Thanks,
>
> On Tue, Jun 13, 2017 at 11:25 AM, Wenzhao Zhang  wrote:
>
> > Hi, All:
> > I'm developing my own scheduler, but become confused about two different
> > approaches.
> >
> > In "*src/cli/execute.cpp*", it defines its own call-back functions, and
> > uses "*src/scheduler/scheduler.cpp*" to interact with the master.   I
> > think
> > this can be named as "*v1*", given the names of the header file and
> > namespace.
> >
> > But in the online official document and many other tutorials, they all
> talk
> > about "*include/mesos/scheduler.hpp*", which is partially implemented
> in "
> > *src/sched/sched.cpp*". And I remember someone names this as old-version
> or
> > "*v0*" (please correct me if I'm wrong).
> >
> > I'm confused about the two different approaches.
> > "v1" only supports "Event", while "v0" supports both "Message" and
> "Event".
> > "v1" is officially used in the source-code.  But almost all online
> > tutorials talk about "v0".
> > And it seems that the two approaches aren't compatible with each other,
> as
> > I get a lot compiling errors if I import/use both header filers in a
> single
> > file.
> >
> > So, is there some "best practice" suggestion? I suppose one approach will
> > gradually become obsolete?
> > Which approach should I adopt?
> > And I believe the answer can also explain the difference between
> > "src/executor" and "src/exec" ?
> >
> > Thanks very much for your time
> > Wenzhao
> >
>

[GitHub] mesos issue #205: Clarify existence of FrameworkID in SUBSCRIBE calls.

[vinodkone]

Github user vinodkone commented on the issue:

https://github.com/apache/mesos/pull/205
  
@hatred still planning to review this?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Confusion about the two different approaches of implementing a scheduler

[Vinod Kone]

Hi WenZhao,

v1 is definitely the recommended way to go if you are building a new
scheduler today. v0 will be deprecated at some point. Since v0 API has been
around much longer than v1, it is not surprising that most online
tutorials/docs reference that.

Thanks,

On Tue, Jun 13, 2017 at 11:25 AM, Wenzhao Zhang  wrote:

> Hi, All:
> I'm developing my own scheduler, but become confused about two different
> approaches.
>
> In "*src/cli/execute.cpp*", it defines its own call-back functions, and
> uses "*src/scheduler/scheduler.cpp*" to interact with the master.   I
> think
> this can be named as "*v1*", given the names of the header file and
> namespace.
>
> But in the online official document and many other tutorials, they all talk
> about "*include/mesos/scheduler.hpp*", which is partially implemented in "
> *src/sched/sched.cpp*". And I remember someone names this as old-version or
> "*v0*" (please correct me if I'm wrong).
>
> I'm confused about the two different approaches.
> "v1" only supports "Event", while "v0" supports both "Message" and "Event".
> "v1" is officially used in the source-code.  But almost all online
> tutorials talk about "v0".
> And it seems that the two approaches aren't compatible with each other, as
> I get a lot compiling errors if I import/use both header filers in a single
> file.
>
> So, is there some "best practice" suggestion? I suppose one approach will
> gradually become obsolete?
> Which approach should I adopt?
> And I believe the answer can also explain the difference between
> "src/executor" and "src/exec" ?
>
> Thanks very much for your time
> Wenzhao
>

[GitHub] mesos pull request #217: Add python-mesos-http scheduler api client

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/mesos/pull/217


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #218: MESOS-7654 Fix owner of fetched files in docker con...

[lycing]

Github user lycing closed the pull request at:

https://github.com/apache/mesos/pull/218


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #218: MESOS-7654 Fix owner of fetched files in docker containeri...

[lycing]

Github user lycing commented on the issue:

https://github.com/apache/mesos/pull/218
  
this bug is fixed already, close it.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos issue #218: MESOS-7654 Fix owner of fetched files in docker containeri...

[bbannier]

Github user bbannier commented on the issue:

https://github.com/apache/mesos/pull/218
  
For code changes like this one we prefer working with our JIRA and 
reviewboard, https://mesos.apache.org/documentation/latest/submitting-a-patch/. 
Could you submit a review request to reviewboard? You probably also want to 
assign the issue to you.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #218: MESOS-7654 Fix owner of fetched files in docker con...

[lycing]

GitHub user lycing opened a pull request:

https://github.com/apache/mesos/pull/218

MESOS-7654 Fix owner of fetched files in docker containerizer

Fix the wrong owner while mesos-fetcher downloading files，and test passed 
in our production environment，from issue 
[MESOS-7654](https://issues.apache.org/jira/browse/MESOS-7654)
@jieyu @Gilbert88 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lycing/mesos master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/218.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #218


commit 8f740dc28a06b055572311ffef8f59aba0ea0eac
Author: lycing 
Date:   2017-06-13T10:43:05Z

Update docker.cpp

fix the wrong owner while mesos-fetcher download files

commit 0a07fed19017b21d5d448746f0870dd374f3a76d
Author: LiuYanchun 
Date:   2017-06-13T14:15:51Z

Fix owner of fetched files in docker containerizer




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] mesos pull request #217: Add python-mesos-http scheduler api client

[osallou]

GitHub user osallou opened a pull request:

https://github.com/apache/mesos/pull/217

Add python-mesos-http scheduler api client

Hi,
I propose the following scheduler python lib as external library to use 
Mesos HTTP API

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/osallou/mesos master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/mesos/pull/217.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #217


commit beb4fa20c9640a67e6394b928d9706fee790d1af
Author: Olivier Sallou 
Date:   2017-06-13T08:51:04Z

Add python-mesos-http scheduler api client




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---