mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tomas Barton <>
Subject DC/OS (Mesos) portability
Date Fri, 03 Nov 2017 15:23:11 GMT

I'd like to contribute to DC/OS with a Debian/Suse/... support.
Surprisingly on Debian most of the compatibility issues could be solved by
a sequence of symlinks.

Why Mesos dev list? :)

Currently the biggest issue is connected to distributing libmesos-bundle
tar archive, which contain the library and several others. The
library is dynamically linked with certain libcurl,  libssl, libsvn etc.
that might differ between distributions.

I can think of a few solutions:
 1. Compile Mesos (master and agent) using static build (which as I
understood aren't currently fully supported/propagated).
 2. Generate bundle during automatic builds for certain supported
 3. Include libmesos in standard distribution channels - rpm, deb packages
(that might take same time).

The last solution would be the best, but Mesos release cycle is very
different from distributions release cycle. It might be complicated to

I coudn't find scripts for generating libmesos-bundle, but it's a archive
with libraries from build server, e.g.

So the question is, whether Mesos website could provide prebuild libmesos
bundle for each release and platform, that could be afterwards used e.g. in
DC/OS packages?

Last issue might be connected to an executor that eventually might need OS
family ENV variable with OS release version, so that it can fetch
corresponding libbundle archive. Such information is typically parsed from
`uname -a` or `lsb_release -sri` (if available). This way DC/OS could be
running on a cluster with diverse OS versions/distributions.

Thanks for your time! I'd like to hear your opinion.

Tomas Barton

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message