Join us the day prior to the Keynotes and Breakout Sessions for a full day hackathon.
Day: Wednesday, September 13
Time: 10:00am-4:00pm
Location: Gold 2, JW Marriott LA Live
The focus of this hackathon, while not excluding other ideas, is improving Apache Mesos and it ecosystem.
There will be a number of experienced contributors and committers helping the participants to get started, give direct feedback and if possible even commit code.
Potential areas include:
All other proposals are welcome as well and will be discussed at the beginning of the hackathon.
Come hear how Apache Mesos is influencing the IT infrastructure at large enterprises, panelists include:
Michael Aguiling (CTO at JPMC)
Larry Rau (Director of Architecture at Verizon)
Cathy Daw (Director of Engineering at Mesosphere)
Stefan Bauer (Head of Development Data Analytics at Audi)
Hubert Fisher (Audi)
Moderated by Josh Bernstein (VP Technology at {code})
The SMACK stack is becoming the architecture for fast data processing and we’re bringing together some of the creators of the projects to talk about how SMACK is impacting the data analytics landscape.
Neha Narkhede (co-founder and CTO of Confluent)
Jonathan Ellis (co-founder and CTO of Datastax)
Benjamin Hindman (co-founder at Mesosphere)
We’ve assembled representatives from organizations operating some of the largest Mesos clusters we know to talk about where they think the future of cluster management is going. You’ll hear from:
Sharma Podila (Distributed Systems Software Architect at Netflix)
Sam Eaton (VP of Engineering, Operations, and Infrastructure at Yelp)
Ian Downes (Sr. Engineering Manager at Twitter)
Zhitao Li (Senior Software Engineer at Uber)
Moderated by Elizabeth Joseph (Open Source Developer Advocate at Mesosphere)
Orchestration of workloads is a hot topic. Everywhere we look there are opinions. All orchestration options claim to be the best, all options have their limitation. We listen to conference presentations that tell us how Company Foo has had amazing results with solution X and that they would never use solution Y, but the very next session tells us that equally impressive results have been achieved with solution Y and they'd never use X. What are we supposed to choose? Who are we supposed to listen to? In Azure Container Service we've been offering a choice of solutions to our customers for some time. What has this taught us about orchestration technology? What does the future look like? Who is the clear winner? [Spoiler alert: no clear winner but there are clear success stories for each offering.]
This talk will provide an overview of multi-tenancy in Apache Mesos, including recent work that was done to enable multi-tenant frameworks (with multi-role framework support and support for hierarchical roles). Topics include multi-tenant resource management, isolation, security, and other multi-tenancy concerns. This talk will also cover some upcoming work.
Most modern distributed applications like Cassandra and HDFS provide replication of data across nodes and failure zones to be able to deal with failures. But the time taken to recover to a pre-failure level of redundancy in cases of permanent node failures can be large, since a lot of data needs to be copied over to the new node. Also, some of these applications cannot accept new writes on the nodes being bootstrapped, further increasing the recovery time.
New, innovative hardware brings with it the opportunity for architectural disruption as well as the challenge of how to effectively tap into a vast existing ecosystem of software.
Cloud native technologies like DC/OS have only increased the velocity and importance of software. And yet the value to be unlocked from new architectures is ever more compelling, and well worth the struggle.
Previous MesosCon talks (Asia, June 2017) have spoken about running Mesos on Armv8 processors. Packet’s Ed Vielmetti will use the Qualcomm Centriq™ 2400 (the world’s first 10nm server processor), as a window into the benefits and challenges of embracing new hardware.
With 48 highly optimized cores, the system provides a compelling new resource for software like DC/OS that is trying to help applications and users get the most out of their infrastructure. Furthermore, Qualcomm’s efforts in concert with the community provides an excellent window into the ecosystem development journey.
As J.R.R. Tolkien said: “All's well that ends better.”
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
