devops for developers

DevOpsfor Developers

#DesertCodeCamp @wfbutton

Promises of DevOpsFaster releases

More confidence Better failure detection

Higher resiliency Improved monitoring


Remember where we came from?…and where we don’t want to go back to!


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.


To the cloud!

• Just needed manager’s CC

• Infinite access to servers

Cloud all the things!


and then the bill came…Accounting was not pleased.


Rule #1Use what you need, but need what you use.


Use the tools:

AWS Cost Analyzer Billing Alerts

Heroku Dashboard


and now everything is great…#DesertCodeCamp @wfbutton

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)


Rule #2Thou shalt not touch production (by hand).


Jenkins or CircleCI Define the workflow Triggered automatically Rules/Tests must pass No humans!


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


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


Rule #3Infrastructure is code.


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


MonitoringIt’s not just for disk space

or CPU or Memory…

(though those are important too!)


Correlated EventsResponse time tagged with deploys


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


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


Metrics Overload

What are your customers paying you for?

How do you measure that?

What are the dependencies?


Rule #4If it’s important, measure it.


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.


Your Homework

• Pick a rule.

• Make some progress.

• Socialize.

• Iterate.

This is how you build culture, and

culture is really what DevOps is

about.


devops for developers

Software