Adopting Docker in today's IT - Carl Caum

As IT teams plan to deploy Docker, they are often looking for the shortest path to get from where they are today to where they want to be with Docker. One challenge is getting the Docker runtime deployed on operating systems already approved by IT and part of existing deployment processes. Once the runtime is deployed, teams need to quickly start managing their container apps across the available cluster nodes. Finally, teams need a clear path to integrate Docker management technologies like Docker Universal Control Plane into existing change management and delivery processes.

This talk will cover:

Using configuration management tools to deploy the docker runtime, sync Docker images, and ensure containers are running where desired with the desired runtime configuration.

Using configuration management practices of identification, control, status accounting, and verification/audit to manage Docker infrastructure over time

Build Docker infrastructure change management processes leveraging infrastructure as code to enable continuous peer review, audit, and replication.

Carl Caum is a technical marketing manager at Puppet Labs with a background in systems administration, software development, and product management. He specializes in IT cultures with a focus on how tools can be leveraged to enforce cultural change in otherwise stagnant IT organizations to increase collaboration and job satisfaction. He tweets at @ccaum.

Transcript

1. Adopting Docker in today's IT AKA Moving Faster without Breaking Things … or getting fired
2. Me. @ccaum Recovering sysadmin
3. I once built things.
4. Tell me about you.
5. A note on traditional IT • Each team has their own priorities • A lack of communication encourages ignorance • Ignorance encourages animosity • Teams act with authority instead of expertise 5 Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All
6. A note on empathy “Empathy rarely extends beyond our line of sight.” If we use Docker I’ll never have to talk to you again 6
7. The tools we use should help bring us together and better understand each other. But do so as efficiently as possible
8. A note on DevOps Culture Automation Measurement Sharing Be these two 8
9. A note on configuration management • Identification • Control • Status Accounting • Audit & Verification 9
10. Don’t burn everything down Begin by embracing your existing world • Use IT approved OSes • Embrace Policy Driven Development • Build all your own images from scratch • Plan for audits from the beginning 10
12. Policy Driven Development
13. Embrace Policy Driven Development The process • Definition • Tests • Implementation • Monitoring 13
14. Include InfoSec from the beginning 14 • Talk to them during the planning phase • Anticipate questions and have clear reasons for your plan • Understand the regulatory and corporate compliance requirement you must adhere to • Work with them to define policies in prose
15. A note on public images 15 No
16. A note on Change Advisory Boards (CABs) 16 You can (and should) replace them, but it won’t happen over night.
17. Change Advisory Boards 17 Start submitting code diffs to your reviews
18. A note on audits 18 Things that matter • You have a process and can prove it’s being used • Any config state can be proven at any moment • A change log exists, is comprehensive, and accurate
19. A note on conlusions Don’t just embrace Docker for you and your team. Understand everyone’s expertise, responsibilities, and pressures in the product delivery process. Include InfoSec, QA, etc early in the planning phase. Know every config in every image and how/why it got there (and prove it). Have an audit trail for everything. 19 Preso title goes here. To update, go to File > Page Setup > Header/Footer, paste title, Apply All