Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile Operations or How to sleep better at night

3,258 views

Published on

Presentation at Agile Tour Riga 2012 conference

Published in: Technology

Agile Operations or How to sleep better at night

  1. 1. Agile Operations or How to sleep better at night Raimonds Simanovskis
  2. 2. @rsim github.com/rsimRaimonds Simanovskis
  3. 3. The easiest Business Intelligence tool on the Web
  4. 4. Before Agile...Customer Developer Tester
  5. 5. Agile Cross-Functional Team Analyze Design Code Test
  6. 6. Development vs Operations Agile SysAdmins Support
  7. 7. DevOps CustomerSupport DeveloperSysAdmin Tester DBA
  8. 8. How to apply Agile values and practicesto Operations?
  9. 9. Agile Values Individuals and Processes over interactions and tools Working Comprehensive overproduction system documentation Customer SLA over collaboration negotiation Responding to Following over change a plan
  10. 10. Infrastructure as code
  11. 11. Typical systemadministration
  12. 12. Typical system administration App1 Pkg2 Pkg1 DB OSInstallation Developmentinstructions server App1 App1 Pkg2 Pkg3 Pkg2 Pkg3 DB Pkg1 Pkg1 DB OS OS1 OS2 Production Test ser vers server
  13. 13. Typical system administration App1 Pkg2 Pkg1 DB OSInstallation Developmentinstructions server App1 server Pkg2 Pkg3 Test Pkg1 DB OS1 OS2 Production ser vers
  14. 14. Automateinfrastructure build Version control system
  15. 15. Automateinfrastructure build Development sand-box Test server Version control system Production servers
  16. 16. Local sand-box toolsVagrant + VirtualBox
  17. 17. Infrastructure provisioning andconfiguration tools Sprinkle
  18. 18. Continuousdeployment
  19. 19. From development to productionDevelopment Operations Production
  20. 20. From development to productionDevelopment Operations Production
  21. 21. From development to productionDevelopment Operations Production
  22. 22. Fear of change
  23. 23. From Big Releasesto small deployments Faster feedback Problems localized faster Reduces risk Reduces overhead
  24. 24. Getting started Continuous integration Automated deployment Real-time alerts Root cause analysis
  25. 25. Good practicesZero-downtime deployments Feature flags Gradual rollouts A/B split testing
  26. 26. Monitoring and self-healing
  27. 27. What to monitor? EverythingCPU Memory is fine!Disk Network
  28. 28. Start with end-user experience HTTPRemote Is it alive? user Time to respond? Our One-time failure or server frequent failures?
  29. 29. Real user monitoring
  30. 30. Preventive error log analysis
  31. 31. What to do when something is wrong? Application 1Monitoring Application 2application Database Operating system
  32. 32. What to do when something is wrong? Application 1Monitoring Application 2application Database Operating system Alert
  33. 33. What to do when something is wrong? Application 1Monitoring Application 2application Database Operating system Alert
  34. 34. What to do when something is wrong? a rt ! Application 1 Re s tMonitoring Application 2application Database Operating system
  35. 35. Fault tolerant systems Design for failure Fail fast Collect failure data Restore to known state
  36. 36. Monitoring tools
  37. 37. Managing infrastructure with code is fun! Pkg2 Pkg1 DB App1 OS

×