MesosCon Europe 2017

While Mesos itself is highly fault tolerant, the apps running on top of it traditionally had to depend on non-standard mechanisms (e.g., agent attributes) to make them highly available. This changes with the introduction of native support for fault domains in Mesos 1.4! Fault domains, as a first class primitive, allows Mesos frameworks to speak a common language when it comes to their desire to launch fault tolerant applications.

This talk will give an overview of the feature and also discusses a few of the use cases this feature unlocks for a lot of organizations. Specifically we will discuss workload bursting from on-prem to public cloud instances and doing rack aware scheduling for stateful applications.

Without first class support for secrets (Credentials, API keys etc), application and framework developers had to traditionally resort to out-of-band mechanisms to transmit and use secrets in Mesos. This is changing now!

In this talk, we will describe the newly-added native support for secrets in Mesos. The Secrets API will let Mesos inject sensitive information into either the container environment or sandbox without exposing it to unauthorized actors. The advantage of this approach is that users do not need to explicitly store sensitive information in their task configuration but can let Mesos retrieve it from a secret store at container launch time. This is possible via the new “Secrets Resolver” module interface which allows operators to integrate Mesos with 3rd party secret stores (e.g., HashiCorp’s Vault).

We will show a cool demo at the end that shows secrets in action.

Apache Mesos and DC/OS allows users to deploy distributed applications and in particular micro-services across a large cluster. Therefore, networking becomes an important aspect especially when trying to provide highly-available applications on top of an unreliable infrastructure.
In this talk, we will first present the various challenges around networking for distributed micro-service architectures, including
* Connectivity
* Service Discovery
* Load-balancing
* Isolation

As for most of the above challenges there is not a one-size-fits-all solution we have an in-depth look at the trade-offs between different solutions.
Afterwards, we will deep dive into the actual implementation of the different components in order to understand how we can achieve a scalable networki

Containers are now everywhere. Apache Mesos, as one of the most powerful container orchestrators, greatly simplifies the deploy, provision, and execution of containerized workloads. In this talk, Jie will talk about the evolution of container technology in Mesos. In particular, how Mesos embraces the industry standard for container networking, storage and image specification, and how Mesos achieves that by using a pluggable and extensible architecture. The first part of this talk will give you an overview of the container technology in Mesos and how it has evolved over the years. Then, we will dive into three specific areas in the container technology: networking, storage and image provisioning, and the three industry standards that Mesos is adopting: CNI (Container Network Interface), CSI (Container Storage Interface) and OCI (Open Container Initiative) image spec.

Over the past 2 years there has been a huge shift involving stateful applications becoming a mainstream feature used by most container users. This has been observed by storage vendors, the Mesos project, and on other container orchestrator platforms. The Container Storage Interface (CSI) is modeled on the successful CNCF sponsored OCI and CNI interoperability initiatives in the container and network space respectively. Its goal is to provide a vendor neutral, curated specification that allows standardized storage plugins to be published and utilized across multiple container orchestrators, including Mesos.

This session will cover the architecture of the CSI. Multiple speakers will address the benefits a standardized storage interface can offer to users, from the perspective of both a container orchestrator and from a storage provider that wishes to support multiple platforms.