Docker in a big company 
1
/me 
• Damien DUPORTAL 
• DevOps Engineer @ Worldline 
• French living in Belgium (French Fries are actually Belgian) 
• Former Teacher in engineering schools (EPSI, ENSG) 
• Rock climber 
2
/me 
• Twitter : @DamienDuportal 
• Mail : damien.duportal@gmail.com 
• Github : github.com/dduportal 
• Blog (Work In Progress) : dduportal.github.io 
3
Worldline, an Atos company 
• 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 
4
Docker in a big company 
What’s the menu today ? 
• Why DevOps ? 
• The path to Docker 
• Problem ? Solutions ! 
• The future 
• One more thing… 
5
6 
Why Devops ?
Why DevOps ? 
This is my dev. laptop : 
7
Why DevOps ? 
This is my production : 
8
Why Devops ? 
9
Why Devops ? 
Separation of duties… 
10
Why Devops ? 
11 
… leads to silos 
(cc. Michael Ducy from Opscode)
Why Devops ? 
Kind of classy silos ! 
12 (cc. Michael Ducy from Opscode)
Why Devops ? 
How to : 
• Reduce TTM of a software part (ship ! Now !) ? 
• Align IT offer to business needs ? 
• Be more efficient against the silos ? 
13
Why Devops ? 
Top-Down 
Bottom-up
Why Devops ? 
15 
So we have to « goat » 
(cc. Michael Ducy from Opscode)
The path to Docker
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
Problems ? Solutions !
Problems ? Solutions ! 
How to run a Docker daemon on Windows ? 
• Stayin’ with Virtualbox 
• The lightweight VM as possible 
• Ready for dev
Problems ? Solutions ! 
Boot2docker : 
• 30 Mb 
• Docker up-to-date and ready 
• VirtualBox ready
Problems ? Solutions ! 
How to reuse already made things ? 
• Maintain already known workflow 
• Easily share folders from Windows 
• Limit configuration effort (proxy, certificates, 
persistence)
Problems ? Solutions ! 
Vagrant + dduportal/boot2docker : 
• Vbox shared folder 
• Provisioning 
• « vagrant-proxyconf » plugin
Problems ? Solutions ! 
How to provision the stack ? 
• Dev. don’t care 
• Dev. use Maven : describe 
• Dev. want ops stuff and their stuff
Problems ? Solutions ! 
Fig 
• YAML text-based : shareable 
• Hierarchy : intentional description 
• Image or build your services
Problems ? Solutions ! 
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)
Problems ? Solutions ! 
dduportal/fig Docker Image 
• Debian-based 
• Embeds a working fig 
• Needs to share Docker socket 
• Won’t be needed when ‘docker groups’
Problems ? Solutions ! 
We got a blueprint ! 
Vagrant 
VirtualBox Private Sandbox IaaS 
Boot2docker VM Boot2docker VM Blueprint 
dduportal/fig 
My App Stack 
docker
Problems ? Solutions !
The future
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
A lot of ??? 
 Multi Host ? 
 Networking ? 
 Monitoring ? 
 Migration ? 
 Orchestration 
 Provisioning 
 Testing ? 
The future 
Just kidding  
PRODUCTION ?
One more thing 
Sup’ Steve
The « Human stack »
The « Human stack » 
Solomon Hykes – SF DockerCon 2014 : 
« The real value of Docker is not technology, 
it’s getting people to agree on something»
The « Human stack » 
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

Docker in a big company

  • 1.
    Docker in abig company 1
  • 2.
    /me • DamienDUPORTAL • DevOps Engineer @ Worldline • French living in Belgium (French Fries are actually Belgian) • Former Teacher in engineering schools (EPSI, ENSG) • Rock climber 2
  • 3.
    /me • Twitter: @DamienDuportal • Mail : damien.duportal@gmail.com • Github : github.com/dduportal • Blog (Work In Progress) : dduportal.github.io 3
  • 4.
    Worldline, an Atoscompany • 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 4
  • 5.
    Docker in abig company What’s the menu today ? • Why DevOps ? • The path to Docker • Problem ? Solutions ! • The future • One more thing… 5
  • 6.
  • 7.
    Why DevOps ? This is my dev. laptop : 7
  • 8.
    Why DevOps ? This is my production : 8
  • 9.
  • 10.
    Why Devops ? Separation of duties… 10
  • 11.
    Why Devops ? 11 … leads to silos (cc. Michael Ducy from Opscode)
  • 12.
    Why Devops ? Kind of classy silos ! 12 (cc. Michael Ducy from Opscode)
  • 13.
    Why Devops ? How to : • Reduce TTM of a software part (ship ! Now !) ? • Align IT offer to business needs ? • Be more efficient against the silos ? 13
  • 14.
    Why Devops ? Top-Down Bottom-up
  • 15.
    Why Devops ? 15 So we have to « goat » (cc. Michael Ducy from Opscode)
  • 16.
  • 17.
    The path toDocker 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 ?
  • 18.
    The path toDocker • Linux on Windows 7 : VirtualBox ! • Manage and share VMs : Vagrant ! • Provision your VMs : Shell or Chef !
  • 19.
    The path toDocker Remember ?
  • 20.
    The path toDocker With that stack :
  • 21.
    The path toDocker Another problem : the learning curve
  • 22.
    The path toDocker So why not Docker ? • It’s fast (start & cache) • It’s reproducible • It’s easy to launch bunch of stuff
  • 23.
  • 24.
    Problems ? Solutions! How to run a Docker daemon on Windows ? • Stayin’ with Virtualbox • The lightweight VM as possible • Ready for dev
  • 25.
    Problems ? Solutions! Boot2docker : • 30 Mb • Docker up-to-date and ready • VirtualBox ready
  • 26.
    Problems ? Solutions! How to reuse already made things ? • Maintain already known workflow • Easily share folders from Windows • Limit configuration effort (proxy, certificates, persistence)
  • 27.
    Problems ? Solutions! Vagrant + dduportal/boot2docker : • Vbox shared folder • Provisioning • « vagrant-proxyconf » plugin
  • 28.
    Problems ? Solutions! How to provision the stack ? • Dev. don’t care • Dev. use Maven : describe • Dev. want ops stuff and their stuff
  • 29.
    Problems ? Solutions! Fig • YAML text-based : shareable • Hierarchy : intentional description • Image or build your services
  • 30.
    Problems ? Solutions! 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)
  • 31.
    Problems ? Solutions! dduportal/fig Docker Image • Debian-based • Embeds a working fig • Needs to share Docker socket • Won’t be needed when ‘docker groups’
  • 32.
    Problems ? Solutions! We got a blueprint ! Vagrant VirtualBox Private Sandbox IaaS Boot2docker VM Boot2docker VM Blueprint dduportal/fig My App Stack docker
  • 33.
  • 34.
  • 35.
    The future Nearfuture : • 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
  • 36.
  • 37.
    A lot of???  Multi Host ?  Networking ?  Monitoring ?  Migration ?  Orchestration  Provisioning  Testing ? The future Just kidding  PRODUCTION ?
  • 38.
    One more thing Sup’ Steve
  • 39.
    The « Humanstack »
  • 40.
    The « Humanstack » Solomon Hykes – SF DockerCon 2014 : « The real value of Docker is not technology, it’s getting people to agree on something»
  • 41.
    The « Humanstack » 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
  • 42.
    Docker makes technology « human centric » It’s true DevOps
  • 43.
    @people around Docker: you’re awesome !
  • 44.

Editor's Notes

  • #42 Look at me : why am i here telling you those things ? Because Docker makes me listen, learn, communicate, and share !