Download - Docker in a big company

Docker in a big company

1

2

• Damien DUPORTAL

• DevOps Engineer @ Worldline

• French living in Belgium (French Fries are actually Belgian)

• Former Teacher in engineering schools (EPSI, ENSG)

• Rock climber

/me

3

• Twitter : @DamienDuportal

• Mail : [email protected]

• Github : github.com/dduportal

• Blog (Work In Progress) : dduportal.github.io

/me

4

• 7 200 people around the World (17 countries)

• I.T. leader in e-payment & transactional activities

• European market : public and industry customers

• 1,1 billion € of turnover

• Part of the Atos group since 2004

Worldline, an Atos company

• Why DevOps ?

• The path to Docker

• Problem ? Solutions !

• The future

• One more thing…

Docker in a big company

What’s the menu today ?

5

6

Why Devops ?

Why DevOps ?This is my dev. laptop :

7

Why DevOps ?This is my production :

8

9

Why Devops ?

Separation of duties…

10

Why Devops ?

11

Why Devops ?… leads to silos

(cc. Michael Ducy from Opscode)

Why Devops ?Kind of classy silos !

12 (cc. Michael Ducy from Opscode)

13

How to :

• Reduce TTM of a software part (ship ! Now !) ?

• Align IT offer to business needs ?

• Be more efficient against the silos ?

Why Devops ?

Why Devops ?

Bottom-up

Top-Down

15

Why Devops ?So we have to « goat »

(cc. Michael Ducy from Opscode)

The path to Docker

17

Use case :

• Linux : How to run « ls –l » ?

• Our tools : How to validate a « managed service » ?

• Network and clusters :

How to validate when my app scales ?

The path to Docker

• Linux on Windows 7 : VirtualBox !

• Manage and share VMs : Vagrant !

• Provision your VMs : Shell or Chef !

The path to Docker

Remember ?

The path to Docker

With that stack :

The path to Docker

Another problem : the learning curve

The path to Docker

So why not Docker ?

• It’s fast (start & cache)

• It’s reproducible

• It’s easy to launch bunch of stuff

The path to Docker

Problems ? Solutions !

How to run a Docker daemon on Windows ?

• Stayin’ with Virtualbox

• The lightweight VM as possible

• Ready for dev


Boot2docker :

• 30 Mb

• Docker up-to-date and ready

• VirtualBox ready


How to reuse already made things ?

• Maintain already known workflow

• Easily share folders from Windows

• Limit configuration effort (proxy, certificates,

persistence)


Vagrant + dduportal/boot2docker :

• Vbox shared folder

• Provisioning

• « vagrant-proxyconf » plugin


How to provision the stack ?

• Dev. don’t care

• Dev. use Maven : describe

• Dev. want ops stuff and their stuff


Fig

• YAML text-based : shareable

• Hierarchy : intentional description

• Image or build your services


You said « run anywhere » ?

• Use of private IaaS (thru vagrant plugin)

• Env. differences (local / remote)

• Fig isn’t full-statically compiled (no b2d,

no busybox)


dduportal/fig Docker Image

• Debian-based

• Embeds a working fig

• Needs to share Docker socket

• Won’t be needed when ‘docker groups’


We got a blueprint !


Vagrant

dduportal/fig

My App Stack

VirtualBox Private Sandbox IaaS

docker

Boot2docker VM Boot2docker VM Blueprint

The future

Near future :

• Private registry + private hub

• Share workstation inside Docker images

• Docker client on Windows ! You guys are awesome !

• Packer-based build for base images (reuse)

• Teach Docker to Dev and Op

The future

The future

A lot of ???

Multi Host ?

Networking ?

Monitoring ?

Migration ?

Orchestration

Provisioning

Testing ?

The futureJust kidding

PRODUCTION ?

One more thing

Sup’ Steve

The « Human stack »

Solomon Hykes – SF DockerCon 2014 :

« The real value of Docker is not technology,

it’s getting people to agree on something»


Docker is the « bottom-up » for devops.

I learned 2 things with that tool :

• It helps people communicate better : we can work and

share humanly

• It creates a learning context : people can see the

value of their jobs


Docker makes technology

« human centric »

It’s true DevOps

@people around Docker :

you’re awesome !

Thank You.

44