Downloaded 39 times
Uploaded byMatthew Skelton
Software operability and run book collaboration - DevOps Summit, Amsterdam
The document discusses software operability and run book collaboration. It begins with background on the speaker and defines operability as the properties that allow a system to work well in production. It then discusses using run books to facilitate collaboration between developers and operations on operational considerations. The document advocates making operability a priority and treating it as an operational feature rather than a non-functional requirement. It suggests automating operations over time when possible.
More Related Content
Similar to Software operability and run book collaboration - DevOps Summit, Amsterdam
Software operability and run book collaboration - DevOps Summit, Amsterdam
- 1. #unidevops Software Operability and RunBook Collaboration Matthew Skelton 14th November 2013 DevOps Summit Amsterdam www.devopssumit.com @matthewpskelton softwareoperability.com
- 2. • Software Operability •Run Book Collaboration • Making Operability Work • Questions #unidevops Agenda
- 3. • Software systemssince 1998 • Build & Deployment at thetrainline.com • London Continuous Delivery meetup group - londoncd.org.uk • Experience DevOps workshops #unidevops Background
- 4.
- 5. • Operability: theproperties of a system which make it work well in Production #unidevops Software Operability
- 6.
- 7.
- 8. • David Copeland(@davetron5000): “How your software runs in production is all that matters. The most amazing abstractions, cleanest code, or beautiful algorithms are meaningless if your code doesn’t run well on production.” • http://www.naildrivin5.com/blog/2013/06/16/production-is-all-that-matters.html #unidevops Software Operability
- 9.
- 10. #unidevops Ops Folk areUsers Too!
- 11.
- 12.
- 13.
- 14.
- 15.
- 16. #unidevops Example • • 1 Table ofContents 2 System Overview – – – – – – – – – 2.1 Service Overview 2.2 Contributing Applications, Daemons, and Windows Services 2.3 Hours of Operation 2.4 Execution Design 2.5 Infrastructure and Network Design 2.6 Resilience, Fault Tolerance and HighAvailability 2.7 Throttling and Partial Shutdown 2.8 Required Resources 2.9 Expected Traffic and Load • • • 4.1 Configuration Management – – – • 7.5 Troubleshooting – 8.1 Maintenance Procedures 7 Operational Tasks • • 5.2 Backup Procedures 5.3 Restore Procedures – – 6.1 Error Messages 6.2 Events 6 Monitoring and Alerting 8.1.1 Patching – – • • – • – 8.1.3.1 Log Rotation 8.2.1 Technical Testing 8.2.2 Post-Deployment 9 Failure and Recovery Procedures – – – • 8.1.1.1 Normal Cycle 8.1.1.2 Zero-Day Vulnerabilities 8.1.2 GMT/BST time changes 8.1.3 Cleardown Activities 8.2 Testing • • 5 System Backup and Restore 5.1.1 Special Files 7.4.1 System Rebuilds 8 Maintenance Tasks • 5.1 Backup Requirements 3 Security and Access Control 4 System Configuration • 7.1 Deployment 7.2 Batch Processing 7.3 Power Procedures 7.4 Routine Checks – 2.10 Environmental Differences 2.11 Tools – • – – – – • 6.3 Health Checks 6.4 Other Messages 2.9.1 Hot or Peak Periods 2.9.2 Warm Periods 2.9.3 Cool or Quiet Periods – – • • – – 9.1 Failover 9.2 Recovery 9.3 Troubleshooting Failover and Recovery 10 Contact Details
- 17. #unidevops Example • • 1 Table ofContents 2 System Overview – 2.1 Service Overview – 2.2 Contributing Applications, Daemons, and Windows Services – 2.3 Hours of Operation – 2.4 Execution Design – 2.5 Infrastructure and Network Design – 2.6 Resilience, Fault Tolerance and High-Availability – 2.7 Throttling and Partial Shutdown – 2.8 Required Resources – 2.9 Expected Traffic and Load • • • • • • • • 3 Security and Access Control 4 System Configuration 5 System Backup and Restore 6 Monitoring and Alerting 7 Operational Tasks 8 Maintenance Tasks 9 Failure and Recovery Procedures 10 Contact Details
- 18.
- 19.
- 20.
- 21. • • • • Focus on thecollaboration Run book is a means, not an end Throw it away when complete (?) Aim to automate more over time • See http://runbookcollab.info/ #unidevops Run Book as Collaboration
- 22.
- 23.
- 24.
- 25. #unidevops “I just wantto write code”
- 26.
- 27.
- 28. • • • • • Operational Features, not“NFRs” Sustainable collaboration Sensible, fair on-call rotas Over-compensate in time off Avoid burn-out #unidevops The operability of operability
- 29.
- 30. • Patterns for Performanceand Operability – Ford, Gileadi, Purba, Moerman • http://whoownsmyoperability.com/ – Recommended reading lists #unidevops Further Reading
- 31. • Software Operability– How to make software work well in Production – Due early 2014 • Sign up at OperabilityBook.com • Discount code for DevOps Summit attendees #unidevops Operability Book
- 32. • A hands-onworkshop for DevOps culture • Forthcoming dates: – Amsterdam: 15 November 2013 – Bangalore: December 2013 – London: February 2014 (tbc) • http://experiencedevops.org/ #unidevops Experience DevOps
- 33.
- 34.
- 35.
- 36. • • • • • Continuous Delivery Tuesday 8thApril 2014 London, UK http://pipelineconf.info/ @PipelineConf #unidevops PIPELINE Conference