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.

Modern devOps with Docker

1,206 views

Published on

2014 was the year of Docker. The container-based world exploded on the scene with the promise to reinvent how you think about distributed applications. But is it just hype or are there immediate benefits to be realized? Join us to explore Continuous Integration/Continuous Delivery leveraging containers, one of the early use cases proving successful with Docker, resulting in reduced Dev/Test cycle times and lower infrastructure costs. We'll walk through the end-to-end CI/CD workflow, highlighting the big wins containers have introduced, as well as discuss common challenges to avoid. Lastly, we'll look ahead, identifying the next set of use cases to likely achieve real-world benefits from containers.

Published in: Technology
  • Be the first to comment

Modern devOps with Docker

  1. 1. devops with docker @beshippable
  2. 2. avi cavale co-founder & ceo @avinci || avi@shippable.com continuous app delivery pipelines
  3. 3. the most frequently asked question during an outage
  4. 4. the most frequently asked question during an outage what changed?
  5. 5. the immediate next question is….
  6. 6. the immediate next question is…. who made the change?
  7. 7. both questions are bad for your business
  8. 8. both questions are bad for your business slowing down
  9. 9. both questions are bad for your business courtesy : dilbert comics slowing down finger pointing
  10. 10. change is the root cause of almost all outages, but…
  11. 11. change is the root cause of almost all outages, but… “business requires change”
  12. 12. “need to embrace change” dev$ app$A$ dev$ app$B$ dev ops
  13. 13. “need to embrace change” dev$ app$A$ dev$ app$B$ dev ops devops: a CULTURE of embracing change
  14. 14. we embraced it tightly
  15. 15. time change required change complete traditional application delivery pipeline
  16. 16. time change required change complete development traditional application delivery pipeline
  17. 17. time change required change complete development unit testing traditional application delivery pipeline
  18. 18. time change required change complete development unit testing functional testing traditional application delivery pipeline
  19. 19. time change required change complete development unit testing functional testing deployment traditional application delivery pipeline
  20. 20. time change required change complete development unit testing functional testing deployment running traditional application delivery pipeline
  21. 21. time change required development unit testing functional testing deployment running devops culture embraced change complete application delivery pipeline
  22. 22. time change required development unit testing functional testing deployment running devops culture embraced change complete 15-20% improvement application delivery pipeline
  23. 23. time change required development unit testing functional testing deployment running devops culture embraced change complete 15-20% improvement org silo friction1 application delivery pipeline
  24. 24. time change required development unit testing functional testing deployment running devops culture embraced change complete 15-20% improvement org silo friction1 tool chain vertically optimized2 application delivery pipeline
  25. 25. time change required development unit testing functional testing deployment running devops culture embraced change complete 15-20% improvement org silo friction1 tool chain vertically optimized2 deployable image built last3 application delivery pipeline
  26. 26. 20% better is not a REVOLUTION! courtesy : V for Vendetta
  27. 27. courtesy : V for Vendetta why not build deployable image first?
  28. 28. devops is culture, so to make it a F A C T
  29. 29. devops is culture, so to make it a application delivery pipelines F A C rictionless gile ontinuous ransparent T
  30. 30. Transparency if you want to do just 1 thing this year every action • starts in a chat room • tracked as a github issue • ends in a chat room
  31. 31. Transparency if you want to do just 1 thing this year business req support prod errors every action • starts in a chat room • tracked as a github issue • ends in a chat room
  32. 32. Continuous • continuous integration for every pull-request • 1 step docker build image for every merge to `master` • 1 step auto deploy & continuous functional testing • deployment to prod is just changing an ENV var
  33. 33. Agile • no SSH! • bug fixes, new changes, ops scripts all go the same way • always deployable `master` • no feature branching • feature flags • in-code branching • small frequent changes • beta program
  34. 34. Frictionless r10r11r12api r19r20r21fe container fab dev beta prod r12 api r21 fe r11 api r20 fe r10 api r20 fe i234 i179 i444 i534 i191 i744 app delivery pipelines
  35. 35. ship images 40-60 times a day noticeable FACTs 15 devs in 5 timezones 2hrs mean time to resolve bugs
  36. 36. where are we going from here? micro-services baby! throughput creates merge hell rapid changes on 1 repo creates images chaos
  37. 37. avi@shippable.com signup for our beta program 45,000 devs on Shippable 25,000 build containers/week quiz me
  38. 38. thank you very much @beshippable

×