From Engines to Orchestrators

A brisk introduction to container runtimes (engines) and an understanding of when container orchestrators enter and what role they play. We’ll look at what makes them alike, yet unique. Presented at ContainerizeThis 2016.

Transcript

1. From Engines to Orchestrators http://calcotestudios.com/feto Lee Calcote Sept 30th, 2016
2. http://calcotestudios.com/feto Lee Calcote clouds, containers, infrastructure, applications and their management linkedin.com/in/leecalcote @lcalcote blog.gingergeek.com lee@calcotestudios.com
3. Show of Hands @lcalcote
4. @lcalcote Types of Containers
5. System Containers Like a VM Full OS image Multiple processes Application Containers Single process Use namespaces to deal with resource isolation for a single process. Use cgroups to manage resources for a group of processes. Similarities:
6. @lcalcote rkt docker runC kurma --- containerd systemd-nspawn OpenVZ Solaris Zones BSD jails Linux-VServer AIX WPARs LXC ---- LXD CGManager machinectl ---- qemu-kvm, lkvm System Container Engines Application Container Engines
7. Container Specifications
8. @lcalcote Implemented by - is the canonical implementation leverages runC is an implementation of for FreeBSD using jails and ZFS rkt Kurma Jetpack Implemented by - is the reference implementation is a hypervisor-based runtime launches an Intel VT-x secured Clear Containers 2.0 hypervisor runC runV cc-oci-runtime
9. @lcalcote a specification for the lifecycle of a running container tooling for the runtime a software shipping container image format spec with security and naming as components tooling for the image runtime-spec runtime-tools image-spec image-tools https://opencontainers.org
10. Get Started with your Engines and get your engines started
11. Popular Engine process models rkt executes as CLI; no daemon Can run Docker Images and also App Container Images (ACIs) Security has been a focal concern uses HTTPS to locate and download remote ACIs and their attached signatures Docker Engine runs a daemon rkt systemd $ rkt run postgres application systemd $ docker run postgres application Docker Engine containerd runC
12. Definition: [ awr -k uh -streyt -or] [k uh n- tey-ner]
13. Core Capabilities Cluster Management Host Discovery Host Health Monitoring Scheduling Orchestrator Updates and Host Maintenance Service Discovery Networking and Load-Balancing Additional Key Capabilities Application Health Monitoring Application Deployments Application Performance Monitoring
14. One size does not fit all. @lcalcote A strict apples-to-apples comparison is inappropriate and not the objective, hence characterizing and contrasting.
15. Kubernetes @lcalcote
16. Genesis & Purpose an opinionated framework for building distributed systems or as its tagline states "an open source system for automating deployment, scaling, and operations of applications." Written in Golang, Kubernetes is lightweight, modular and extensible considered a third generation container orchestrator led by Google, Red Hat and others. bakes in load-balancing, scale, volumes, deployments, secret management and cross- cluster federated services among other features. Declaratively, opinionated with many key features included @lcalcote
17. @lcalcote Docker Swarm
18. Genesis & Purpose Swarm is simple and easy to setup. Swarm is responsible for the clustering and scheduling aspects of orchestration. Originally an imperative system, now declarative Swarm’s architecture is not complex as those of Kubernetes and Mesos Written in Golang, Swarm is lightweight, modular and extensible @lcalcote