need help/shepherd on MESOS-1806

2015-09-17 Thread Shuai Lin 
Hi,

I am working on MESOS-1806 (substitute zookeeper with etcd) based on the
former work of Cody Maloney.  After a general understanding of mesos code
base, this week I rebased the code to the latest master (with necessary
changes), and it compiles well. The code is here:
https://github.com/lins05/mesos/tree/etcd

However, when running the tests

I got some error:

Recovery failed: Failed to recover registrar: Failed to perform fetch
> within 1mins
>

However, I don't think the changes on my branch does anything to the
registrar and replicated logs modules.

Can anyone help/shepherd on this?

Regards,
Shuai

Re: Failed to build Mesos module

2015-09-17 Thread Qian AZ Zhang 

Hi Kapil,

Any updates? :-)

I have resolved that issue with a workaround by using the option
"--disable-java", like:
../configure --with-glog=/usr --with-protobuf=/usr --with-boost=/usr
--disable-java
And then I did "make" and "make install" successfully.

However, after I cloned the code from https://github.com/mesos/modules and
found an error to build it:
$ ../configure --with-mesos=/usr/local
checking for gcc... gcc
checking whether the C compiler works... yes
...
checking for google/protobuf/message.h... yes
checking picojson.h usability... no
checking picojson.h presence... no
checking for picojson.h... no
configure: error: picojson is not installed.

So it can not find picojson.h. And I checked the source code tree of Mesos,
and found picojson as a 3rd party lib are here:
mesos/3rdparty/libprocess/3rdparty/picojson-4f93734.tar.gz, maybe we should
put the picojson.h to /usr/local/include during "make install"?


Regards,
Qian Zhang



From:   Kapil Arya 
To: dev 
Date:   09/18/2015 00:34
Subject:Re: Failed to build Mesos module



I'll take a look shortly and will report back with the status.

Kapil


On Thu, Sep 17, 2015 at 10:56 AM, Qian AZ Zhang 
wrote:

> Thanks Kapil.
>
> I am now following the steps in https://github.com/mesos/modules to build
> my module, but it failed:
> stack@u1404u1:~/mesos/build$ ../configure --with-glog=/usr/local
> --with-protobuf=/usr/local --with-boost=/usr/local
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking target system type... x86_64-unknown-linux-gnu
> ...
> checking for /usr/share/java/protobuf.jar... no
> configure: error: cannot find PROTOBUF_JAR=/usr/share/java/protobuf.jar
>
> And I have already installed protobuf, glog and boost libraries in my
> machine with the command:
> sudo apt-get install libprotobuf-dev libboost-dev libgoogle-glog-dev
>
> Can you please help? Thanks!
>
>
> Regards,
> Qian Zhang
>
> [image: Inactive hide details for Kapil Arya ---09/17/2015
> 21:50:55---Hello Qian, Please follow the instructions on
> https://github.com/]Kapil Arya ---09/17/2015 21:50:55---Hello Qian,
> Please follow the instructions on https://github.com/mesos/modules to get
>
> From: Kapil Arya 
> To: dev 
> Date: 09/17/2015 21:50
> Subject: Re: Failed to build Mesos module
> --
>
>
>
> Hello Qian,
>
> Please follow the instructions on https://github.com/mesos/modules to get
> up and running with building a mesos module. Apparently, building mesos
> modules requires you to build Mesos without bundled protobuf, glog and
> boost libraries. Thus, you need to have them installed system wide. The
> above repo has a readme and a few test modules that you can play with.
>
> Please let us know if you need any more help.
>
> Kapil
>
> On Thu, Sep 17, 2015 at 9:20 AM, Qian AZ Zhang 
> wrote:
>
> >
> >
> > Hi all,
> >
> > I am trying to follow the doc (
> >
> >
>
https://github.com/apache/mesos/blob/master/docs/modules.md#writing-mesos-modules

> > ) to implement a test module, but when I built the module, I got the
> > following error:
> > user1@test1:~/mesos/src/examples$ g++ -lmesos -fpic -o
test_module.o
> > test_module.cpp
> > In file included from /usr/local/include/mesos/mesos.hpp:22:0,
> >  from test_module.hpp:22,
> >  from test_module.cpp:2:
> > /usr/local/include/mesos/mesos.pb.h:9:42: fatal error:
> > google/protobuf/stubs/common.h: No such file or directory
> >  #include 
> > ^
> > compilation terminated.
> >
> > It seems it can not find the header file:
> google/protobuf/stubs/common.h. I
> > see this header file is in the Mesos source code tree, but not in
> > /usr/local/include/mesos ( I have done "make install" after building
> Mesos
> > source code).
> >
> > Any help will be appreciated, thanks!
> >
> >
> > Regards,
> > Qian Zhang
>
>

Re: seeking a shepherd for autotools build changes

2015-09-17 Thread James Peach 

> On Sep 17, 2015, at 10:04 AM, Adam Bordelon  wrote:
> 
> James, we're certainly interested, but TimSt.Clair, our committer build
> expert is relatively inactive lately, so we should find another shepherd. I
> trust Cody's build expertise, and he's already given a couple of looks, but
> he's not (yet) a committer. Maybe a committer can pair with him to review
> and land these patches.

Thanks Adam. To clarify, I'm totally OK with dropping these, just looking for 
some guidance :)

> On Thu, Sep 17, 2015 at 9:44 AM, James Peach  wrote:
> 
>> 
>>> On Sep 1, 2015, at 4:02 PM, Vinod Kone  wrote:
>>> 
>>> Tim, looks like you already reviewed some of these patches? Do you have
>>> cycles to shepherd this?
>> 
>> Is there any interest in this? Should I just close out the JIRA?
>> 
>>> 
>>> On Wed, Aug 26, 2015 at 1:16 PM, James Peach  wrote:
>>> 
 Hi all,
 
 Is anyone willing to shepherd or otherwise provide feedback on
>> MESOS-2537?
 
   https://reviews.apache.org/r/33752/
   https://reviews.apache.org/r/35084/
   https://reviews.apache.org/r/35234/
 
 This improves the --enable-foo handling so that you can safely specify
>> the
 default (without receiving the opposite). Is also extracts handling of
 bundled dependencies into macros so that they are handled consistently.
 
 thanks,
 James
>> 
>>

Re: Mesos 0.25.0

2015-09-17 Thread Joris Van Remoortere 
As mentioned by Vinod in the Community Developer Meeting, we will be having
a 0.25.0 rc1 triage meeting Friday September 18th at 10:30am Pacific Time.
If you are interested in attending or are heavily engaged in the remaining
tickets please reach out to me if you would like to join the meeting. I
will try my best to accommodate everyone in the hangout.
Regardless, your shepherd will reach out to you if you have patches
outstanding targeted for 0.25.0.

The meeting will move quickly through the remaining issues, their
shepherds, and what is critical.

Joris

On Wed, Sep 16, 2015 at 7:56 PM, Michael Park  wrote:

> We have created the new target version for 0.26.0 and have cut out what
> we're planning to land for 0.25.0 on the 0.25.0 dashboard.
>
> Please set your target version to 0.26.0 unless it's a critical issue that
> needs to get into 0.25.0!
>
> Thanks,
>
> Joris, MPark, and Niklas
>
> On Mon, Sep 14, 2015, 9:23 AM Joris Van Remoortere 
> wrote:
>
> > Following in the footsteps of the dashboard for the 0.23.0 release,
> > here is the Mesos 0.25.0 Release Dashboard
> > <
> >
> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12326859
> > >
> >
> > This dashboard was very successful at reducing the time required to
> triage
> > the first release candidate. Let's repeat that same success!
> >
> > A special thanks to Adam for providing us with this great template.
> >
> > Joris, Mpark, and Niklas
> >
>

Re: seeking a shepherd for autotools build changes

2015-09-17 Thread Adam Bordelon 
James, we're certainly interested, but TimSt.Clair, our committer build
expert is relatively inactive lately, so we should find another shepherd. I
trust Cody's build expertise, and he's already given a couple of looks, but
he's not (yet) a committer. Maybe a committer can pair with him to review
and land these patches.

On Thu, Sep 17, 2015 at 9:44 AM, James Peach  wrote:

>
> > On Sep 1, 2015, at 4:02 PM, Vinod Kone  wrote:
> >
> > Tim, looks like you already reviewed some of these patches? Do you have
> > cycles to shepherd this?
>
> Is there any interest in this? Should I just close out the JIRA?
>
> >
> > On Wed, Aug 26, 2015 at 1:16 PM, James Peach  wrote:
> >
> >> Hi all,
> >>
> >> Is anyone willing to shepherd or otherwise provide feedback on
> MESOS-2537?
> >>
> >>https://reviews.apache.org/r/33752/
> >>https://reviews.apache.org/r/35084/
> >>https://reviews.apache.org/r/35234/
> >>
> >> This improves the --enable-foo handling so that you can safely specify
> the
> >> default (without receiving the opposite). Is also extracts handling of
> >> bundled dependencies into macros so that they are handled consistently.
> >>
> >> thanks,
> >> James
>
>

Re: Apache Mesos Community Sync

2015-09-17 Thread Adam Bordelon 
Today's community sync video/audio is archived at:
http://youtu.be/ZQT6-fw8Ito
The meeting agenda/notes are available at:
https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit?usp=sharing

For convenience, today's notes are reproduced below:

   -

   0.21.2-0.24.1 Patch Releases [Adam]
   -

  What’s the plan for how many releases we want to support? BenH:
  Support at least 3 versions (e.g. 0.22.x, 0.23.x, 0.24.x) for
which we will
  do patch fixes
  Neil: Or support an LTS version + recent releases
  -

  Separate Release Manager for backports? Joris and MPark will RM for
  these patch releases, with Adam shepherding. In general, patch/point
  releases don’t need to be managed by the same person who did the original
  release.
  -

  Need some guidelines (on the website) for what is a
  backport-able/critical patch.
  -

  AI[Adam+0.25RMs]: Expand Release Guide with # supported releases,
  guidelines for critical patches, RM roles/responsibilities
  -

   0.25.0 Release Planning[Joris]: Dashboard
   
   -

  Planning a triage meeting for Friday, hope to cut 0.25.0-rc1 by Sept.
  23rd.
  -

   MesosCon EU [Adam]: Schedule announced! http://mesosconeu2015.sched.org/
   -

  Register! Attend! Meet cool people! Learn awesome things!
  -

  Want to grow developer community as well as user community
  -

  Community voting vs. Program Committee selection?
  -

   Mesos Developer Community Sync Frequency to weekly [Joris, BenH]
   -

  Rotating time for time zones
  -

  Weeklys can be video/hangout
  -

  1/mo can be on-site @Twitter/Mesosphere/etc
  -

  AI [Joris]: Send out email proposal for times, weekly schedule
  -

  Proposal: Send each meeting’s notes to dev list (in plain text)
  afterwards
  -

   ReviewBot needs more OS/Compiler coverage [Joseph, Joris]
   -

  ReviewBot != Jenkins continuous build
  -

   MESOS-3147: Allocator Refactor project kick off, want to discuss more
   for how we can proceed this. [Guangya, MPark, AlexR]
   -

  Shepherd: MPark
  -

  Reviewer: AlexR
  -

  working group for this project
  -

 members: IBM, ?/
 -

  Gather more requirement/use-cases in a doc first
  -

   [Impromptu from Micheal@twitter] framework dev kit - File a JIRA ticket
   and start collecting user-stories so as to understand scope. From BenH: May
   require user-group at some point.
   -

WRT growing the developer community ... does anyone want to
   speak about the process of getting a shepherd?
   -

   jpeach: Short answer: email the dev@ list. Long answer:
  we can discuss it at the next community sync
  -

  There will be a talk at MesosCon EU about this as well


On Thu, Sep 17, 2015 at 8:32 AM, Joris Van Remoortere 
wrote:

> Youtube on-air: http://youtu.be/ZQT6-fw8Ito
> Speakers channel:
> https://plus.google.com/hangouts/_/hoaevent/AP36tYd59qP_P4ac-NwOI7LztI_hBsku54gXqk1DhFGsKkne_cmByA
>
> On Mon, Sep 14, 2015 at 7:02 PM, Adam Bordelon  wrote:
>
>> We'll have the next community sync this Thursday (Sept. 17th) at 8:30am
>> Pacific.
>>
>> Please add items to the agenda
>> 
>> .
>>
>> We will try Hangouts on Air this time. We will post the video stream link
>> shortly before the meeting, and only active participants (especially people
>> on the agenda) should join the actual hangout. Others can watch the video
>> stream and ask brief questions on #mesos on IRC. If you have something
>> lengthier to discuss, put it on the agenda and ping us on email/IRC to get
>> into the hangout. We hope this works better for everyone.
>>
>>
>> On Wed, Sep 2, 2015 at 12:34 PM, Vinod Kone  wrote:
>>
>>> We'll have the next community sync tomorrow (Sept 3rd) at 3 PM PST.
>>>
>>> Please add items to agenda
>>> 
>>> .
>>>
>>>
>>> On Wed, Aug 5, 2015 at 4:12 PM, Vinod Kone  wrote:
>>>
 We'll have the next community sync tomorrow at 3 PM PST.

 Please add items to agenda
 
 .

 Thanks,

 On Thu, Jul 2, 2015 at 11:24 AM, Joris Van Remoortere <
 jo...@mesosphere.io> wrote:

> Reminder: The Mesos Community Developer Sync will be happening today
> at 3pm Pacific.
>
> To participate remotely, join the Google hangout:
> https://plus.google.com/hangouts/_/twitter.com/mesos-sync
>
> On Thu, Jun 18, 2015 at 7:22 AM, Adam Bordelon 
> wrote:
>
>> Reminder: We're hosting a developer community sync at Mes

Re: seeking a shepherd for autotools build changes

2015-09-17 Thread James Peach 

> On Sep 1, 2015, at 4:02 PM, Vinod Kone  wrote:
> 
> Tim, looks like you already reviewed some of these patches? Do you have
> cycles to shepherd this?

Is there any interest in this? Should I just close out the JIRA?

> 
> On Wed, Aug 26, 2015 at 1:16 PM, James Peach  wrote:
> 
>> Hi all,
>> 
>> Is anyone willing to shepherd or otherwise provide feedback on MESOS-2537?
>> 
>>https://reviews.apache.org/r/33752/
>>https://reviews.apache.org/r/35084/
>>https://reviews.apache.org/r/35234/
>> 
>> This improves the --enable-foo handling so that you can safely specify the
>> default (without receiving the opposite). Is also extracts handling of
>> bundled dependencies into macros so that they are handled consistently.
>> 
>> thanks,
>> James

Re: Failed to build Mesos module

2015-09-17 Thread Kapil Arya 
I'll take a look shortly and will report back with the status.

Kapil


On Thu, Sep 17, 2015 at 10:56 AM, Qian AZ Zhang  wrote:

> Thanks Kapil.
>
> I am now following the steps in https://github.com/mesos/modules to build
> my module, but it failed:
> stack@u1404u1:~/mesos/build$ ../configure --with-glog=/usr/local
> --with-protobuf=/usr/local --with-boost=/usr/local
> checking build system type... x86_64-unknown-linux-gnu
> checking host system type... x86_64-unknown-linux-gnu
> checking target system type... x86_64-unknown-linux-gnu
> ...
> checking for /usr/share/java/protobuf.jar... no
> configure: error: cannot find PROTOBUF_JAR=/usr/share/java/protobuf.jar
>
> And I have already installed protobuf, glog and boost libraries in my
> machine with the command:
> sudo apt-get install libprotobuf-dev libboost-dev libgoogle-glog-dev
>
> Can you please help? Thanks!
>
>
> Regards,
> Qian Zhang
>
> [image: Inactive hide details for Kapil Arya ---09/17/2015
> 21:50:55---Hello Qian, Please follow the instructions on
> https://github.com/]Kapil Arya ---09/17/2015 21:50:55---Hello Qian,
> Please follow the instructions on https://github.com/mesos/modules to get
>
> From: Kapil Arya 
> To: dev 
> Date: 09/17/2015 21:50
> Subject: Re: Failed to build Mesos module
> --
>
>
>
> Hello Qian,
>
> Please follow the instructions on https://github.com/mesos/modules to get
> up and running with building a mesos module. Apparently, building mesos
> modules requires you to build Mesos without bundled protobuf, glog and
> boost libraries. Thus, you need to have them installed system wide. The
> above repo has a readme and a few test modules that you can play with.
>
> Please let us know if you need any more help.
>
> Kapil
>
> On Thu, Sep 17, 2015 at 9:20 AM, Qian AZ Zhang 
> wrote:
>
> >
> >
> > Hi all,
> >
> > I am trying to follow the doc (
> >
> >
> https://github.com/apache/mesos/blob/master/docs/modules.md#writing-mesos-modules
> > ) to implement a test module, but when I built the module, I got the
> > following error:
> > user1@test1:~/mesos/src/examples$ g++ -lmesos -fpic -o test_module.o
> > test_module.cpp
> > In file included from /usr/local/include/mesos/mesos.hpp:22:0,
> >  from test_module.hpp:22,
> >  from test_module.cpp:2:
> > /usr/local/include/mesos/mesos.pb.h:9:42: fatal error:
> > google/protobuf/stubs/common.h: No such file or directory
> >  #include 
> > ^
> > compilation terminated.
> >
> > It seems it can not find the header file:
> google/protobuf/stubs/common.h. I
> > see this header file is in the Mesos source code tree, but not in
> > /usr/local/include/mesos ( I have done "make install" after building
> Mesos
> > source code).
> >
> > Any help will be appreciated, thanks!
> >
> >
> > Regards,
> > Qian Zhang
>
>

Re: Apache Mesos Community Sync

2015-09-17 Thread Joris Van Remoortere 
Youtube on-air: http://youtu.be/ZQT6-fw8Ito
Speakers channel:
https://plus.google.com/hangouts/_/hoaevent/AP36tYd59qP_P4ac-NwOI7LztI_hBsku54gXqk1DhFGsKkne_cmByA

On Mon, Sep 14, 2015 at 7:02 PM, Adam Bordelon  wrote:

> We'll have the next community sync this Thursday (Sept. 17th) at 8:30am
> Pacific.
>
> Please add items to the agenda
> 
> .
>
> We will try Hangouts on Air this time. We will post the video stream link
> shortly before the meeting, and only active participants (especially people
> on the agenda) should join the actual hangout. Others can watch the video
> stream and ask brief questions on #mesos on IRC. If you have something
> lengthier to discuss, put it on the agenda and ping us on email/IRC to get
> into the hangout. We hope this works better for everyone.
>
>
> On Wed, Sep 2, 2015 at 12:34 PM, Vinod Kone  wrote:
>
>> We'll have the next community sync tomorrow (Sept 3rd) at 3 PM PST.
>>
>> Please add items to agenda
>> 
>> .
>>
>>
>> On Wed, Aug 5, 2015 at 4:12 PM, Vinod Kone  wrote:
>>
>>> We'll have the next community sync tomorrow at 3 PM PST.
>>>
>>> Please add items to agenda
>>> 
>>> .
>>>
>>> Thanks,
>>>
>>> On Thu, Jul 2, 2015 at 11:24 AM, Joris Van Remoortere <
>>> jo...@mesosphere.io> wrote:
>>>
 Reminder: The Mesos Community Developer Sync will be happening today at
 3pm Pacific.

 To participate remotely, join the Google hangout:
 https://plus.google.com/hangouts/_/twitter.com/mesos-sync

 On Thu, Jun 18, 2015 at 7:22 AM, Adam Bordelon 
 wrote:

> Reminder: We're hosting a developer community sync at Mesosphere HQ
> this morning from 9-11am Pacific.
>
> The agenda is pretty bare, so please add more topics you would like to
> discuss:
>
> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit
>
> If you want to join in person, just show up to 88 Stevenson St, ring
> the buzzer, take the elevator up to 2nd floor, and then you can take the
> stairs up to the 3rd floor dining room, or ask somebody to let you up the
> elevator to the 3rd floor.
>
> To participate remotely, join the Google hangout:
> https://plus.google.com/hangouts/_/mesosphere.io/mesos-developer
>
> On Mon, Jun 15, 2015 at 10:46 AM, Adam Bordelon 
> wrote:
>
>> As previously mentioned, we would like to host additional Mesos
>> developer syncs at our new Mesosphere HQ at 88 Stevenson St (tucked 
>> behind
>> Market & 2nd), starting this Thursday from 9-11am Pacific. We opted for 
>> an
>> earlier slot so that the European developer community can participate.
>>
>> Now that we are having these more frequently, it would be great to
>> dive deeper into designs for upcoming features as well as discuss
>> longstanding issues. While high-level status updates are useful, they
>> should be a small part of these meetings so that we can address issues
>> currently facing our developers.
>>
>> Please add agenda items to the same doc we've been using for previous
>> meetings' Agenda/Notes:
>>
>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit
>>
>> Join in person if you can, or join remotely via hangout:
>> https://plus.google.com/hangouts/_/mesosphere.io/mesos-developer
>>
>> Thanks,
>> -Adam-
>>
>>
>> On Thu, May 28, 2015 at 10:08 AM, Vinod Kone 
>> wrote:
>>
>>> Cool.
>>>
>>> Here's the agenda doc
>>> <
>>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit#
>>> >
>>> for next week that folks can fill in.
>>>
>>> On Thu, May 28, 2015 at 9:52 AM, Adam Bordelon 
>>> wrote:
>>>
>>> > Looks like next week, Thursday June 4th on my calendar.
>>> > I thought it was always the first Thursday of the month.
>>> >
>>> > On Thu, May 28, 2015 at 9:33 AM, Vinod Kone 
>>> wrote:
>>> >
>>> > > Do we have community sync today or next week? I'm a bit confused.
>>> > >
>>> > > @vinodkone
>>> > >
>>> > > > On Apr 1, 2015, at 3:18 AM, Adam Bordelon 
>>> wrote:
>>> > > >
>>> > > > Reminder: We're having another Mesos Developer Community Sync
>>> this
>>> > > > Thursday, April 2nd from 3-5pm Pacific.
>>> > > >
>>> > > > Agenda:
>>> > > >
>>> > >
>>> >
>>> https://docs.google.com/document/d/153CUCj5LOJCFAVpdDZC7COJDwKh9RDjxaTA0S7lzwDA/edit?usp=sharing
>>> > > > To Join: follow the BlueJeans instructions from the recurring
>>> meeting
>>> > > > invite at the start

Re: Failed to build Mesos module

2015-09-17 Thread Qian AZ Zhang 

Thanks Kapil.

I am now following the steps in https://github.com/mesos/modules to build
my module, but it failed:
stack@u1404u1:~/mesos/build$ ../configure --with-glog=/usr/local
--with-protobuf=/usr/local --with-boost=/usr/local
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
...
checking for /usr/share/java/protobuf.jar... no
configure: error: cannot find PROTOBUF_JAR=/usr/share/java/protobuf.jar

And I have already installed protobuf, glog and boost libraries in my
machine with the command:
sudo apt-get install libprotobuf-dev libboost-dev libgoogle-glog-dev

Can you please help? Thanks!


Regards,
Qian Zhang



From:   Kapil Arya 
To: dev 
Date:   09/17/2015 21:50
Subject:Re: Failed to build Mesos module



Hello Qian,

Please follow the instructions on https://github.com/mesos/modules to get
up and running with building a mesos module. Apparently, building mesos
modules requires you to build Mesos without bundled protobuf, glog and
boost libraries. Thus, you need to have them installed system wide. The
above repo has a readme and a few test modules that you can play with.

Please let us know if you need any more help.

Kapil

On Thu, Sep 17, 2015 at 9:20 AM, Qian AZ Zhang  wrote:

>
>
> Hi all,
>
> I am trying to follow the doc (
>
>
https://github.com/apache/mesos/blob/master/docs/modules.md#writing-mesos-modules

> ) to implement a test module, but when I built the module, I got the
> following error:
> user1@test1:~/mesos/src/examples$ g++ -lmesos -fpic -o test_module.o
> test_module.cpp
> In file included from /usr/local/include/mesos/mesos.hpp:22:0,
>  from test_module.hpp:22,
>  from test_module.cpp:2:
> /usr/local/include/mesos/mesos.pb.h:9:42: fatal error:
> google/protobuf/stubs/common.h: No such file or directory
>  #include 
> ^
> compilation terminated.
>
> It seems it can not find the header file: google/protobuf/stubs/common.h.
I
> see this header file is in the Mesos source code tree, but not in
> /usr/local/include/mesos ( I have done "make install" after building
Mesos
> source code).
>
> Any help will be appreciated, thanks!
>
>
> Regards,
> Qian Zhang

Re: Failed to build Mesos module

2015-09-17 Thread Kamil Chmielewski 
Hi,

we had problems with building it recently.
See https://github.com/mesos/modules/pull/4

Regards,
Kamil

2015-09-17 15:49 GMT+02:00 Kapil Arya :

> Hello Qian,
>
> Please follow the instructions on https://github.com/mesos/modules to get
> up and running with building a mesos module. Apparently, building mesos
> modules requires you to build Mesos without bundled protobuf, glog and
> boost libraries. Thus, you need to have them installed system wide. The
> above repo has a readme and a few test modules that you can play with.
>
> Please let us know if you need any more help.
>
> Kapil
>
> On Thu, Sep 17, 2015 at 9:20 AM, Qian AZ Zhang 
> wrote:
>
> >
> >
> > Hi all,
> >
> > I am trying to follow the doc (
> >
> >
> https://github.com/apache/mesos/blob/master/docs/modules.md#writing-mesos-modules
> > ) to implement a test module, but when I built the module, I got the
> > following error:
> > user1@test1:~/mesos/src/examples$ g++ -lmesos -fpic -o test_module.o
> > test_module.cpp
> > In file included from /usr/local/include/mesos/mesos.hpp:22:0,
> >  from test_module.hpp:22,
> >  from test_module.cpp:2:
> > /usr/local/include/mesos/mesos.pb.h:9:42: fatal error:
> > google/protobuf/stubs/common.h: No such file or directory
> >  #include 
> > ^
> > compilation terminated.
> >
> > It seems it can not find the header file:
> google/protobuf/stubs/common.h. I
> > see this header file is in the Mesos source code tree, but not in
> > /usr/local/include/mesos ( I have done "make install" after building
> Mesos
> > source code).
> >
> > Any help will be appreciated, thanks!
> >
> >
> > Regards,
> > Qian Zhang
>

Re: Failed to build Mesos module

2015-09-17 Thread Kapil Arya 
Hello Qian,

Please follow the instructions on https://github.com/mesos/modules to get
up and running with building a mesos module. Apparently, building mesos
modules requires you to build Mesos without bundled protobuf, glog and
boost libraries. Thus, you need to have them installed system wide. The
above repo has a readme and a few test modules that you can play with.

Please let us know if you need any more help.

Kapil

On Thu, Sep 17, 2015 at 9:20 AM, Qian AZ Zhang  wrote:

>
>
> Hi all,
>
> I am trying to follow the doc (
>
> https://github.com/apache/mesos/blob/master/docs/modules.md#writing-mesos-modules
> ) to implement a test module, but when I built the module, I got the
> following error:
> user1@test1:~/mesos/src/examples$ g++ -lmesos -fpic -o test_module.o
> test_module.cpp
> In file included from /usr/local/include/mesos/mesos.hpp:22:0,
>  from test_module.hpp:22,
>  from test_module.cpp:2:
> /usr/local/include/mesos/mesos.pb.h:9:42: fatal error:
> google/protobuf/stubs/common.h: No such file or directory
>  #include 
> ^
> compilation terminated.
>
> It seems it can not find the header file: google/protobuf/stubs/common.h. I
> see this header file is in the Mesos source code tree, but not in
> /usr/local/include/mesos ( I have done "make install" after building Mesos
> source code).
>
> Any help will be appreciated, thanks!
>
>
> Regards,
> Qian Zhang

Failed to build Mesos module

2015-09-17 Thread Qian AZ Zhang 


Hi all,

I am trying to follow the doc (
https://github.com/apache/mesos/blob/master/docs/modules.md#writing-mesos-modules
) to implement a test module, but when I built the module, I got the
following error:
user1@test1:~/mesos/src/examples$ g++ -lmesos -fpic -o test_module.o
test_module.cpp
In file included from /usr/local/include/mesos/mesos.hpp:22:0,
 from test_module.hpp:22,
 from test_module.cpp:2:
/usr/local/include/mesos/mesos.pb.h:9:42: fatal error:
google/protobuf/stubs/common.h: No such file or directory
 #include 
^
compilation terminated.

It seems it can not find the header file: google/protobuf/stubs/common.h. I
see this header file is in the Mesos source code tree, but not in
/usr/local/include/mesos ( I have done "make install" after building Mesos
source code).

Any help will be appreciated, thanks!


Regards,
Qian Zhang

FYI: MesosCon Europe 2015 Schedule & Diversity Scholarship now available

2015-09-17 Thread Michael Hausenblas 
Details see:

http://mesos.apache.org/blog/mesoscon-europe-2015-schedule-announced/

We'd love to see as many as possible of you in Dublin!

Cheers,
Michael

--
Michael Hausenblas
Ireland, Europe
http://mhausenblas.info/