Conference: Nov 13-15, 2017
Workshops: Nov 16-17, 2017
Presentation: Mesos: A State-Of-The-Art Container Orchestrator
Duration
Level:
- Intermediate
Persona:
- Architect
- Developer
- DevOps Engineer
Key Takeaways
- Hear lessons learned building and deploying container technology from a Mesos engineer.
- Gain better knowledge about different container technologies that are available, such as Docker, Mesos, and Rocket.
- Learn what’s gone into the Mesos container story as it’s evolved to 1.0.
Abstract
Mesos, as one of the most powerful container orchestrators, greatly simplifies the deploy, provision and execution of containerized workloads. It automates the distribution of preprovisioned container images, injection of configuration, scheduling onto machines, life-cycle-management, and monitoring of applications, microservices, and jobs in the cloud.
In this talk, Jie Yu will first give you an overview about Mesos and its powerful API which allows users to easily deploy their stateless and stateful services. Then, Jie will talk about how containers are managed in Mesos. In particular, Jie will provide a deep dive into the unified containerizer which is first introduced in Mesos 1.0.
Jie will show some of the new container networking and storage features that are built recently, and how they benefit from the pluggable and extensible architecture of the unified containerizer. Finally, Jie will discuss the future of container support in Mesos.
Interview
Jie: I currently work at Mesosphere, and my current role is tech lead at the container team. Basically, I work on everything related to containerization, and I lead the projects under that team.
Jie: Mesos has its own containerization engine (it came before Docker). I previously worked at Twitter who's been using Mesos for quite a while. It’s pretty reliable. The thing I’ve been working on is trying to improve the container engine, so it can launch Docker containers or maybe OCI containers (in the future). We are not trying to touch the tools you can use for development from Docker, but, after you push to the registry, we trying to make it where Mesos can take care of everything. So you don’t have to rely on the Docker Daemon. All this has been releasing with Mesos 1.0 and the main thing I’ve been working on.
Jie: Mesos agent is what’s deployed to every host, but it’s not really a Daemon. If you can kill a Daemon, every task goes away. Mesos can kill the agent at any time, and it will recover everything correctly. If you want to store some data, we always checkpoint to the disk (so it can recover). Our whole architecture is designed in such a way that it can survive crash elegantly.
I think that’s the main difference. I think when Docker designed Docker Daemon they didn’t design it in such a way that the assumed Daemon can crash at any time.
Jie: I think they will have a better idea about different kinds of container technology (like Docker, Mesos, or Rocket), and have a clearer idea of what the pros and the cons of each of those technologies are. Hopefully, they will want to choose Mesos, and will understand the advantage of the Mesos container runtime.
Jie: I’m going to cover the container side of the story for Mesos 1.0. He did a bunch of work to the containers runtime in 1.0. There are things in there like container network and container storage. The whole thing about the mesos containerization runtime is it’s so pluggable you can do anything you want.
Jie: I think 1.0 is mainly about the API. Mesos has been in production for several years. People know that it's running in Twitter in production. They know it can handle 30,000 machines in a single cluster. So it’s pretty stable. We could have called it 1.0 a long time ago, but we decided not to because we didn’t have a coherent story for api. Now we do. So I think 1.0 is mainly about API for the framework providers.
Similar Talks
.
Tracks
Monday Nov 7
-
Architectures You've Always Wondered About
You know the names. Now learn lessons from their architectures
-
Distributed Systems War Stories
“A distributed system is one in which the failure of a computer you didn't even know existed can render your own computer unusable.” - Lamport.
-
Containers Everywhere
State of the art in Container deployment, management, scheduling
-
Art of Relevancy and Recommendations
Lessons on the adoption of practical, real-world machine learning practices. AI & Deep learning explored.
-
Next Generation Web Standards, Frameworks, and Techniques
JavaScript, HTML5, WASM, and more... innovations targetting the browser
-
Optimize You
Keeping life in balance is a challenge. Learn lifehacks, tips, & techniques for success.
Tuesday Nov 8
-
Next Generation Microservices
What will microservices look like in 3 years? What if we could start over?
-
Java: Are You Ready for This?
Real world lessons & prepping for JDK9. Reactive code in Java today, Performance/Optimization, Where Unsafe is heading, & JVM compile interface.
-
Big Data Meets the Cloud
Overviews and lessons learned from companies that have implemented their Big Data use-cases in the Cloud
-
Evolving DevOps
Lessons/stories on optimizing the deployment pipeline
-
Software Engineering Softskills
Great engineers do more than code. Learn their secrets and level up.
-
Modern CS in the Real World
Applied, practical, & real-world dive into industry adoption of modern CS ideas
Wednesday Nov 9
-
Architecting for Failure
Your system will fail. Take control before it takes you with it.
-
Stream Processing
Stream Processing, Near-Real Time Processing
-
Bare Metal Performance
Native languages, kernel bypass, tooling - make the most of your hardware
-
Culture as a Differentiator
The why and how for building successful engineering cultures
-
//TODO: Security <-- fix this
Building security from the start. Stories, lessons, and innovations advancing the field of software security.
-
UX Reimagined
Bots, virtual reality, voice, and new thought processes around design. The track explores the current art of the possible in UX and lessons from early adoption.
Conference for Professional Software Developers
