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.

ChefConf 2015 Cleaning up the Kitchen

437 views

Published on

Presentation from ChefConf 2015 on the journey we have taken with Chef at Cerner Corporation.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

ChefConf 2015 Cleaning up the Kitchen

  1. 1. Cleaning up the Kitchen
  2. 2. Cleaning up the Kitchen@ablythe
  3. 3. Lessons • Be Patient/Be Hungry • Look outward – Ask Community – Ask Chef • You can’t please all the people • Know your constraints and work within them @ablythe
  4. 4. Recommendations • Have a focused team - Configuration Management does not just happen • Focus on the Workflow • Incent your community to work together • Define how your collective organization should use roles/environments/data bags • Educate!! • Involve Your Friends at Chef @ablythe
  5. 5. http://www.slideshare.net/AaronBlythe/ @ablythe
  6. 6. Aaron Blythe @ablythe http://www.meetup.com/DevOps-Kansas-City/
  7. 7. Founded in 1979
  8. 8. 2011 2012 2014 20152013 Journey With @ablythe
  9. 9. 2011 2012 2014 20152013 @ablythe
  10. 10. 2011 2014 20152013 2012 @ablythe
  11. 11. http://www.pxleyes.com/photography-picture/50ccc14f7f012/Fork-Off.html @ablythe
  12. 12. @ablythe
  13. 13. ON @ablythe
  14. 14. January 2012 – Late March 2012 @ablythe
  15. 15. 2011 2012 2014 2015 2013 We 50+ @ablythe
  16. 16. Which Chef Server? What is the admin password? How is this being backed up? Where did this cookbook come from? Is this the original cookbook or a fork? Why is this in production, but not in Staging? Is this wiki page up to date with which Server to connect to? Can we double bootstrap it? @ablythe
  17. 17. @ablythe
  18. 18. @ablythe
  19. 19. • Value Proposition of Chef: – Infrastructure as Code • Repeatable/Testable Deployments • Consistency - Staging Like Production @ablythe
  20. 20. In Kansas City… One Night Only • http://www.meetup.com/DevOps-Kansas-City/ Adam Jacob!! @ablythe
  21. 21. Later that week… OpsInfra @ablythe
  22. 22. Later that Month… "I have never been in a room with that many system engineers that were all smiling, almost giddy. It was as if we all knew a secret." @ablythe
  23. 23. @ablythe
  24. 24. Paul Edelhertz - Interview • Senior VP Customer Ops – Chef • Former CEO – Empath, Inc. (bought by Navigant) @ablythe
  25. 25. Paul Edelhertz - Interview • Ability to persuade through writing is becoming a lost art – Make the message short – State exactly how I feel – Different mediums but repeat the message over and over to many people @ablythe
  26. 26. Chef – “The List” • Fuel the love of Chef • Make it easy to be successful • Give organizations reasons to buy • Be their favorite company to work with • Speed matters, be disruptive @ablythe
  27. 27. We Believe… • A minimal number of associates need to directly touch nodes (approaching zero) • These tools matter – improve the lives of our users • • Tools should be hardened - so that we can find the root cause and drive corrective action @ablythe
  28. 28. Identity • Tools Team • Culture Team @ablythe
  29. 29. @ablythe
  30. 30. @ablythe
  31. 31. @ablythe
  32. 32. Workflow Step 1: Source Code Step 2: ????? Step 3: Production (Profit!!!) @ablythe
  33. 33. @ablythe
  34. 34. @ablythe
  35. 35. @ablythe
  36. 36. RFC’s @ablythe
  37. 37. Conway’s Law – Educate who you need to 2 classes * 15 attendess * Re-delivering to 15-30/month * Over 1 year __________________ 200+ https://learn.chef.io/index.html @ablythe
  38. 38. $20/Class @ablythe
  39. 39. 2011 2012 20152013 2014 Provide the Platform @ablythe
  40. 40. Migration Workshop • 1st rule of teaching: – Control all variables other than the concept you are focusing on @ablythe
  41. 41. Current State of Cookbooks • https://wiki.ucern.com/display/ChefEcosystem/Booksh elf • 129 Cookbooks listed – 87% of cookbooks have a metadata.rb. (112/129) – 79% of cookbooks have a cookbooks folder (102/129) – 56% of cookbooks have a Rakefile. (72/129) – 33% of cookbooks have a Berksfile. (42/129) – 30% of cookbooks have a Vagrantfile. (39/129) – 24% of cookbooks have a pom.xml. (31/129) @ablythe
  42. 42. Good Migrations @ablythe
  43. 43. Success Engineer @ablythe
  44. 44. Stephen Lauck “Usually I show up and I am helping companies go from 0 to 20. You are clearly going from 40 to 60. Keep me in the loop, because I want to continue to be part of your success. We all know the companies that will be able to move fast will be the companies that remain successful in the market.” @ablythe
  45. 45. • Push Jobs • Analytics • OpenStack • SuperMarket @ablythe
  46. 46. Push Jobs • Value: Orchestration • Review: Overall positive, have-to-have feature for most of our teams • Drawbacks: Push Jobs 1.x is not very mature or feature rich. We have seen issues with Networking. @ablythe
  47. 47. Analytics • Value: Compliance/Auditing for non-coders • Review: Interesting need to see latest version. We get asked about creating this functionality regularly… Future features look promising. • Drawbacks: Early versions search slightly confusing. Filtering was not working right so very busy. @ablythe
  48. 48. OpenStack Integration • Decision (At this point): Heat Templates • Still really want to see chef-provisioning mature @ablythe
  49. 49. SuperMarket • Value: Helps lock down our pipeline • Review: Decided that we need a better pipeline first. • Drawbacks: Early on was not ready for RHEL, hacked something together, but need to revisit. Authorization model not there for an Enterprise (CCLA not applicable). @ablythe
  50. 50. 2011 2012 2014 2015 2013 March toward Continuous Integration/ Continuous Delivery@ablythe
  51. 51. Where are we now? • We are at about the 1 year mark of a focused well oiled system • Have over 3000 Chef nodes involved with 100’s of separate systems/sub-systems • Over 400 user accounts created on the server @ablythe
  52. 52. Wat ta do about CD? • Jenkins – Workflow Plugin • Go.cd • Chef Delivery • All the wonderful things we have seen at the booths here @ablythe
  53. 53. Blocker – Sensitive Flag user 'zabbix' do shell '/sbin/nologin' comment 'Zabbix Monitoring System' supports manage_home: true node.run_state['zabbix_password'] = SecureRandom.base64(36) password node.run_state['zabbix_password'] gid 'zabbix' unless platform_family?('windows') sensitive true action [:create, :lock] end end @ablythe
  54. 54. Centralized vs. Decentralized @ablythe
  55. 55. Open Source • 6 associates contribute to core Chef • Another 15 or so contribute to Cookbooks in SuperMarket @ablythe
  56. 56. 2011 2012 2014 20152013 Journey With @ablythe
  57. 57. Lessons • Be Patient/Be Hungry • Look outward – Ask Community – Ask Chef • You can’t please all the people • Know your constraints and work within them @ablythe
  58. 58. Recommendations • Have a focused team - Configuration Management does not just happen • Focus on the Workflow • Incent your community to work together • Define how your collective organization should use roles/environments/data bags • Educate!! • Involve Your Friends at Chef @ablythe
  59. 59. What do you think? @ablythe aaron.blythe@gmail.com http://www.slideshare.net/AaronBlythe/ Community room next session 3-4PM @ablythe

×