You are viewing content from a past/completed QCon

Presentation: Control Theory In Container Orchestration

Track: Delivering on the Promise of Containers

Location: Bayview AB

Duration: 2:55pm - 3:45pm

Day of week: Tuesday

Level: Intermediate - Advanced

Persona: Backend Developer, DevOps Engineer

Share this on:

What You’ll Learn

  1. Find out some of the basic principles of observing systems, controller design, and PID controllers.
  2. Learn how to apply engineering control theory to container management.
  3. Listen about scaling controllers, using both first principles and proven designs from Kubernetes and Mesos.

Abstract

Containers offer 2 central promises: software as encapsulated and reproducible units. A key corollary of those promises is the ability to schedule and manage containers automatically. This session aims to give attendees a solid understanding of leveraging or building container orchestration using feedback signals. 

We’ll apply engineering control theory to key container management scenarios. This will cover basic principles of observing systems, controller design, and PID controllers. In particular, we’ll dive into container scaling controllers, using both first principles and proven designs from Kubernetes and Mesos.

Question: 

Are you talking of automation systems control theory?

Answer: 

It's about applying control theory as an existing engineering rather than accidentally reinventing control theory when you're building automation. I'm going to introduce the fundamentals of control theory, the terminology, and I'll step through some increasingly complex cases in orchestration. Starting with something very simple, maybe health checking container, and going out to focus on auto-scaling. Incrementally bring in more terminology and bring in more concepts, such as cold PID controllers. Concept-scenario, concept-scenario.

Question: 

Who's the audience you are addressing? Poope that are building orchestration tools or those using them?

Answer: 

I'm not sure if I have a focus between those two. A lot of it is to people who are building orchestrators or heavily customising, which can go from customizing code to just very heavily leveraging settings. Auto-scaling is something I want to focus on because that's something that many people heavily customize based on particular servers, particular apps, even if they're not writing platform.

Question: 

When you say 'first principles', what do you mean in the context of orchestration?

Answer: 

I have this little container I want to do something with it without talking about abstract things already existing. In the case of health checks I would want to talk about that in terms of just hearers first off, the kind of state machine of what's going on with this computer when you're managing health check.

Question: 

What do you want someone to leave your talk with?

Answer: 

I want to leave with a better understanding of how we can build automation controllers.

Speaker: Vallery Lancey

Software Developer and Cloud Specialist @Checkfront

Qcon

Vallery Lancey is currently the Lead DevOps Engineer at Checkfront, working on infrastructure automation and reliability.

Find Vallery Lancey at

Similar Talks

Mistakes and Discoveries While Cultivating Ownership

Qcon

Engineering Manager @Netflix in Cloud Infrastructure

Aaron Blohowiak

Monitoring and Tracing @Netflix Streaming Data Infrastructure

Qcon

Architect & Engineer in Real Time Data Infrastructure Team @Netflix

Allen Wang

Future of Data Engineering

Qcon

Distinguished Engineer @WePay

Chris Riccomini

Coding without Complexity

Qcon

CEO/Cofounder @darklang

Ellen Chisa

ML in the Browser: Interactive Experiences with Tensorflow.js

Qcon

Research Engineer in Machine Learning @cloudera

Victor Dibia

Scaling Patterns for Netflix's Edge

Qcon

Playback Edge Engineering @Netflix

Justin Ryan

Tracks

Monday, 11 November

Tuesday, 12 November

Wednesday, 13 November