DEV/ops Evolution & Revolution 2016

21
© 2014 Trace3, All rights reserved. Evolution & Revolution By: Brian Carpio – Chief DevOps Architect DevOps 2016

Transcript of DEV/ops Evolution & Revolution 2016

Page 1: DEV/ops Evolution & Revolution 2016

© 2014 Trace3, All rights reserved.

Evolution & Revolution

By: Brian Carpio – Chief DevOps Architect

DevOps 2016

Page 2: DEV/ops Evolution & Revolution 2016

Brian Carpio

• 15 Years Of Experience In IT • IBM, Oracle, Qwest, Broadhop, Pearson, Aetna• Consulting Company (Security, Automation, etc..)

• Strong Security Background• First Online Hacker War Game Site Intrusionsec• Pen Testing For Multiple F500

• Designed API Driven Self Service Infrastructure • Leading DevOps Transformation

Page 3: DEV/ops Evolution & Revolution 2016

What DevOps Is Not

DevOps: A culture shift or movement that encourages great collaboration which fosters building and releasing

better quality software quicker with more reliability.

DevOps is NOT:A role, person, or organizationSomething only operations engineers doSomething only software engineers doSomething only infrastructure engineers doWriting puppet or chef scriptsvRealize, NSX, ACI, Cliqr, Docker

Page 4: DEV/ops Evolution & Revolution 2016

Lean Got Us Started

Page 5: DEV/ops Evolution & Revolution 2016

10 Deployments A Day

Page 6: DEV/ops Evolution & Revolution 2016

Ops Problem Now

Page 7: DEV/ops Evolution & Revolution 2016

Supporting Developers

Page 8: DEV/ops Evolution & Revolution 2016

IT Security

Page 9: DEV/ops Evolution & Revolution 2016

Config Management

Page 10: DEV/ops Evolution & Revolution 2016

IaaS

Page 11: DEV/ops Evolution & Revolution 2016

Shadow IT

Page 12: DEV/ops Evolution & Revolution 2016

NoOps

Page 13: DEV/ops Evolution & Revolution 2016

Put Developers On Call

Page 14: DEV/ops Evolution & Revolution 2016

Don’t Feed The Bears

Page 15: DEV/ops Evolution & Revolution 2016

Developers Carry Pagers Too

“As a developer, there has never been a more satisfying point in my career than when I wrote the code, I pushed the button to deploy it, I watched the metrics to see if it actually worked in production, and fixed it if it broke.”

– Tim Tischler Director of Operations Engineering, Nike, Inc.

Page 16: DEV/ops Evolution & Revolution 2016

Microservices

Page 17: DEV/ops Evolution & Revolution 2016

DEV/ops & Building Infrastructure APIs

Page 18: DEV/ops Evolution & Revolution 2016

Building The Manufacturing Plant

Page 19: DEV/ops Evolution & Revolution 2016

Operations Culture

Page 20: DEV/ops Evolution & Revolution 2016

CI/CD/CD

Page 21: DEV/ops Evolution & Revolution 2016

The End