« Previous 1 2
Mesos compute cluster for data centers
Distributed!
Was That All Folks?
Late in 2014, Mesosphere announced the Datacenter Operating System (DCOS) [18]. Mesophere describes DCOS as a "new kind of operating system that spans all of the servers in a physical or cloud-based data center and runs on top of any Linux distribution." Mesos assumes the system kernel role at the base of the DCOS system.
The Marathon [19] and Chronos [20] frameworks will also be part of the package. Marathon manages jobs with a longer execution time. If you compare DCOS with a classical Unix-style operating system, Marathon is equivalent to the init process. You can also view Marathon as a meta-scheduler. Marathon starts the other frameworks and monitors them. In doing so, Marathon checks whether the desired number of job instances are running. If a slave fails, Marathon starts the failed processes on the remaining Mesos nodes.
Chronos, which runs jobs in line with a defined schedule, is the equivalent of cron. In DCOS, Chronos is the first framework started by Marathon. Both have a REST interface for interaction.
Figure 3 shows a highly simplified DIY version of DCOS. Marathon (Figure 4) and Chronos are registered as Mesos applications. The jobs are simple sleep
commands. The use of ZooKeeper is mandatory for DCOS. Both Marathon and Chronos require ZooKeeper.
When this issue went to press, the DCOS by Mesosphere was still in beta. You can visit the Mesosphere website [18] to download a pre-release version.
Conclusions of a Kind
Just a glance at the list of enterprises that have been using Mesos for years is more than enough to show that Mesos is an exciting project. The number of frameworks based on Mesos is also quite impressive. Mesos really comes into its own in large and heterogeneous IT landscapes. The Mesos framework offers a simple approach to pooling existing compute capacities and providing them either as a bulk package or bit by bit. This form of abstraction is also very attractive for smaller IT environments.
Infos
- Apache Mesos: http://mesos.apache.org
- Mesos at the Usenix Conference: http://www.usenix.org/conference/hotcloud-09/common-substrate-cluster-computing
- Mesos progress: http://people.csail.mit.edu/matei/papers/2011/nsdi_mesos.pdf
- Twitter uses Mesos: http://www.wired.com/2013/03/google-borg-twitter-mesos/all/
- Google's Omega: http://research.google.com/pubs/pub41684.html
- Getting started with Mesos: http://mesos.apache.org/documentation/latest/app-framework-development-guide/
- Mesos applications: http://mesosphere.com/docs/frameworks/
- Architecture: http://mesos.apache.org/documentation/latest/mesos-architecture/
- Configuration: http://mesos.apache.org/documentation/latest/configuration/
- Resources: http://mesos.apache.org/documentation/attributes-resources/
- Mesos in HA setups: http://mesos.apache.org/documentation/latest/high-availability/
- ZooKeeper: http://zookeeper.apache.org
- Leader election in ZooKeeper: http://zookeeper.apache.org/doc/trunk/recipes.html#sc_leaderElection
- SASL: http://tools.ietf.org/html/rfc4422
- Crammd5: http://tools.ietf.org/html/rfc2195
- Authorization: http://mesos.apache.org/documentation/latest/authorization/
- JSON: http://json.org
- Mesosphere: http://mesosphere.com
- Marathon: https://mesosphere.github.io/marathon/
- Chronos: https://github.com/mesos/chronos
« Previous 1 2
Buy this article as PDF
(incl. VAT)