blocks|key|4561803|text|Mesos和Kubernetes都可以用来管理机器集群和抽象硬件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4561804|Mesos在设计上并没有为您提供调度器(用于决定何时何地运行进程以及在进程失败时如何处理)，您可以使用Marathon或Chronos之类的工具，或者编写自己的调度器。|4561805|Kubernetes将为您进行开箱即用的调度，并且可以用作Mesos的调度器(如果我错了，请纠正我！)这是你可以一起使用它们的地方。Mesos可以有多个调度器共享同一个集群，因此理论上您可以在相同的硬件上一起运行kubernetes和chronos。|4561806|非常简单:如果你想控制如何调度你的容器，去Mesos，否则Kubernetes摇滚。|4561807|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Mesos and Kubernetes can both be used to manage a cluster of machines and abstract away the hardware.

Mesos, by design, doesn't provide you with a scheduler (to decide where and when to run processes and what to do if the process fails), you can use something like Marathon or Chronos, or write your own.

Kubernetes will do scheduling for you out of the box, and can be used as a scheduler for Mesos (please correct me if I'm wrong here!) which is where you can use them together. Mesos can have multiple schedulers sharing the same cluster, so in theory you could run kubernetes and chronos together on the same hardware.

Super simplistically: if you want control over how your containers are scheduled, go for Mesos, otherwise Kubernetes rocks.

blocks|key|4561827|text|这两个项目都旨在使在数据中心或云中的容器内部署和管理应用程序变得更容易。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4561828|为了在Mesos之上部署应用程序，可以使用Marathon或Kubernetes+for+Mesos。|4561829|Marathon是一个集群范围的初始化和控制系统，用于在cgroup和Docker容器中运行Linux服务。Marathon有许多不同的canary+deploy特性，是一个非常成熟的项目。|4561830|Marathon运行在Mesos之上，Mesos是一个高度可伸缩的、经过战斗考验的灵活资源管理器。事实证明，Marathon具有可伸缩性，并可在许多生产环境中运行。|4561831|Mesos和Mesosphere技术堆栈为运行现有Linux工作负载提供了一个类似云的环境，但它也为构建新的分布式系统提供了一个本机环境。|4561832|Mesos是一个分布式系统内核，具有完整的API，可直接针对数据中心进行编程。它将底层硬件(例如裸机或虚拟机)抽象化，只公开资源。它包含用于编写分布式应用程序的原语(例如，Spark最初是Mesos应用程序、Chronos等)例如消息传递、任务执行等。因此，完全新的应用程序成为可能。Apache+Spark是一个新的(在Mesos术语中称为)框架的例子，该框架最初是为Mesos构建的。这使得开发速度非常快-+Spark的开发人员不必担心网络在节点之间分发任务，因为这是Mesos中的核心原语。|4561833|据我所知，目前在Google的生产部署中还没有使用Kubernetes。对于生产，Google使用Omega/Borg，它更类似于Mesos/Marathon模型。然而，使用Mesos作为基础的伟大之处在于Kubernetes和Marathon都可以在其上运行。|4561834|更多关于马拉松的资源：|4561835|https://mesosphere.github.io/marathon/|offset|length|4561836|视频：https://www.youtube.com/watch?v=hZNGST2vIds|4561837|entityMap|0|LINK|mutability|MUTABLE|url|1|https://www.youtube.com/watch?v=hZNGST2vIds^0|0|0|0|0|0|0|0|0|0|12|0|0|3|17|1|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|15|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|16|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|17|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|18|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|19|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1A|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1B|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1C|8|@]|9|@$R|1D|S|1E|1|1F]]|A|$]]|$1|T|3|U|5|6|7|1G|8|@]|9|@$R|1H|S|1I|1|1J]]|A|$]]|$1|V|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|Q]]|12|$5|Y|Z|10|A|$11|13]]]]

Both projects aim to make it easier to deploy &amp; manage applications inside containers in your datacenter or cloud.

In order to deploy applications on top of Mesos, one can use Marathon or Kubernetes for Mesos.

Marathon is a cluster-wide init and control system for running Linux services in cgroups and Docker containers. Marathon has a number of different canary deploy features and is a very mature project.

Marathon runs on top of Mesos, which is a highly scalable, battle tested and flexible resource manager. Marathon is proven to scale and runs in many production environments. 

The Mesos and Mesosphere technology stack provides a cloud-like environment for running existing Linux workloads, but it also provides a native environment for building new distributed systems.

Mesos is a distributed systems kernel, with a full API for programming directly against the datacenter. It abstracts underlying hardware (e.g. bare metal or VMs) away and just exposes the resources. It contains primitives for writing distributed applications (e.g. Spark was originally a Mesos App, Chronos, etc.) such as Message Passing, Task Execution, etc. Thus, entirely new applications are made possible. Apache Spark is one example for a new (in Mesos jargon called) framework that was built originally for Mesos. This enabled really fast development - the developers of Spark didn't have to worry about networking to distribute tasks amongst nodes as this is a core primitive in Mesos.

To my knowledge, Kubernetes is not used inside Google in production deployments today. For production, Google uses Omega/Borg, which is much more similar to the Mesos/Marathon model. However the great thing about using Mesos as the foundation is that both Kubernetes and Marathon can run on top of it.

More resources about Marathon:

<a href="https://mesosphere.github.io/marathon/" rel="noreferrer">https://mesosphere.github.io/marathon/</a>

Video:
<a href="https://www.youtube.com/watch?v=hZNGST2vIds" rel="noreferrer">https://www.youtube.com/watch?v=hZNGST2vIds</a>

blocks|key|55296|text|我喜欢这里的这个短视频mesos+learning+material|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|55297|使用裸机集群时，您需要生成HDFS、SPARK、MR等堆栈。因此，如果您仅使用裸机集群管理启动与这些任务相关的任务，将会有大量的冷启动时间。|55298|使用mesos，您可以在裸机上安装这些服务，并且可以避免这些基础服务的启动时间。这是mesos做得很好的事情。并且可以被建立在它上面的kubernetes使用。|55299|entityMap|0|LINK|mutability|MUTABLE|url|https://mesosphere.com/learn/^0|B|N|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

I like this short video here <a href="https://mesosphere.com/learn/" rel="noreferrer">mesos learning material</a>

with bare metal clusters, you would need to spawn stacks like HDFS, SPARK, MR etc... so if you launch tasks related to these using only bare metal cluster management, there will be a lot cold starting time.

with mesos, you can install these services on top of the bare metals and you can avoid the bring up time of those base services. This is something mesos does well. and can be utilised by kubernetes building on top of it.

blocks|key|4561881|text|“我知道两者都是服务器群集管理软件。”|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4561882|这句话并不完全正确。Kubernetes不管理服务器集群，它编排容器，使它们以最小的麻烦和暴露协同工作。Kubernetes允许您将应用程序的部分定义为“pod”(一个或多个容器)，这些部分由“部署”或“守护程序集”(以及其他几个)提供，并通过服务公开给外部世界。然而，Kubernetes本身并不管理集群(有一些工具可以为您提供、配置和扩展集群，但这些工具不是Kubernetes本身的一部分)。|4561883|另一方面，Mesos更接近于“集群管理”，因为它可以控制什么在哪里运行，但不仅仅是在调度容器方面。Mesos还管理集群服务器上运行的独立软件。尽管Mesos主要用作Kubernetes的替代品，但它可以很容易地与Kubernetes一起使用，因为虽然在许多领域中功能重叠，Mesos可以做更多的事情(但在重叠的部分，Kubernetes往往更好)。|4561884|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

"I understand both are server cluster management software."

This statement isn't entirely true. Kubernetes doesn't manage server clusters, it orchestrates containers such that they work together with minimal hassle and exposure. Kubernetes allows you to define parts of your application as "pods" (one or more containers) that are delivered by "deployments" or "daemon sets" (and a few others) and exposed to the outside world via services.
However, Kubernetes doesn't manage the cluster itself (there are tools that can provision, configure and scale clusters for you, but those are not part of Kubernetes itself).

Mesos on the other hand comes closer to "cluster management" in that it can control what's running where, but not just in terms of scheduling containers. Mesos also manages standalone software running on the cluster servers. Even though it's mostly used as an alternative to Kubernetes, Mesos can easily work with Kubernetes as while the functionality overlaps in many areas, Mesos can do more (but on the overlapping parts Kubernetes tends to be better).

What exactly is the difference between Apache's Mesos and Google's Kubernetes?
I understand both are server cluster management software. Can anyone elaborate where the main differences are - when would which framework be preferred?

Why would you want to use <a href="http://googlecloudplatform.blogspot.ch/2014/08/mesosphere-collaborates-with-kubernetes-and-google-cloud-platform.html">Kubernetes on top of Mesosphere</a>?

What's the difference between Apache's Mesos and Google's Kubernetes

数据中心

Kubernetes

服务器

虚拟机

容器

Spark 

Linux

HDFS

Apache的Mesos和Google的Kubernetes到底有什么不同？我知道这两个都是服务器集群管理软件。谁能详细说明主要的区别在哪里--哪个框架是首选的？为什么要使用

问Apache的Mesos和Google的Kubernetes有什么不同
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Apache的Mesos和Google的Kubernetes有什么不同EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Apache的Mesos和Google的Kubernetes有什么不同
EN