Moving Data Centers is Scary, Make it Less Scary with Chef!

"You should never rewrite your whole application" is a common bit of wisdom in the programming world. But what about rebuilding your entire data center and application on a new platform? The Behance Team at Adobe decided to move from the comfortable world of a physical data center to "The Cloud". We decided that adopting Chef was the only way to make this happen. In this talk you'll hear how the Ops and Quality Engineering teams joined forces to convert bash scripts - and the bash mentality - to Chef. We'll talk about the decision making process and some of the pitfalls we encountered. We will go in to detail on how we use Chef to build our development, QE, and staging environments so that the entire development team can dogfood our cookbooks before they reach production.

Transcript

1. #CHEFCONF2014
2. MOVING DATA CENTERS IS SCARY, MAKE IT LESS SCARY WITH CHEF! ! U-HAUL NOT INCLUDED. // MANNY TOLEDO @MTLDO // CHRIS FORTIER @CFORTIER https://flic.kr/p/5mj9gS
3. CHALLENGE
4. WHAT IS BEHANCE? The leading online platform to showcase & discover creative work. The creative world updates their work in one place to broadcast it widely and efficiently. Companies explore the work and access talent on a global scale.
7. THE BODEGA Everything except the (test) kitchen sink
8. https://flic.kr/p/bmjLbd
9. BC = BEFORE CHEF
11. USE CHEF TO RUN A BASH SCRIPT? PLEASE DON’T
12. THE NEW (CHEF) WAY
13. THE BIG MOVE Moving from Rackspace to AWS.
14. FROM PHYSICAL TO A CLOUD http://bit.ly/cWtLwX http://bit.ly/1jsea9G
15. THE QEOPS TEAM Sounds suspiciously like “DevOps”. It’s what happens when QE and Ops work together on the same project.
16. OPS QE
17. It takes a family of three to care for a single puppy, but a few cowboys can drive tens of thousands of cows over great distances. “ ” —Joshua McKenty, CTO of Piston Cloud
18. Need to maintain current infrastructure Need to build new products in AWS Need to migrate current infrastructure Need Development and QE environments ONE SET OF COOKBOOKS FOR ALL
19. PROTIP: ! Everyone needs to sit together.
20. WHY CHEF? IT’S DELIGHTFUL !
21. DOGFOODING THE COOKBOOKS Cookbooks tested on Bodegas. Everyday.
22. CHEF-CLIENT EVERYDAY = RAINBOWS AND UNICORNS. RIGHT?
23. CHEF-CLIENT EVERYDAY != RAINBOWS AND UNICORNS
24. ! Know your versions Dedicated repo mirrors Control dependencies CONTROL ALL THE THINGS
25. DOGFOOD ALL THE QE INSTANCES
26. MULTIPLE LOCATIONS How does it work in multiple locations?
27. Global Namspace for attributes node['be']['location']
28. Test-Suite Samples suites: - name: bodega-stage-aws-php55 provisioner: client_rb: environment: "stage-aws" run_list: - recipe[bebootstrap::default] - recipe[bebodega::default] attributes: authorization: sudo: users: [ "jenkins" ] be: location: "aws" php: version: "5.5" bedatadog: apache: true mondo: true mysql: true suites: - name: bodega-stage-rax-php54 provisioner: client_rb: environment: "stage-aws" run_list: - recipe[bebootstrap::default] - recipe[bebodega::default] attributes: authorization: sudo: users: [ "jenkins" ] be: location: "rax" php: version: "5.4" bedatadog: apache: true mondo: true mysql: true
29. I need new hotness for development! “ ” —RANDOM DEVELOPER Yeah, we can make it happen. “ ” —OPERATIONS
30. CHEF GATEKEEPER ATTRIBUTES BEPHP::DEFAULT RECIPE BEPHP::DEFAULT ATTRIBUTE BEPHP::BEPHP55 ATTRIBUTE
31. WORKFLOW AND TESTING PIPELINE Jenkins for the win!
32. GITHUB SERVERSPEC CHEFSPEC JENKINS KNIFE-SPORK BERKSHELF RUBOCOP FOODCRITIC TESTKITCHEN MERGEATRON
33. TESTS JENKINS MERGEATRON PULL REQUEST GITHUB
34. ONLY JENKINS PUSHES COOKBOOKS
35. I CAN TEST ON MY LAPTOP
36. PROTIP: ! Try testing at 30,000 feet
37. CHEF TEST MONITORING
38. WHAT IS OUR PROCESS All the process.
39. ! Code wins arguments Chef is idempotent, your cookbooks might not be Treat servers as ephemeral Lock environments
40. OBLIGATORY: OF COURSE WE’RE HIRING!
41. THANK YOU! MANNY TOLEDO // @MTLDO CHRIS FORTIER // @CFORTIER Speaker Hours: ! Right now. In the Marina Room.