Many developers think DevOps is nice and valuable but consider it a SEP (Somebody Else's Problem) - not because they do not care but simply because they do not know enough about Ops to relate it to their daily work. This presentation tries to fill the gap a bit, clarifies some common misunderstandings and explains the typical needs of an Ops admin. Then a set of design principles is shown that address the needs of an admin and help to build applications ready for Ops - because in the end it's all about production! As always lots of the information of this presentation is on the voice track but yet I think that you can find some helpful pointers in this deck.
9. Top 5 Needs of an Admin
1. Give me my peace and quiet!
2. Don‘t make me think!
3. Let me see that everything is fine!
4. Show me the problem – now!
5. Tell me what to do!
10. Top 5 Needs of an Admin (translated)
1. Give me my peace and quiet!
(The application should just run smoothly)
2. Don‘t make me think!
(Rollout, setup and operation of the application should be easy)
3. Let me see that everything is fine!
(The application should show its state)
4. Show me the problem – now!
(The application should provide concise error messages and enable easy root cause drilldown)
5. Tell me what to do!
(The application should be documented properly – including error handling instructions)
11. Top 3 Dev Challenges
1. Manageability
2. Resilience
3. Transparency
4. Documentation
19. • Context-related parameters
Do not stage – managed by stage admin
• Application-related parameters
Must be staged – managed by application admin
• Business-related parameters
Must be staged – managed by business admin
37. • Consider log message structure
All required information / machine readable / human readable
• Define logging policy
Debug and less: developers perspective / Info and more: operations perspective
39. Wrap-up
• Dev often does not know Ops
• Know the needs of an admin
• Face the challenges for a developer
• Apply the design principles
… and then you‘re ready for DevOps