|
|
|
|
|
|
by jetblackio
4096 days ago
|
|
|
Forgive me, but I'm not very familiar with the rapidly growing container-based ecosystems market, but how do all these pieces fit together? Namely: * Mesos / Yarn * Marathon * Kubernetes * OpenShift * Chronos There are others I'm sure that I just don't recall. Also, how does the container approach fit in the traditional VM models of OpenStack / AWS / Digital Ocean. Are these systems aiming to ultimately replace them? Do they solve the problems of networking and disk? Maybe it's time I spent an afternoon looking into all this. |
|
|
Mesos is a general purpose framework for task scheduling into a set of machines. Mesos uses a concept of 'offers' where custom frameworks can choose to use or not use them. Yarn is similar, but it's a bit incestual with the rest of the Hadoop ecosystem and is designed to run distributed MRv2 jobs. Mesos isn't related to Hadoop other than it's use of Zookeeper for leader election & state.
Mesos itself doesn't do much without a framework.
> Marathon
Marathon is a framework for Mesos that runs long-lived tasks and supports interesting things like artifact staging, dependencies.
> Kubernetes
Not really sure how Kubernetes differentiates itself from Mesos (besides having Google as a sponsor). I haven't used it myself.
> OpenShift
A PaaS from Red Hat that uses it's own scheduling and distribution mechanisms to run applications built (very Similar to Heroku/Elastic Beanstalk)
> Chronos
Similar to Marathon, except that it runs an essentially distributed cron (and has dependencies, etc). You can use Chronos as a full-fledged distributed job running system. Chronos isn't intended to run long-running tasks.