Current Status: Chef (Presented at Denver/Boulder Cloud Meetup)

These are the slides I used for the Chef presentation at the Denver/Boulder Cloud meetup on 5/24/2012. For more comprehensive details on the upcoming features of Chef, see Chris Brown's talk from ChefConf:

http://www.youtube.com/watch?v=Lv89JG81-9M&feature=plcp

Transcript

1. Current Status: Chef Joshua Timberman Technical Program Manager joshua@opscode.com
2. Chef 0.10.10 Faster release cycle, coming soon: Chef 0.10.12!
3. Chef 0.10.0 • Environments • Encrypted Data Bags • Knife Plugins • Windows Support
4. Full Stack Installers
5. Clients • /opt/chef • Ruby 1.9 • Includes the most common knife plugins • Native packaging formats • A single command to install
6. curl -L http://opscode.com/chef/install.sh | sudo bash
7. Chef Clients • Ubuntu 10.04, 11.04, 11.10, 12.04 • Red Hat Enterprise Linux 5, 6 (plus derivatives) • Debian Stable • Windows 2003R2, 2008 • Solaris 9+ (on x86 and SPARC) • You can help us add more!
8. Open Source Chef Server • Single package • /opt/chef-server • Single configuration file • chef-server-ctl • Service management • Single-configuration file
9. Private Chef • Single package • /opt/opscode • Single configuration file for the entire infrastructure • private-chef-ctl • Service control • Built-in testing • High Availability
10. Full Stack Installers • omnibus-ruby • omnibus-software • omnibus-chef • omnibus-your-project?
11. Providers and Resources • Providers are state machines that move Resources from "current" to "desired" states by taking a default or user-selected action. • "Why-run" and Reporting both benefit from knowing and comparing these states.
13. What you get... • Serial and complete analysis of prerequisites defined in recipes • best effort in state differences • clear indications of what actions would be taken and why at a useful level of abstraction
14. What you don't get... • Cannot ensure complete safety in "why-run" or during a real run • Cannot meet "hidden" expectations • Environment at time of "why-run" may differ greatly from actual run time • No "free" implementation in user- written providers
17. Output Formatters
19. Exception!
21. Primitives for Reporting • Report/exception handlers • Output formatters • "Why-run"* • APIs and services
22. Opscode Private Chef
23. Private Chef • Supported, behind your firewall Chef Server. • HA capable. • Simple installation. • Enterprise class.
24. Community
25. May 16-18 http://youtube.com/user/opscode
26. Community Events • Workshops, Training • Hack days • User groups • Conferences • ChefConf
27. Chef is Open Source • Apache v2 Software License • Over 720 individuals, 130 companies • Chef, Ohai, Cookbooks, and dozens of software projects (plugins, mixlibs and more)
28. community.opscode.com
29. Cookbooks
30. Development Release
31. Cookbooks • Support • Testing (minitest, rspec, cucumber) • Linting (foodcritic) • LWRPs and Libaries
32. Application Deployment... application "myapp" do path "/opt/myapp" repository "git://github.com/myapp/myapp.git" revision "2.0-stable" packages ["build-essential", "git"] rails do gems ["bundler","passenger"] database do database "myapp" username "myapp" password "awesome_password" end database_master_role "myapp_database_master" end passenger_apache2 do server_aliases ["myapp", "myapp.#{node['domain']}"] end end
33. Application deployment • Ruby • Python • Php • Java
34. Heartbeat Configuration... heartbeat "heartbeat" do auto_failback true autojoin "other" search node['heartbeat']['config']['search'] authkeys "your favorite authkey" interface "eth0" resources "192.168.17.100" end
35. Staying updated • http://opscode.com/blog • http://lists.opscode.com • http://twitter.com/opscode
36. Questions? We're hiring! opscode.com/careers Joshua Timberman @jtimberman joshua@opscode.com #opschef