DevconTLV 2014 (Jan) - DIY DevOps

1,380 views
1,223 views

Published on

We all know that bringing devops practices to your organisation is hard and very labour intensive task. Despite the fact that for large organisations it is still a real challenge, for small startups and development teams devops practices can be adopted relatively easily.

In this talk Leonid will share his experience of bringing devops practices to small organisations, and prove that devops isn't something that you should postpone for a later growth stage, but something you can do (and relatively easy) now, at the first stages of your idea inception!

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,380
On SlideShare
0
From Embeds
0
Number of Embeds
101
Actions
Shares
0
Downloads
30
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

DevconTLV 2014 (Jan) - DIY DevOps

  1. 1. DIY DEVOPS @leonidlm www.leonidmirsky.com
  2. 2. About me LEONID MIRSKY Freelancer (1+ year) Liveperson (5+ years)
  3. 3. DevOps is... Chef/Puppet
  4. 4. DevOps is... Continuous Delivery
  5. 5. DevOps is... Docker
  6. 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. 7. Implementing DevOps as after though is hard!
  8. 8. DevOps is part of startup engineering course curriculum https://www.coursera.org/course/startup
  9. 9. “For startups, DevOps is business as usual but ...” http://www.pistoncloud.com/2013/09/is-devops-optional-or-normal/
  10. 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. 11. The bigger the organization becomes, the harder it is to introduce DevOps practices
  12. 12. Start early!
  13. 13. How can we make your startup more DevOps oriented?
  14. 14. How much time will it take?
  15. 15. Culture Startup team characteristics: 1. Small agile teams 2. One/two influencers 3. Doitall culture (full stack developers)
  16. 16. Probably only small adjustments are needed
  17. 17. Culture - try to avoid...
  18. 18. Sharing - Internal WhatsApp (hipchat/...) incidents group Practice Lessons Learned
  19. 19. Sharing - External
  20. 20. total work estimate = 1 day
  21. 21. Automation - Continuous Deployment
  22. 22. Automation - Continuous Deployment Similar tools are available: TravisCI, CircleCI ... Extremely easy to set up Relatively cheap monthly subscription
  23. 23. Configuration Management requires a lot of your resources
  24. 24. Automation - Configuration Management Usually CM can be avoided at the beginning Instead use a combination of 1. fabric / capistrano / shell scripts 2. AMI / snapshotting
  25. 25. total work estimate = 5 days (1 + 4)
  26. 26. Measurement Infrastructure User Experience Application
  27. 27. Don’t start from infrastructure monitoring (Nagios)
  28. 28. Measurement - Application Start from measuring the Application Quick win - NewRelic agent to gather application stack metrics
  29. 29. Measurement - Application
  30. 30. 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
  31. 31. 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-
  32. 32. total work estimate = 8 days (1 + 4 + 3)
  33. 33. It is only a beginning...
  34. 34. 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
  35. 35. Start simple. Grow with the demand.
  36. 36. Thank you! @leonidlm www.leonidmirsky.com Design inspiration: https://speakerdeck.com/lara/design-for-performance
  37. 37. 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
  38. 38. Measurement User Experience Application Infrastructure
  39. 39. Measurement NewRelic Librato (instrumentation) collectd
  40. 40. 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)

×