Need shepherd for MESOS-4353 [Limit the number of processes created by libprocess]

https://issues.apache.org/jira/browse/MESOS-4353 Thanks.

Re: Mesos 0.27.1

Hi Travis, It slipped through the cracks, sorry about that! I have now assigned myself as the shepherd on the Jira ticket and will get you the feedback on the review request later Today. Best, Kapil On Tue, Feb 9, 2016 at 8:19 AM, Hegner, Travis wrote: > Thanks Adam,

Re: Apache Mesos Community Sync

Our next community sync will be on Thursday, February 11, 2016 at 9am PST. To join in person, come to Mesosphere HQ at 88 Stevenson St. and see the reception on the 2nd floor. Please add your agenda items to the Google Doc

Re: Endpoint documentation is now published!

It looks great! Thanks Ben, Kevin, and Neil for putting this together :) On 8 February 2016 at 23:56, Benjamin Mahler wrote: > Agreed, thanks for the links. > > I had mentioned looking into swagger to a few folks when we started doing > this, but we realized we needed to

Re: China Mesos Developers Wechat Group

Thank you very much, adam. Now I know why @Gilbert told me he could not saw the image last night. Let me send this through a link. The QR code link: http://i13.tietuku.com/d95e584fa4815860.jpg On Tue, Feb 9, 2016 at 3:33 PM, Adam Bordelon wrote: > Haosdent, I think Apache

Slave Terminology Rename Proposal

Hello Everyone, The initial proposal for the slave to agent rename has been added to the Epic JIRA item: https://issues.apache.org/jira/browse/MESOS-1478 for your review. The link to the proposal working document is posted in the description of the JIRA item. Your comments/feedback would be

RE: Mesos 0.27.1

Thanks Adam, Kapil offered to shepherd it originally, but I haven't heard from him. Haosdent has been providing some feedback on the review board, and I have addressed all raised issues. What else can I do to keep it moving? Travis -Original Message- From: Adam Bordelon

IPv6 progress / Default listening socket

Hi all, sorry in advance for the wall of text below :) I went ahead and implemented a proof-of-concept, and things seem to work quite well so far: I have a mesos-master and a mesos-slave on different machines in an IPv6-only network, and I'm able run RENDLER jobs on them. The one unexpected

Reorganize 3rdparty directory

Hi All, TLDR: Move everything from 3rdparty/libprocess/3rdparty/* into 3rdparty/. (Optionally) Move libprocess/stout to the top-level directory. I wanted to start some discussion around reorganizing stuff inside "3rdparty". I apologize for the length of the email, please bear with me.

Re: Reorganize 3rdparty directory

> > However, in the current code base, we don't strictly follow the 3rdparty > structure. For example, stout has a dependency on picojson and > google-protobuf, but we don't put these two packages inside > 3rdparty/libprocess/3rdparty/stout/3rdparty/. My understanding is that stout is header

Re: Reorganize 3rdparty directory

On Tue, Feb 9, 2016 at 7:20 PM, Jie Yu wrote: > > > > > However, in the current code base, we don't strictly follow the 3rdparty > > structure. For example, stout has a dependency on picojson and > > google-protobuf, but we don't put these two packages inside > >

Re: Reorganize 3rdparty directory

Kapil, I guess what I want to understand is why the existing structure makes it hard for you to do the things that you want to do (installing module-specific 3rdparty dependencies into "${pkglibdir}/3rdparty" as part of "make install"). The only reason you mentioned in the original email is that

Re: Reorganize 3rdparty directory

On Tue, Feb 9, 2016 at 8:23 PM, Jie Yu wrote: > Kapil, > > I guess what I want to understand is why the existing structure makes it > hard for you to do the things that you want to do (installing > module-specific 3rdparty dependencies into "${pkglibdir}/3rdparty" as part >