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.

Continuous Delivery: Delivering Client Value at Light Speed - DevCon 2015

361 views

Published on

Continuous Delivery Slides from DevCon 2015

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Continuous Delivery: Delivering Client Value at Light Speed - DevCon 2015

  1. 1. This year… This dude promises to NOT Stand on his head.
  2. 2. • https://www.youtube.com/watch?v=SIaVsG7 m8n4
  3. 3. Continuous Delivery: Delivering Client Value at Light Speed Aaron Blythe
  4. 4. Aaron Blythe - Cerner • Writing Code • Answering questions • Sharing Thoughts • Running Meetups @ablythe
  5. 5. Aaron Blythe – Outside Cerner • Writing Code • Answering questions • Running Meetups http://aaronblythe.org/ @ablythe
  6. 6. Three Things to Get Right •Culture •Workflow •Tooling
  7. 7. • http://www.leanenterprisebook.com/
  8. 8. Part 1 Culture 2. Workflow 3. Tooling
  9. 9. Fremont Assembly Plant http://en.wikipedia.org/wiki/Fremont_Assembly
  10. 10. NUMMI plant http://en.wikipedia.org/wiki/NUMMI
  11. 11. Tesla Factory http://en.wikipedia.org/wiki/Tesla_Factory
  12. 12. “The long-term value of an enterprise is not captured by the value of its products and intellectual property but rather by its ability to continuously increase the value it provides to customers-and to create new customers-through innovation.”
  13. 13. Friction
  14. 14. Mission Control vs. Command and Control The Prussion Army lost to Napoleon in 1809 Picture courtesy: http://en.wikipedia.org/wiki/Prussian_Army
  15. 15. Auftragstaktik
  16. 16. 2014 State of Devops Report 9,200 technologists
  17. 17. • I would recommend this organization as a good place to work. • I have the tools and resources to do my job well. • I am satisfied with my job. • My job makes good use of my skills and abilities.
  18. 18. Part 2 Workflow 3. Tooling 1. Culture
  19. 19. http://blog.crisp.se/2013/02/05/yassalsundman/continuous-delivery-vs-continuous- deployment
  20. 20. • So when can you say you’re doing continuous delivery? I’d say it’s when you could flip a switch to go to continuous deployment if you decided that was the best way to deliver value to your customers. • http://continuousdelivery.com/2010/08/conti nuous-delivery-vs-continuous-deployment/
  21. 21. http://blog.crisp.se/2013/02/05/yassalsundman/continuous-delivery-vs-continuous- deployment
  22. 22. 232 Highlights – Kindle Version • It should always be cheaper to create a new environment than to repair an old one. Humble, Jez; Farley, David (2010-07-27). Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation (Addison-Wesley Signature Series (Fowler)) (Kindle Location 1633). Pearson Education. Kindle Edition.
  23. 23. Let’s Take a Test!!!!11!! If your configuration management process is sound, you should be able to answer “yes” to the following questions: • Could you completely re-create your production system, excluding production data, from scratch from the version -controlled assets that you store? • Could you regress to an earlier, known good state of your application? • Can you be sure that each deployed environment in production, in staging, and in test is set up in precisely the same way? If not, then your organization is at risk.
  24. 24. Command and Control vs. Promise Theory
  25. 25. mvn deploy rake deploy
  26. 26. Continuous Delivery Tool Roll Out test-kitchen Chef Push Jobs rake deploy kitchen test knife push Project Project.yml Kitchen.yml Chef roles
  27. 27. Part 3 Tooling 1. Culture 2. Workflow
  28. 28. Continuous Delivery Tools Workflow PluginDelivery Many more over the next couple years…
  29. 29. Chef Delivery
  30. 30. Go (from ThoughtWorks)
  31. 31. Jenkins
  32. 32. Demo
  33. 33. • Jenkins – Open Source “Workflow Plugin” • Enterprise Support needed for “Workflow Stage View” – Working POC – Open Source • Job – https://spork.devcerner.com/view/opsinfra/job/workflow_tes t_ops_clientlog_server/configure • Source Code – http://github.cerner.com/OpsInfra/jenkins_workflow_test
  34. 34. • http://blog.cloudbees.com/2014/12/jenkins- operations-and-continuous.html
  35. 35. Workflow Plugin TODO’s • Permissions for input approval – https://issues.jenkins-ci.org/browse/JENKINS-27134 • Option for stage step to cancel older executions – https://issues.jenkins-ci.org/browse/JENKINS-27039 • Visual Distinction of Steps – https://issues.jenkins-ci.org/browse/JENKINS-27394
  36. 36. Chef Delivery • https://www.chef.io/delivery/ • ChefConf 2015 Keynote: – https://www.youtube.com/watch?v=YA3VXAQqDi 4&index=7&list=PL11cZfNdwNyO9CpTWH2qjYfzys EtpfOCd – @ about 23:30
  37. 37. Verify Stage
  38. 38. Code Review
  39. 39. Chef Delivery TODO’s • Everything • We do have a demo version for the next 2 weeks.
  40. 40. Why is this important??
  41. 41. Address slow innovation adoption From time new knowledge discovered until ½ of physicians act on that knowledge = 15 - 17 years Everett Rogers, Diffusion of Innovations, 1995 Balas, Boren. Managing Clinical Knowledge for Health Care Improvement. Yearbook of Medical Informatics 2000 %ofpopulation Time Adoption Half-life = 17y Knowledge Half-life = 10y “Finish medical school and residency knowing everything…read and retain 2 articles every single night…at the end of 1 year you’re only 1,225 years behind.” W Stead. JAMIA 2005;12:113-20 Alper BS, Hand JA, ElliottSG, et al. J Med Lib Assoc 2004;92:429-37
  42. 42. Can this actually be done?
  43. 43. If we delivery faster so what?
  44. 44. How far along are we? • From October (7 months ago) – Continuous Delivery: What Do We Need to Get There - October 2014 Meetup – https://connect.ucern.com/videos/26267 • Status – https://connect.ucern.com/docs/DOC-390893
  45. 45. Continuous Delivery Tool Roll Out test-kitchen Chef Push Jobs rake deploy kitchen test knife push Project Project.yml Kitchen.yml Chef roles
  46. 46. Science Says: Command and Control… … does not lead to Success Culture can … … radically change in positive ways 1. Culture
  47. 47. DevOps means? • DevOps != Devs In Production • DevOps == Few, if anyone In Production • DevOps != Manual steps • DevOps == Automate to achieve quality 2. Workflow
  48. 48. Patient but Persistent It’s worth it • HP  18 months to build continuous delivery • Microsoft  10 years to build continuous delivery 3. Tooling
  49. 49. http://cote.io/blog/the-emerging-market-in-devops-451-researchs-q1?source=old_url

×