Chef and Rails, our story

A little story about how we use Chef and Rails for our custom controlpanel.

Transcript

1. Chef + Rails for customer cloud control zondag 7 april 13
2. Joren dev Steven ops zondag 7 april 13
3. Openminds zondag 7 april 13
4. How it used to be • ./post_install.sh • openminds gem • rackup omd.rb • data push to Sock zondag 7 april 13
5. • Idempotence • Time consuming • Direct control • Special snowflakes Implications for us zondag 7 april 13
6. for customers • no fixed solution: special snowflakes • one-way traffic to Sock • not a real control panel zondag 7 april 13
7. starting with chef zondag 7 april 13
8. Why Chef zondag 7 april 13
9. Why Chef zondag 7 april 13
10. First steps • ./post_install.sh zondag 7 april 13
11. LAMP Chef Server A M P VPS x zondag 7 april 13
12. Initial Issues • not always reusable • no why-run zondag 7 april 13
13. Version management • don’t break old stuff • no major upgrades • wrapper recipe • new version == new recipe zondag 7 april 13
14. MySQL::default zondag 7 april 13
15. Version management Library cookbook Wrapper cookbook zondag 7 april 13
16. Version management Library cookbook Sock (cookbook) zondag 7 april 13
17. Sock B.C. • one-way traffic • not a real control panel • time consuming for us zondag 7 april 13
18. Sock A.C. • two-way traffic • real control panel • client in control zondag 7 april 13
19. How Clients Sock Chef node(s) Openminds zondag 7 april 13
20. Provisioning Sock zondag 7 april 13
21. Provisioning Sock zondag 7 april 13
22. Provisioning Sock zondag 7 april 13
23. Sock provisions Chef zondag 7 april 13
24. Chef handling our JSON • Light-Weight Resource and Providers • Actions: create, update, delete, lock, move, ... zondag 7 april 13
25. Chef handling our JSON zondag 7 april 13
26. Chef handling our JSON zondag 7 april 13
27. Breaking stuff • Cache invalidation • Naming things • Git usage; working in a team • “but it worked on my Vagrant...” zondag 7 april 13
28. Sandbox Environment • We still use Vagrant <3 • Mimics Production Environment • Detailed monitoring zondag 7 april 13
29. Automated testing • Jenkins • Functional tests • Integration tests zondag 7 april 13
30. Knife test zondag 7 april 13
31. Knife test Food critic zondag 7 april 13
32. Knife test Food critic zondag 7 april 13
33. Xen node a node b node c zondag 7 april 13
34. Xen node a node b node c Integration tests } zondag 7 april 13
35. zondag 7 april 13
36. Le Future • we’re agile, we don’t plan the future • chef-sock all the things, all the time • better queueing and reporting zondag 7 april 13
37. Le Future zondag 7 april 13
38. Thank you. joren Zhann zondag 7 april 13