Red Hat IT’s

DevOps Journey:Year One Retrospective

Bill Montgomery

IT Manager, Red Hat

Birth of a DevOps Initiative

CIO

LOB DevEnterprise DevRegional ITOCIO IT Enablement

Ops SysEng “Inception” EA InfoSec

Bill / Mgr (Ops)

Jen / PO (Prgm mgmt)

Steve / Eng (InfoSec & Dev) Chris / Eng (SysAdmin)

Tim / Eng (Release Eng)

Ryan / Eng (SysAdmin)

The Dedicated Team

Mission

Enable IT to improve Red Hat’s

business agility by halving cycle

time and doubling frequency of

software changes by October 2015

StrategyDevOps

Continuous

Delivery

Release

automation

Where to begin?

ValueR

eadin

ess

ERP apps

SaaS apps

“Packaged” apps

Landing on SOA Services & ESB (“SSE”)

● Service Oriented Architecture: APIs into Red Hat’s business

● Enterprise Service Bus: app-level communications backbone

● Integration point for back-office & front-office apps

● At intersection of every major program

● Optimize SSE’s delivery to make everything else easier

Partnership

Partnership

Challenges

Measuring Progress

● Today:o Cycle time

o Deployment frequency

● Soon:o Change failure rate

o MTTR

The Journey

Read this first

Winternewt (formerly “Release Engine”)

● Repeatable, automated deployments

● Developed in Red Hat IT

● Open Source

● https://github.com/RHInception

● Modular, extensible

Worked well

Dedicated team

Agile / iterative

approach

Build DevOps from

CI/CD practices

Things we learned

Clarify mission

early

Create a hypothesis

of record and

measure against it

Attach to a low-risk

project to start

Lessons learned

Help me!

How do we transition from a 24-month DevOps change initiative

to sustained ongoing investment in DevOps?

I want to know your thoughts!

Twitter: @billmvt

Email: bmontgom@redhat.com

Thank You!

Q&A