Skip to main content

Mesos, Marathon and Mesosphere

Everything is turning up Docker these days and as such there are a number of new orchestration and scheduling systems for Docker that are popping up. Three projects that seem to be connected are Mesos, Marathon and Mesosphere. I'm sure they are interesting projects by in my "Level-A" stack they do not measure up.

Mesos

  • Mess requires the JDK and as such will not install on CoreOS as nicely as one would like. Self installer or not, CoreOS is meant to be immutable and so this is not an idiomatic idea.
  • The getting started documentation gives Ubuntu 12.04 examples and as of this writing Ubuntu is well into the 14.10 cycle with 15.04 just a few months away. They could have updated the doc. (not a good sign)
  • And without first hand knowledge other than reading the architecture documentation it appears that Mesos is something that looks like an analog of Docker in the JVM.
  • There is mention of some Hadoop Clustering and MPI. MPI is part of the cluster compute API framework and never makes it to Docker first class.
  • This link does talk about Docker and Mesos, however, it seems to be a me too.
Marathon
  • Just looking at the requirements and I feel justified.
  • Requires the JDK
  • Requires Mesos and so by extension it a bust
  • While scala is now a professional and fully realized language it is still built on the JDK and I have yet to hear that they have completed a SDK replacement and therefore still suffers from all the problems of Java.
  • ZooKeeper calls itself a coordination server. (Doozer is a highly-available, completely consistent store for small amounts of extremely important data.; and etcd is an open-source distributed key value store)
Mesosphere
  • Requires Mesos and Marathon... meaning it also requires the JDK
  • Looks like it will run on CoreOS, however, that seems to conflict with the JDK requirement.
  • It also requires ZooKeeper even though CoreOS includes etcd.
Without going off the deepen here... Even if this tool stack is awesome it still a pig. The configuration is deep and has lots of moving parts. Getting to any level of excellence is going to be a serious challenge. This has go to be the worst of all of the similar systems in the same space. And having speed-read through the documentation I cannot find a single killer feature worth investing in and I've already had success with many of the others.

Comments

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…