Lot's of talks focus on DevOps. This one strives to leave the attendee with small, measurable, actionable steps he or she can take to start their own DevOps journey. YMMV :)

1. DevOps
for Developers
#DesertCodeCamp @wfbutton

2. Promises of
DevOps
Faster releases
More confidence
Better failure detection
Higher resiliency
Improved monitoring
#DesertCodeCamp @wfbutton

3. Remember where we came from?
…and where we don’t want to go back to!
#DesertCodeCamp @wfbutton

4. IT and Development were not aligned
Provisioning hardware was slow and expensive
Changes were risky and hard to rollback
We’ll have that server
ready for you next quarter.
#DesertCodeCamp @wfbutton

5. To the cloud!
• Just needed manager’s CC
• Infinite access to servers
Cloud all the
things!
#DesertCodeCamp @wfbutton

6. and then the bill came…
Accounting was not pleased.
#DesertCodeCamp @wfbutton

7. Rule #1
Use what you need, but need what you use.
#DesertCodeCamp @wfbutton

8. Use the tools:
AWS Cost Analyzer
Billing Alerts
Heroku Dashboard
#DesertCodeCamp @wfbutton

9. and now everything is great…
#DesertCodeCamp @wfbutton

10. Managing Deployments
• Define the rules of production
• Who can push code (ideally,
no one)
• Tests that must pass
• Rollbacks
• Change review boards suck
(but sometimes are needed)
#DesertCodeCamp @wfbutton

11. Rule #2
Thou shalt not touch production (by hand).
#DesertCodeCamp @wfbutton

12. Jenkins or CircleCI
Define the workflow
Triggered automatically
Rules/Tests must pass
No humans!
#DesertCodeCamp @wfbutton

13. Testing
• Tests for your code
• Mandatory
• Minimum levels of test
• Server tests
• rspec for puppet
• Test Kitchen
• CI Tool requires passing tests
• API testing with jmeter
#DesertCodeCamp @wfbutton

14. Don’t you forget about me.
• Configuration management
• Remember how we got here?
• IT does play a role
• …and it should be automated
• Chef/Puppet/Ansible/Salt
• Same rules:
• Tests/ Rollback/ Ephemeral
#DesertCodeCamp @wfbutton

15. Rule #3
Infrastructure is code.
#DesertCodeCamp @wfbutton

16. From a Disaster Recovery
View
• Find the most recent backup
• Pray that it’s good
• Build a new server
• Search Stack Overflow
• Test
• Search Stack Overflow
• Ask business what data they
really need
• Update LinkedIn profile
• Deploy via CI
#DesertCodeCamp @wfbutton

17. Monitoring
It’s not just for disk space
or CPU
or Memory…
(though those are important
too!)
#DesertCodeCamp @wfbutton

18. Correlated Events
Response time tagged with deploys
#DesertCodeCamp @wfbutton

19. Apdex Score
• It’s a real thing
• Measure of response times
against a threshold
• https://en.wikipedia.org/wiki/
Apdex
• Satisfied: T or less
• Tolerating: >T, <= 4T
• Frustrating: >4T
#DesertCodeCamp @wfbutton

20. Things that
don’t
Polling is great for this
TTL on metrics (Riemann)
Instrument alerts and fallbacks
in code
The Art of Monitoring
-James Turnbull
#DesertCodeCamp @wfbutton

21. Metrics
Overload
What are your customers
paying you for?
How do you measure that?
What are the
dependencies?
#DesertCodeCamp @wfbutton

22. Rule #4
If it’s important, measure it.
#DesertCodeCamp @wfbutton

23. Rules in Review
• Use what you need, but need what you use.
• Thou shalt not touch production (by hand).
• Infrastructure is code.
• If it’s important, measure it.
#DesertCodeCamp @wfbutton

24. Your Homework
• Pick a rule.
• Make some progress.
• Socialize.
• Iterate.
This is how you
build culture, and
culture is really
what DevOps is
about.
#DesertCodeCamp @wfbutton