Ops for Developers

Because I can't bring myself to use the term 'DevOps'

Derek Carter aka 'goozbach'

Goozbach Infrastructure Solutions

Historically

Developers
vs
Operations

Contrary Objectives (devs)

• Product Specs/Features
• Bug Fixes
• Fast Fast Fast

Contrary Objectives (ops)

• Uptime is king
• Resources
  • Hardware
  • Bandwidth
• Disaster Recovery
• Capacity Planning
• Security

Tools (devs)

• Test Driven Development
• Scrum
• Agile
• Waterfall
• Libraries and Frameworks

Tools (ops)

• CapEX
• Maintainers Windows
• Change management
• Install Servers
• SSH
• Bash

There is a Better Way

• DevOps movement
• Less us vs them
• More All of us for the customer/product

Building Blocks of DevOps

• Source Control
  • SCM
    • SVN
    • Git
  • Versioning
    • http://semver.org

Versioning

• This

    http://example.com/api/foo/new/
  

• VS This

    http://example.com/api/1.0.0/foo/new/
  

Self Service Infrastructure

• Reduce dependency on Ops team
• No more waiting on sysadmin to buy/hang/configure servers
• Configuration management
  • Ansible
  • Puppet
  • Chef
• Functional Tests
• Continuous Integration

Making DevOps Work

• Proper Stacks
  • production
  • QA/Testing/Preprod
  • Development

Stack holy grail

• Production not touched by human hands
  • If you logged in you have failed.
• QA stack matches Production as closely as possible
• Dev stack VERY cheap to produce/destroy
• Multiple Dev stacks
  • Vagrant files anyone?

Keeping Tabs

• You cannot improve what you do not measure
• Monitoring
• Trending
• Alerting

What do we aspire to?

• Etsy
• Fuse

Where do I start?

http://www.opsreportcard.com/

References

• Devops devops and enterprise inertia the developer is dead killing the developer distilling devops Code as craft
• Books Information Technology corrosion competitive advantage
• Virtual Environments Vagrant Vagrant Boxes Virtualbox
• Config Management Ansible Puppet

Thank You!