Tweet
Tweet

Slide 1

Slide 1 text

Adopting Docker Puppet Labs Gareth Rushgrove Common use cases, from getting started to production

Slide 2

Slide 2 text

@garethr

Slide 3

Slide 3 text

Gareth Rushgrove

Slide 4

Slide 4 text

Gareth Rushgrove

Slide 5

Slide 5 text

This talk

Slide 6

Slide 6 text

Solving local development problems Gareth Rushgrove

Slide 7

Slide 7 text

Improving continuous integration Gareth Rushgrove

Slide 8

Slide 8 text

First steps into production Gareth Rushgrove

Slide 9

Slide 9 text

Going full container Gareth Rushgrove

Slide 10

Slide 10 text

Local development dependencies

Slide 11

Slide 11 text

Developers want to run different operating systems, and manage them adhoc Gareth Rushgrove

Slide 12

Slide 12 text

Local operating systems are often different to the target production operating system Gareth Rushgrove

Slide 13

Slide 13 text

Modern software stacks are complex Gareth Rushgrove

Slide 14

Slide 14 text

Not everyone can know how to manage every component Gareth Rushgrove

Slide 15

Slide 15 text

Being able to run everything locally is incredibly handy Gareth Rushgrove

Slide 16

Slide 16 text

Local virtual machines help, but still have a maintenance cost Gareth Rushgrove

Slide 17

Slide 17 text

Gareth Rushgrove application code dependent services a computer

Slide 18

Slide 18 text

Gareth Rushgrove application code dependent services a shared computer application code application code

Slide 19

Slide 19 text

Gareth Rushgrove application code services in virtual machines a computer

Slide 20

Slide 20 text

Gareth Rushgrove application code dependent services in containers a computer container runtime in a virtual machine

Slide 21

Slide 21 text

Gareth Rushgrove application code services in containers a computer with a native container runtime

Slide 22

Slide 22 text

Gareth Rushgrove Docker Machine

Slide 23

Slide 23 text

$ docker-machine create -d virtualbox dev INFO[0000] Creating SSH key... INFO[0000] Creating VirtualBox VM... INFO[0007] Starting VirtualBox VM... INFO[0007] Waiting for VM to start... INFO[0041] "dev" has been created and is now the active machine. Gareth Rushgrove Create local container runtimes

Slide 24

Slide 24 text

Gareth Rushgrove $ docker-machine ls NAME ACTIVE DRIVER STATE URL dev * virtualbox Running tcp://192.168.99.127:2376

Slide 25

Slide 25 text

Gareth Rushgrove $ docker-machine create -d digitalocean remote INFO[0000] Creating SSH key... INFO[0001] Creating Digital Ocean droplet... INFO[0002] Waiting for SSH... INFO[0070] Configuring Machine... INFO[0109] "remote" has been created and is now the active machine. Create remote container runtimes

Slide 26

Slide 26 text

Gareth Rushgrove $ docker-machine ls NAME ACTIVE DRIVER STATE URL dev virtualbox Running tcp://192.168.99.127:2376 remote * digitalocean Running tcp://104.236.253.181:2376

Slide 27

Slide 27 text

Gareth Rushgrove Docker Compose

Slide 28

Slide 28 text

Gareth Rushgrove $ cat docker-compose.yml web: build: . links: - db - redis ports: - "8000:8000" db: image: postgres image: redis Share workspace definitions

Slide 29

Slide 29 text

Gareth Rushgrove $ cat docker-compose.yml web: build: . links: - db - redis - elasticsearch ports: - "8000:8000" db: image: postgres image: redis image: elasticsearch Easily add new services

Slide 30

Slide 30 text

Continuous Integration

Slide 31

Slide 31 text

Everyone wants faster build times Gareth Rushgrove

Slide 32

Slide 32 text

Isolated builds are essential to avoid unrelated failures due to environment pollution Gareth Rushgrove

Slide 33

Slide 33 text

Virtual machines solve the isolation, but add overhead to a test run Gareth Rushgrove

Slide 34

Slide 34 text

Lots of hardware capacity for peak load can lead to utilisation issues Gareth Rushgrove

Slide 35

Slide 35 text

Docker provides just enough isolation for many test use cases Gareth Rushgrove

Slide 36

Slide 36 text

And a scheduler like Mesos can result in best possible utilisation Gareth Rushgrove

Slide 37

Slide 37 text

Gareth Rushgrove Docker Jenkins plugin

Slide 38

Slide 38 text

The aim of the docker plugin is to be able to use a docker host to dynamically provision a slave, run a single build, then tear-down that slave. Gareth Rushgrove https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin

Slide 39

Slide 39 text

Gareth Rushgrove Mesos Jenkins plugin

Slide 40

Slide 40 text

The mesos-jenkins plugin allows Jenkins to dynamically launch Jenkins slaves on a Mesos cluster depending on the workload! Gareth Rushgrove https://wiki.jenkins-ci.org/display/JENKINS/Mesos+Plugin

Slide 41

Slide 41 text

Gareth Rushgrove jenkins slave jenkins slave jenkins slave jenkins master Job

Slide 42

Slide 42 text

Gareth Rushgrove jenkins slave jenkins slave jenkins slave jenkins master Job

Slide 43

Slide 43 text

Gareth Rushgrove jenkins slave jenkins slave jenkins slave jenkins master Job Job Job one job per slave is no problem

Slide 44

Slide 44 text

Gareth Rushgrove jenkins slave jenkins slave jenkins slave jenkins master Job Job Job but with multiple jobs per slave we can run into dependency issues

Slide 45

Slide 45 text

Gareth Rushgrove mesos slave mesos slave mesos slave jenkins master Job Job Job each container is a short lived jenkins slave

Slide 46

Slide 46 text

Gareth Rushgrove eBay CI Solution

Slide 47

Slide 47 text

Docker is an implementation detail. You’re not directly using the Docker interfaces. Gareth Rushgrove

Slide 48

Slide 48 text

A package format and a runtime

Slide 49

Slide 49 text

1 container per VM pattern Gareth Rushgrove

Slide 50

Slide 50 text

Gareth Rushgrove

Slide 51

Slide 51 text

It’s all about security domains Gareth Rushgrove

Slide 52

Slide 52 text

Take advantage of containers in production now, while minimising downsides Gareth Rushgrove

Slide 53

Slide 53 text

Operating containers requires new knowledge and new tools Gareth Rushgrove

Slide 54

Slide 54 text

Visibility for operations Gareth Rushgrove

Slide 55

Slide 55 text

Problems with ps Gareth Rushgrove

Slide 56

Slide 56 text

Gareth Rushgrove $ ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND ... 999 1807 0.2 11.4 867624 464572 ? Ssl 09:38 0:21 mysqld Is this process in a container?

Slide 57

Slide 57 text

Gareth Rushgrove $ ps -eo ucmd,cgroup COMMAND CGROUP ... mysqld 9:perf_event:/docker/61e76d2c39121282474ff895b9b3ba2addd775cdea6d2ba89ce76c28 Which container is that?

Slide 58

Slide 58 text

Gareth Rushgrove Sysdig

Slide 59

Slide 59 text

Provides a Kernel module, which hooks into cgroups and namespaces Gareth Rushgrove (Prediction: We’ll see more of this kind of thing)

Slide 60

Slide 60 text

Gareth Rushgrove $ sudo sysdig -c topcontainers_cpu CPU% container.name ----------------------------------------------------------------------- 90.13% mysql 15.93% wordpress1 7.27% haproxy 3.46% wordpress2 CPU usage acros containers

Slide 61

Slide 61 text

Gareth Rushgrove $ sudo sysdig -pc -c topprocs_cpu container.name=client CPU% Process container.name ---------------------------------------------- 02.69% bash client 31.04% curl client 0.74% sleep client CPU usage in a single container

Slide 62

Slide 62 text

Gareth Rushgrove $ sudo sysdig -pc -c topprocs_net Bytes Process Host_pid Container_pid container.name --------------------------------------------------------------- 72.06KB haproxy 7385 13 haproxy 56.96KB docker.io 1775 7039 host 44.45KB mysqld 6995 91 mysql 44.45KB mysqld 6995 99 mysql 29.36KB apache2 7893 124 wordpress1 29.36KB apache2 26895 126 wordpress4 29.36KB apache2 26622 131 wordpress2 29.36KB apache2 27935 132 wordpress3 29.36KB apache2 27306 125 wordpress4 22.23KB mysqld 6995 90 mysqlclient Network bandwidth

Slide 63

Slide 63 text

Gareth Rushgrove $ sudo sysdig -pc -A -c echo_fds "fd.ip=172.17.0.3 and fd.ip=172.17.0.7" ------ Write 103B to [haproxy] [d468ee81543a] 172.17.0.7:37557->172.17.0.3:80 (hapr GET / HTTP/1.1 User-Agent: curl/7.35.0 Host: 172.17.0.7 Accept: */* X-Forwarded-For: 172.17.0.8 ------ Read 103B from [wordpress1] [12b8c6a04031] 172.17.0.7:37557->172.17.0.3:80 ( GET / HTTP/1.1 User-Agent: curl/7.35.0 Host: 172.17.0.7 Accept: */* X-Forwarded-For: 172.17.0.8 ------ Write 346B to [wordpress1] [12b8c6a04031] 172.17.0.7:37557->172.17.0.3:80 (a HTTP/1.1 302 Found Date: Sat, 21 Feb 2015 22:19:18 GMT Traffic between containers

Slide 64

Slide 64 text

Metadata Gareth Rushgrove

Slide 65

Slide 65 text

Gareth Rushgrove

Slide 66

Slide 66 text

Metadata like name, version, build time, build host, dependencies, descriptions, licence, signature and urls Built in logic like pre/post install scripts An API to interact with this – the rpm or apt/deb commands Gareth Rushgrove - - - https://www.devco.net/archives/2015/03/30/some-thoughts-on-operating-containers.php

Slide 67

Slide 67 text

Gareth Rushgrove $ docker exec -ti mycontainer container --metadata|json_reformat { "validate_method": "/srv/support/bin/validate.sh", "start_method": "/srv/support/bin/start.sh", "update_method": "/srv/support/bin/update.sh" "validate": true, "build_cause": "TIMERTRIGGER", "build_tag": "jenkins-docker rbldnsd-55", "ci": true, "image_tag_names": [ "hub.my.net/ripienaar/rbldnsd" ], "project": "rbldnsd", "build_time": "2015-03-30 06:02:10", "build_time_stamp": 1427691730, "image_name": "ripienaar/rbldnsd", "gitref": "e1b0a445744fec5e584919711cafd8f4cebdee0e", }

Slide 68

Slide 68 text

$ docker exec -ti rbldnsd container --examine Container first started at 2015-03-30 05:02:37 +0000 (1427691757) Names: Project Name: centos_base Image Name: ripienaar/centos_base Image Tag Names: hub.my.net/ripienaar/centos_base Build Info: CI Run: true Git Hash: fcb5f3c664b293c7a196c9809a33714427804d40 Build Cause: TIMERTRIGGER Build Time: 2015-03-24 03:25:01 (1427167501) Build Tag: jenkins-docker centos_base-20 Actions: START: not set UPDATE: not set VALIDATE: not set Gareth Rushgrove

Slide 69

Slide 69 text

Community standards here would be awesome Gareth Rushgrove

Slide 70

Slide 70 text

Base image Gareth Rushgrove

Slide 71

Slide 71 text

Scratch images Minimal distros like busybox Full OS like Ubuntu or Debian Full OS with working init system Gareth Rushgrove - - - -

Slide 72

Slide 72 text

No one right answer. Depends on context; existing tooling, application runtime, etc. Gareth Rushgrove

Slide 73

Slide 73 text

Managing configuration Gareth Rushgrove

Slide 74

Slide 74 text

Separate configuration from containers Gareth Rushgrove

Slide 75

Slide 75 text

Retain advantages of declarative configuration management tools Gareth Rushgrove

Slide 76

Slide 76 text

Gareth Rushgrove

Slide 77

Slide 77 text

Gareth Rushgrove

Slide 78

Slide 78 text

Clusters of containers

Slide 79

Slide 79 text

Warning Beyond here lies the future Gareth Rushgrove

Slide 80

Slide 80 text

Higher level interfaces Multi-host scheduling Health checks Load balancing Gareth Rushgrove - - - -

Slide 81

Slide 81 text

Gareth Rushgrove Borg

Slide 82

Slide 82 text

Gareth Rushgrove Kubernetes

Slide 83

Slide 83 text

Gareth Rushgrove Mesos

Slide 84

Slide 84 text

Gareth Rushgrove CoreOS

Slide 85

Slide 85 text

Gareth Rushgrove

Slide 86

Slide 86 text

Gareth Rushgrove Lattice

Slide 87

Slide 87 text

Gareth Rushgrove Docker Swarm

Slide 88

Slide 88 text

Gareth Rushgrove Amazon ECS

Slide 89

Slide 89 text

A quest for an API Gareth Rushgrove

Slide 90

Slide 90 text

Current lack of tools build atop those APIs Gareth Rushgrove

Slide 91

Slide 91 text

Conclusions

Slide 92

Slide 92 text

We should talk about container use cases more than about containers Gareth Rushgrove

Slide 93

Slide 93 text

Different use cases probably require different tooling Gareth Rushgrove

Slide 94

Slide 94 text

Different use cases will have different best practices Gareth Rushgrove

Slide 95

Slide 95 text

You don’t have to use containers everywhere to see benefits Gareth Rushgrove

Slide 96

Slide 96 text

Questions? And thanks for listening Gareth Rushgrove