Multi Cloud Mesos
summary
Adobe runs DC/OS/Mesos across AWS, Azure and private datacenters using an input-file -> infrastructure -> cluster-data pipeline: troposphere → CloudFormation for AWS, Azure Container Service Engine → ARM for Azure, and RackHD for bare metal in the data center, with outputs committed to Git. CoreOS nodes boot via cloud-config/ignition, self-register with Marathon, and operators use a cattle model (drain and replace) for day‑two ops. A one‑click DC/OS deploy to each cloud is demonstrated and a Multicloud Transport (MCT) underlay provides private cross‑cloud networking.
AI-written summary · about
chapters (9)
- 0:00Introduction and objective
- 2:37Defining the core problem
- 5:08DCOS and container adoption
- 9:14The multicloud strategy
- 14:05Designing the multicloud stack
- 20:46Tooling and implementation
- 28:17Operational day two
- 32:08Data center modernization
- 39:39Demo and conclusion
related talks
22mKeynote: The Future of Apache Mesos and DC/OS
43mGetting to a Multi-Cloud Deployment - A Case Study of
23mHow cluster managers affect the landscape of modern distributed computing
42mDC/OS — more than PaaS
34mApache Mesos For All Your Hybrid Cloud Needs
40mPanel Discussion: Going Multi-Cloud for Realz. Stories From Media, Retail, & Infrastructure
38mOS-Climate & SIG-SRE: Benefiting from the Operate First Community Cloud
19mKeynote: Operating 600+ Mesos Servers on 7 Datacenters @Criteo