Adopting Docker in today's IT - Carl Caum

Slide 1

Slide 1 text

Adopting Docker in today's IT AKA Moving Faster without Breaking Things … or getting fired

Slide 2

Slide 2 text

Me. @ccaum Recovering sysadmin

Slide 3

Slide 3 text

I once built things.

Slide 4

Slide 4 text

Tell me about you.

Slide 5

Slide 5 text

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

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

The tools we use should help bring us together and better understand each other. But do so as efficiently as possible

Slide 8

Slide 8 text

A note on DevOps Culture Automation Measurement Sharing Be these two 8

Slide 9

Slide 9 text

A note on configuration management ● Identification ● Control ● Status Accounting ● Audit & Verification 9

Slide 10

Slide 10 text

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

Slide 11

Slide 11 text

No content

Slide 12

Slide 12 text

Policy Driven Development

Slide 13

Slide 13 text

Embrace Policy Driven Development The process ● Definition ● Tests ● Implementation ● Monitoring 13

Slide 14

Slide 14 text

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

Slide 15

Slide 15 text

A note on public images 15 No

Slide 16

Slide 16 text

A note on Change Advisory Boards (CABs) 16 You can (and should) replace them, but it won’t happen over night.

Slide 17

Slide 17 text

Change Advisory Boards 17 Start submitting code diffs to your reviews

Slide 18

Slide 18 text

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

Slide 19

Slide 19 text

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