Re: Failed to build Mesos module

[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
>
>

need help/shepherd on MESOS-1806

[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

[VOTE] Release Apache Mesos 0.24.1 (rc1)

[Adam Bordelon]

Hi friends,

Please vote on releasing the following candidate as Apache Mesos 0.24.1.

0.24.1 includes the following:

* [MESOS-2986] - Docker version output is not compatible with Mesos
* [MESOS-3136] - COMMAND health checks with Marathon 0.10.0 are broken

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.1-rc1


The candidate for Mesos 0.24.1 release is available at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.1-rc1/mesos-0.24.1.tar.gz

The tag to be voted on is 0.24.1-rc1:
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=0.24.1-rc1

The MD5 checksum of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.1-rc1/mesos-0.24.1.tar.gz.md5

The signature of the tarball can be found at:
https://dist.apache.org/repos/dist/dev/mesos/0.24.1-rc1/mesos-0.24.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-1068

Please vote on releasing this package as Apache Mesos 0.24.1!

The vote is open until Wed Sep 23 18:00 PDT 2015 and passes if a majority
of at least 3 +1 PMC votes are cast.

[ ] +1 I tested this package. Release it as Apache Mesos 0.24.1
[ ] -1 Do not release this package because ...

Thanks,
-Adam-

Re: Working Group List

[Vinod Kone]

+1

On Fri, Sep 18, 2015 at 10:55 AM, Niklas Nielsen 
wrote:

> Hi folks,
>
> Per our last community meeting, I created a list on our Confluence Wiki to
> keep track of and increase visibility into the running working groups.
> We have previously created these groups implicitly, and as the community
> grow, we unfortunately ended up with duplicate meetings with different
> stake holders in the case of Networking and folks have been missing out on
> other meetings too.
>
> So, here it is:
>
> https://cwiki.apache.org/confluence/display/MESOS/Apache+Mesos+Working+Groups
>
> I imagined that we could create IRC channels, hangouts etc and note the
> channels there.
>
> Of course, the main activity should be on the dev@ list but we have
> traditionally met up (online or IRL) for design sessions, higher frequency
> feedback during reviews, etc.
>
> Thoughts / ideas?
>
> Cheers,
> Niklas
>

need help/shepherd on MESOS-3435

[tommy xiao]

I plan to add Hyper support on Marathon. So i proposal this request on
Marathon, https://github.com/mesosphere/marathon/issues/1815
but in discussion and tim mentioned, i first need familiar with mesos
docker implement.
I want to know which way is best:
does it good start:
/src/slave/containerizer/docker.hpp
if i can as this file as reference to add hyper.hpp, right?



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

Re: need help/shepherd on MESOS-3435

[Timothy Chen]

I think it helps to write a design doc first, as I'm not familiar with hyper 
and basically how it works and how it maps to the containerizer API.

 But yes docker.cpp can be a reference how to integrate another containerizer, 
and it's not the only way which depends on the containerizer.

Tim

> On Sep 18, 2015, at 4:34 AM, tommy xiao  wrote:
> 
> I plan to add Hyper support on Marathon. So i proposal this request on
> Marathon, https://github.com/mesosphere/marathon/issues/1815
> but in discussion and tim mentioned, i first need familiar with mesos
> docker implement.
> I want to know which way is best:
> does it good start:
> /src/slave/containerizer/docker.hpp
> if i can as this file as reference to add hyper.hpp, right?
> 
> 
> 
> -- 
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com

Working Group List

[Niklas Nielsen]

Hi folks,

Per our last community meeting, I created a list on our Confluence Wiki to
keep track of and increase visibility into the running working groups.
We have previously created these groups implicitly, and as the community
grow, we unfortunately ended up with duplicate meetings with different
stake holders in the case of Networking and folks have been missing out on
other meetings too.

So, here it is:
https://cwiki.apache.org/confluence/display/MESOS/Apache+Mesos+Working+Groups

I imagined that we could create IRC channels, hangouts etc and note the
channels there.

Of course, the main activity should be on the dev@ list but we have
traditionally met up (online or IRL) for design sessions, higher frequency
feedback during reviews, etc.

Thoughts / ideas?

Cheers,
Niklas