[Aug 6] Debian Stretch Minimal 64bit (0.7.8) / Ubuntu 18.04 Bionic LXDE Desktop Image (0.7.8) / Ubuntu 18.04 Bionic minimal 64bit / 32bit Image (0.7.8) / Ubuntu 18.04 Bionic Containers Image (0.7.8) / Stretch OpenMediaVault OS Image armhf / Stretch OpenMediaVault OS Image arm64 ( 0.7.8) - ROCK64 | [June 25] Stock Android 8.1 - ROCK64 | [June 19] Armbian (5.42) - ROCK64 | [June 19] Armbian (5.38) - PINE A64(+) / PINE A64-LTS / SOPINE

Project Inspiration | Get Started | IRC Logs | Forum Rules/Policy


Mesos?
#1
Does anybody tried to create cluster of Pine64s on Mesos? Is it possible?
Reply
#2
(09-02-2016, 10:59 AM)kermitas Wrote: Does anybody tried to create cluster of Pine64s on Mesos? Is it possible?

Read from the wiki page, it seems possible but nobody has try out yet.
Reply
#3
I bought 3 Pine64 boards specifically to try that out. I have 2 of them up and running on Ubuntu 16.04 per longsleep's build. THat's the good news.

The bad news is that I cannot get mesos building. I keep gettign errors in building the 3rdparty google logging code.

UNAME_MACHINE = aarch64
UNAME_RELEASE = 3.10.102-0-pine64-longsleep
UNAME_SYSTEM  = Linux
UNAME_VERSION = #7 SMP PREEMPT Fri Jun 17 21:30:48 CEST 2016
configure: error: cannot guess build type; you must specify one
Makefile:1147: recipe for target 'glog-0.3.3-build-stamp' failed
make[3]: *** [glog-0.3.3-build-stamp] Error 1
make[3]: Leaving directory '/home/debian/mesos/build/3rdparty'
Makefile:832: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/debian/mesos/build/3rdparty'
Makefile:647: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/debian/mesos/build/3rdparty'
Makefile:762: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Any ideas? I am wondering if I cannot build glog on aarch64 or if make doesn't know the overall target.

I bought 3 Pine64 boards specifically to try that out. I have 2 of them up and running on Ubuntu 16.04 per longsleep's build. THat's the good news.

The bad news is that I cannot get mesos building. I keep gettign errors in building the 3rdparty google logging code.

UNAME_MACHINE = aarch64
UNAME_RELEASE = 3.10.102-0-pine64-longsleep
UNAME_SYSTEM  = Linux
UNAME_VERSION = #7 SMP PREEMPT Fri Jun 17 21:30:48 CEST 2016
configure: error: cannot guess build type; you must specify one
Makefile:1147: recipe for target 'glog-0.3.3-build-stamp' failed
make[3]: *** [glog-0.3.3-build-stamp] Error 1
make[3]: Leaving directory '/home/debian/mesos/build/3rdparty'
Makefile:832: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/debian/mesos/build/3rdparty'
Makefile:647: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/debian/mesos/build/3rdparty'
Makefile:762: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Any ideas? I am wondering if I cannot build glog on aarch64 or if make doesn't know the overall target.
Reply
#4
I doubt it will be smooth at the moment.

https://issues.apache.org/jira/browse/ME...ext%20~%20"arm64"

lists few open bugs.

Even updating dependencies and fixing some minor issues, the compiled binaries segfault right now.


the glog issue might be some issue with go language / compiler.

Maybe you could try doing this again with Debian sid/unstable version instead?
Reply
#5
(01-02-2017, 04:42 PM)baryluk Wrote: I doubt it will be smooth at the moment.

https://issues.apache.org/jira/browse/ME...ext%20~%20"arm64"

lists few open bugs.

Even updating dependencies and fixing some minor issues, the compiled binaries segfault right now.


the glog issue might be some issue with go language / compiler.

Maybe you could try doing this again with Debian sid/unstable version instead?

Thanks. I'll give it a try and let you know.
Reply
#6
(09-02-2016, 10:59 AM)kermitas Wrote: Does anybody tried to create cluster of Pine64s on Mesos? Is it possible?

sure, it been done for awhile, assume you inderstand how docker works:

https://hub.docker.com/r/mdef/mesos-arm64/
you need to pull image and than run container.
mesos-agent inside image compiled for arm64.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)