Agile 2013 Talk: How DevOps Changes Everything

How DevOps
changed everything
Karthik Gaekwad
@iteration1 #AgileDevOps
Wednesday, August 7, 13

Howdy!
• I’m Karthik Gaekwad
• Senior Web Engineer
• Mentor Graphics Embedded
• From Austin,TX
• We have great BBQ,
chill people and
brutal summers!
#AgileDevOps@iteration1 Agile 2013

My Background
• National Instruments (NI)
• Ecommerce Team (Agile)
• R&D Cloud Team (DevOps)
• Mentor Graphics Embedded
• Cloud Team (DevOps)
• Organizer: CloudAustin, DevOpsDays
Austin, TheAgileAdmin

Audience Survey

The most important DevOps things I’ve
learned over the last 4 years
Let’s not waste time!

First, we have to talk about agile...

There was a waterfall
Requirements
Design
Implement, Test
Maintain
Deploy

Roles
Requirements
Design
Implement
Maintain
Deploy
Product Manager, Business Analyst
Business Analyst,Web Designer,Architect
Programmer Analyst,Web Developer
Programmer Analyst, System Administrator
System Administrator

S
Waterfall..

“But I told you this already”
Communication

“That is not my job!”
Accountability

“That is not a priority”
Time to deliver

**About the time I started...

New Product: Partslist
Collaborate and tag parts to build
large systems

Transitioned to SCRUM
2 Week Iterations
Targeted Feature sets
Demo at end of iteration

The Product Team >
Traditional Organization

Results
Working together, building things that were
wanted

Results
Between Business and IT

Results
Better products being delivered, at a faster
pace.
Methodology expanded to all other web
teams...

Results
I love my job! #ForReal

Agile: Retrospective
• Scrum brought team together.
• Building products on time, which were
actually needed.
• Superior collaboration between business
and IT.
• Organization shift -> Scrum

Ops conversations
“Agile is cool! but it’s
hard for ops to be
agile because it takes
months to buy and
provision servers.”

Ops conversations
Deployer
Dude
“All day everyday”

But in the community...

“We’re making cloud
products now”
“Go build us
cloud products
now”
Sincerely,
Management

products now”
“Cloud is
AWESOME!”

products now”
“Cloud is
OSSM”
-Dave Nielson
-NIST

products now”
“Cloud is AWESOME
OSSM”
On-demand
Self-service
Scalable
Measurable

“Give me API or
give me death”
@littleidea

products now”
“Agile DevOps
Cloud Team”

DevOps
“A cultural and professional movement”
Adam Jacobs

DevOps
“System administrators participating in an agile
development process alongside developers and using many
of the same agile techniques for their systems work.”
The Agile Admin Blog

Alison Chaiken
Embedded Linux,Thought Leader
“Get rid of the devs;
get rid of the ops; let’s
just ﬁnd people who can
solve problems”

CULTURE
MEASUREMENT
AUTOMATION
SHARING
Pillars of
DevOps
John Willis
Damon Edwards
By:

DevOps 101
Ideas and Stories
Free!! No charge!!

products now”
“Agile DevOps
Cloud Team”
Buzzword friendly!

We had a goal:
“Build a cloud authentication prototype”

C
U
LT
U
R
E
Our 1st sprint(s) sucked!

C
U
LT
U
R
E
But we suffered from
“Wall of confusionitis”
Devs: “REST Services!”
Ops: “System Stability!”

C
U
LT
U
R
E
Not seeing eye to eye
#Frustrating #Angry

C
U
LT
U
R
E

C
U
LT
U
R
E
Really, this is “Platform Architecture”, but I’m too lazy to redo the image

C
U
LT
U
R
E
Devs and ops understand good architecture.
#GoodPlaceToStart

C
U
LT
U
R
E
Think platform ﬁrst, then app later.
#PaaS #REST

• Everyone understood architecture
• Helped everyone speak same language
• Reduced friction
• Called it “The System Model”
A
U
T
O
M
A
T
IO
N
1st win:Architecture

• “Model Driven Automation”
• Championed by ops
• Everyone needs to understand the model
• Figure out how to deploy the model
A
U
T
O
M
A
T
IO
N

• Programmable Infrastructure Environment
(PIE)
• Based on version controlled architecture
diagram
• Provisioned cloud boxes
• Ran deploys
• Set standard naming for boxes
• On demand deploy for apps
A
U
T
O
M
A
T
IO
N

Outcomes
• Ops learns Java!
• Ops learns version control!
• Developers get comfortable with
production environments!
• ...Now we’re speaking many common
languages!
A
U
T
O
M
A
T
IO
N

No Chef? No Puppet?
A
U
T
O
M
A
T
IO
N
Are y’all crazy???

A
U
T
O
M
A
T
IO
N
Everybody be cool
• We believe the cleanest abstraction layer is
starting with the entire system you’re trying
to model
• In 2009, chef and puppet were younger
• We were scared of Ruby
• We needed windows cloud support
• Plus dawg, cloud was a wild wild world then!

A
U
T
O
M
A
T
IO
N
Please automate!!

A
U
T
O
M
A
T
IO
N
Do I pick Chef or Puppet??
“whatever makes you happy”

SH
A
R
IN
G
For chef/puppet, you’ll need
to code.
#NotJust4Devs #NotScary

SH
A
R
IN
G
Stuck? Just ask your DevOps
dev guy!
#NotJust4Devs

SH
A
R
IN
G
Don’t hide.
Share the knowledge

SH
A
R
IN
G
App conﬁgs

SH
A
R
IN
G
App conﬁgs
Easy Change Management
Let your automation control
these kind of ﬁles

Tools Philosophy
D
EV
O
PS
• Needed to work for cloud
• Facilitate collaboration
• Charts and graphs
• Everyone wants to use it

Tools Philosophy
M
EA
SU
R
E
• Monitoring = Cloudkick
• Monitor servers
• Monitor code (custom synthetic checks)
We use #datadog now

Tools Philosophy
M
EA
SU
R
E
Teach your devs how to monitor their code,
and they will love the tool
Example: #NewRelic

Tools Philosophy
M
EA
SU
R
E
If it measures business metrics, management
will love you too!
#statsd #dogstatsd
HINT: Management pays you. Make them happy

Tools Philosophy
M
EA
SU
R
E
WASTE OF TIME:
SSH’ing into a box to read log
ﬁles

Tools Philosophy
M
EA
SU
R
E
Get a logging solution.
Plethora of choices!
#Logstash #Graylog #Splunk #Sumologic
Which one? CloudAustin July Meetup

SH
A
R
IN
G
You’ll need more tools
Find them or write them!
You’re devops now!
Tools Philosophy

Tools Philosophy
M
EA
SU
R
E
DevOps victory:
“People” use tools that solve
their core problems

DevOps 201
MOAR Ideas and Stories
For ops who can code
and dev not scared of linux

C
U
LT
U
R
E
Is different for every team.
What works for your team,
works for your team

C
U
LT
U
R
E
This worked for us...
#AlwaysBeInclusive

C
U
LT
U
R
E
Stuff Breaks
Like...all the time

C
U
LT
U
R
E
#DontDoThis

C
U
LT
U
R
E
Be Cool. Fix the issue at hand
If you panic, everyone else does too.

C
U
LT
U
R
E
Post Mortem
Do a Post mortem

C
U
LT
U
R
E
Post Mortem
It’s okay to admit mistakes
You’re not Batman...

C
U
LT
U
R
E
Post Mortem
Why x5
Add more tests
Make sure it doesn’t happen again

C
U
LT
U
R
E
RELEASE OFTEN
Release with 4 changes
is less risky than
Release with 40,000 changes

D
EV
O
PS
Testing

D
EV
O
PS
Test Everything
Test the code
Test the infrastructure
It’s all the same now
#infrastructureAsCode

D
EV
O
PS
Free Time?
Write more tests!

D
EV
O
PS
CONTINUOUSLY

D
EV
O
PS
Manual Changes
To
Production

D
EV
O
PS
Manual Changes
Don’t do this.
Do this:
1. Make manual changes in dev
2.Add to your chef/puppet script
3. Release to test/prod

DevOps 301
MOAR MOAR Tips
For when your team grows

Security in the loop
Add security audits as a part of your
sprint.
We do an audit periodically
@Gauntlt @RuggedDevOps

Hire an infosec pro to your devops
team

No budget?
Try a cross functional working group

Expanding Teams?
• Rotate times for meetings (status/planning)
• Scrum standups were recorded and dropbox(ed)
• “OK to call” philosophy
• Campﬁre chat (saves history)
• Ownership of new features

Expanding Teams?
• No secret: Face to face is always better
• Prioritize travels for visits to teammates

Everyone asking
for DevOps?
The embedded DevOps model
works*

Everyone asking
for DevOps?
Make sure your team culture is strong
enough so you don’t lose person
permanently :)

Start Small...
Don’t say
“WE’RE 100% DEVOPS TODAY”

DevOps 401
MOAR MOAR MOAR Ideas
For next time. I don’t have any.
Tweet #agiledevops for your best ideas!

STILL STUCK?
Just ask!
We’re devops, and this is real
(even though we can’t deﬁne it)
Twitter: #devopsama
http://devopsweekly.com/
Go to a devopsdays
https://groups.google.com/forum/#!forum/devops

DevOps: Retrospective
• DevOps and CAMS
bring team together.
• Building stable
products on time,
which were actually
needed.
• Superior collaboration
between devs and ops
• Organization shift ->
DevOps

DevOps: Retrospective
• DevOps and CAMS
bring team together.
• Building stable
products on time,
which were actually
needed.
• Superior collaboration
between devs and ops
DevOps
• Scrum brought team
together.
• Building products on
time, which were
actually needed.
• Superior
collaboration between
business and IT.
Scrum

Thank you!
Let’s work together, and
solve the problems that
our business wants us
to!
#DevOps

Agile 2013 Talk: How DevOps Changes Everything

Recommended

Recommended

More Related Content

Similar to Agile 2013 Talk: How DevOps Changes Everything

Similar to Agile 2013 Talk: How DevOps Changes Everything (20)

More from Karthik Gaekwad

More from Karthik Gaekwad (20)

Recently uploaded

Recently uploaded (20)

Agile 2013 Talk: How DevOps Changes Everything