How cluster managers affect the landscape of modern distributed computing
summary
Mesosphere open-sources DC/OS to stop teams from reinventing Mesos orchestration; Mesos is framed as Mesos as cluster kernel that aggregates CPUs/memory into a single computer and exposes small primitives. Claim: code reuse and modularity reduce ops headcount — Autodesk runs multiple small clusters across regions with one engineer managing them for a year. Predictions: container isolation improves vs VMs within ~2 years, smarter isolation (Google-style CPI2 heuristics) appears, and modules are pluggable but not hot-loaded today.
AI-written summary · about
chapters (19)
- 0:00Cluster managers introduction
- 1:30Containers as packaging
- 4:00Manual task mapping impractical
- 4:43Mesos as single-computer abstraction
- 5:26Mesos vs DC/OS differences
- 6:28Why DC/OS was open-sourced
- 7:50DC/OS reducing DevOps workload
- 8:55Autodesk’s DC/OS success
- 9:39Container security challenges
- 10:48Smarter isolation and multi-tenancy
- 11:55Cluster manager competition
- 12:38Growing open-source communities
- 13:41Community contributions
- 14:48Simplifying data center architecture
- 16:18Smartphones as compute nodes
- 17:04DevOps priorities and utilization
- 18:09Mesos and DC/OS FAQ
- 20:47Q&A on HTC and runtime
- 23:01Closing remarks
related talks
22mKeynote: The Future of Apache Mesos and DC/OS
27mKeynote Panel: Future of Cluster Management
42mDC/OS — more than PaaS
59mBuilding Distributed Systems with Apache Mesos
44mMulti Cloud Mesos
31mKubernetes on Top of Mesos on Top of DCOS
52mNightmares of a Container Orchestration System
38mMesomatic: The Cluster is a Library