Expanding Mesos Ecosystems: Enabling Mesos on Windows
summary
Mesos runs Windows agents against existing Linux masters, shipping a working CMake build that replaces autotools, adds Java bindings, Ninja support and precompiled headers, and cuts a cold Windows build from ~60 minutes to 18 minutes. The Windows containerizer uses job objects for limits and supports Docker containers; a prototype enforces a 1 GB hard memory cap. CI and a Windows review bot run daily, nightly binaries are available, about 630 tests currently cover Windows versus ~1,400 on Linux, and customers run this in production.
AI-written summary · about
chapters (13)
- 0:00Intro
- 1:10Why Add Windows Support?
- 2:05A Little Bit of History
- 4:46Hybrid DCIOS Cluster Deployment (3/3)
- 5:42Build System Improvements
- 10:47Why use CMake?
- 16:19Autotools versus CMake
- 18:21ReviewBot for Windows
- 19:15Continuous Integration for Windows
- 20:16A Case Study: Ctrip International
- 21:18Demonstration: Hybrid Cluster
- 24:33What's Next?
- 26:00Resources
related talks
22mEnsuring Platform Security with Windows Bosh Add-ons - Maris, Schaefbauer, Coppock, Boeing
55mMarathon and Jobs - Today and Tomorrow
50mJenkins in the Enterprise: Building Resilient CI Infrastructure
36mClosing the Developer Experience Gap of your Container Platforms
58m“Embracing Standard C++ for the Windows Runtime"
36mPractical Cloud Native: What Works, What Doesn't
19mBuilding Meta's Internal Cloud: the opportunities and challenges
24mThe Platform Wars, Begun They Have