DevconTLV 2014 (Jan) - DIY DevOps
1 like1,698 views
The document discusses the implementation of DevOps in startups, emphasizing the importance of culture, automation, measurement, and sharing knowledge among teams. It outlines steps to transition toward a DevOps-oriented approach, including specific tools for continuous deployment and application performance measurement. The author highlights that cultural change can be challenging, especially in larger organizations, and stresses the need to start simple and adapt as business demands grow.
DevconTLV 2014 (Jan) - DIY DevOps
- 2. About me LEONID MIRSKY Freelancer (1+ year) Liveperson (5+ years)
- 6. What is DevOps? (for me, shortly) “Finishing what agile development started” (www. devops.com) DevOps is all about CAMS 1. Culture 2. Automation 3. Measurement 4. Sharing
- 7. Implementing DevOps as after though is hard!
- 8. DevOps is part of startup engineering course curriculum https://www.coursera.org/course/startup
- 9. “For startups, DevOps is business as usual but ...” http://www.pistoncloud.com/2013/09/is-devops-optional-or-normal/
- 10. “the longer you’ve had separate dev and ops departments, the more difficult the cultural shift will be” http://www.pistoncloud.com/2013/09/is-devops-optional-or-normal/
- 11. The bigger the organization becomes, the harder it is to introduce DevOps practices
- 12. Start early!
- 13. How can we make your startup more DevOps oriented?
- 14. How much time will it take?
- 15. Culture Startup team characteristics: 1. Small agile teams 2. One/two influencers 3. Doitall culture (full stack developers)
- 16. Probably only small adjustments are needed
- 17. Culture - try to avoid...
- 18. Sharing - Internal WhatsApp (hipchat/...) incidents group Practice Lessons Learned
- 20. total work estimate = 1 day
- 21. Automation - Continuous Deployment
- 23. Automation - Continuous Deployment Similar tools are available: TravisCI, CircleCI ... Extremely easy to set up Relatively cheap monthly subscription
- 24. Configuration Management requires a lot of your resources
- 25. Automation - Configuration Management Usually CM can be avoided at the beginning Instead use a combination of 1. fabric / capistrano / shell scripts 2. AMI / snapshotting
- 26. total work estimate = 5 days (1 + 4)
- 28. Don’t start from infrastructure monitoring (Nagios)
- 29. Measurement - Application Start from measuring the Application Quick win - NewRelic agent to gather application stack metrics
- 31. Measurement - Application Instrument your application code and send the metrics to Librato Codahale’s presentation ‘metrics metrics everywhere’ is a must... http://www.youtube.com/watch?v=czes-oa0yik
- 32. Measurement - Infrastructure Add Librato collectors (collectd, ...) to get additional “free” metrics Integrate cloudwatch metrics into Librato http://support.metrics.librato. com/knowledgebase/articles/195366-amazon-awscloudwatch-integration-
- 33. total work estimate = 8 days (1 + 4 + 3)
- 34. It is only a beginning...
- 35. When will you need to invest more? When the business demands more 1. Autoscaling 2. More elaborate automation is needed 3. SaaS/PaaS functionality is too narrow 4. Ops expertise
- 36. Start simple. Grow with the demand.
- 39. Measurement - Application Start from measuring the Application 1. NewRelic for “free” application stack metrics 2. Instrument your app and send the data to Librato 3. Aggregate logs with Papertrail
- 42. Why DevOps might be hard Cultural change could be hard! Hiring people with relevant devops expertise Lack of team and management buy-in (http://puppetlabs.com/2013-state-of-devops-infographic)