An Overview of Mesos Containerization and the Default Executor
Channel: The Linux Foundation
Date: 21/09/2017

An Overview of Mesos Containerization and the Default Executor - Gilbert Song & Anand Mazumdar, Mesosphere

Mesos, different from some other container orchestrators, has its own native container runtime. Based on the pure Linux Kernel namespaces and cgroups, Mesos supports different container image formats with advantages of extensible container storage, networking, and security.

As of today it support all major container image formats such as OCI or Docker Image format, as well as default storage and networking plugins formats with CSI and CNI.

Historically, Mesos has provided a command executor for running one off tasks by schedulers e.g., Marathon. For launching a group of co-located tasks, the recommended way was to implement the logic using a custom executor. With the support for task groups aka Pods in Mesos, the default executor is the new recommended way for running pods in production. Moreover, based on nested containers, debug containers become realistic to enter any containers namespaces.

In this talk you will learn the following:

- Overview of the Mesos Agent API’s for nested containers used by the default executor

- Best practices for running sidecar/adapter containers and transient tasks

- Health Checks and Probes (Non-interpreted health checks)

- Default Termination Policy for the default executor

- New planned upcoming features on the roadmap

About

Anand Mazumdar
Mesosphere
Distributed Systems Engineer
Anand Mazumdar is an Engineer at Mesosphere and a committer on the Apache Mesos project. Prior to that, he used to work at a Quantitative Hedge Fund and Amazon Web Services on scalable data stream processing. He holds a Masters in Computer Science from The University of Texas at Austin. On weekends, you can find him playing Poker at a nearby local casino.


Gilbert Song
Mesosphere
Distributed Systems Engineer
Gilbert Song, Apache Mesos PMC/Committer, is a Distributed Systems Engineer at Mesosphere. He has been contributing to Mesos for years and mainly focuses on Mesos Containerization. He holds a Master’s degree in Computer Engineering from University of California, Santa Barbara. He is passionate about highly available and scalable distributed systems.