DevOps Moves to ProductionLori MacVittie. F5 Networks

@lmacvittie

About Lori Developer Lori• 9 years software

development – Enterprise architecture– Telecom – ISVs

• Still hobby coding – PHP + vi – node.js

Networking Lori • 6 years Network

Computing Test Lab – Networking– Security– Integration and Middleware

• 9 years F5 Networks – Technical Marketing– Evangelism

M.S. Computer Science

From Windows to Whenever

“Currently, DevOps is more like a philosophical movement, not yet a precise collection of practices, descriptive or prescriptive”

JOHN ALLSPAW, PATRICK DEBOIS, DAMON EDWARDS, JEZ HUMBLE, GENE KIM, MIKE ORZEN, AND JOHN WILLIS

DevOps Hype

DevOps Reality

Expanding CD into Production Taking a Toll on Dev and Ops

Dev drawn into production

troubleshooting more often

45% 43%

Ops spending more time deploying software

31%

Ops spending more time managing

production apps

31%

Experiencing higher number of

perf and/or availability problems

15%

All of the above

Source: NewRelic sponsored EMA Survey, 2015

Lack of Automation

DEVPROD

IntegratedAgileGitJenkinsMaven Gradle Software API

IndependentWaterfall FilesystemsSSHbash ConsolesHardware CLI

Introducing DevOps to Production

What. The heck. Is that.

Isn’t DevOps Dev and Ops?

Security Network “Operations” Storage

O P E R AT I O N S

Net + Ops Has Same Issues as Dev + Ops

Turret Syndrome

• Don’t collaborate well• Success is measured on

different metrics • Handoffs are awkward and

cause bottlenecks • Processes are inefficient and

burdened by a tower/silo mentality (even within silos)

Develop Build Deploy Test ReleaseAPP

NETWORK DeployThe toolchain that works for apps (dev) is not the same exact tool chain that works for the network (production)

SD $everything

Continuous Deploymen

t

Dev

Continuous Delivery

UI Core QA / Test DBA

Ops

SDx

Infra Network Security Storage

Infrastructure as code

APIs• Call by call • CLI as API• Step by step • Config on device

Templates • Settings • Deployed via API • All at once • Config off device

• Repositories will store templates, policies, and artifacts as easily as code (infrastructure as code)• Git• Subversion

• Network functions increasingly virtualized/containerized for better integration with deploy/test phases • Ansible• Vagrant • Docker

• SDx relies on the other API ecosystem (infrastructure APIs) to enable deploy • VMware• Cisco• OpenStack• SaltStack • Puppet• Chef • Cloud marketplaces

Find commonalities in tool chains to Reduce Friction

Develop

Build

Deploy

THANK YOU Lori MacVittie, F5 Networks

@lmacvittie