Chef is an infrastructure automation tool that allows users to define and maintain server configurations. It uses recipes, resources, cookbooks and roles to provision and configure servers. Chef works by installing a Chef client on nodes that runs recipes to configure the node according to cookbooks. The Chef server stores cookbooks and node data. Users can write recipes in Ruby syntax to define what configuration should be applied to nodes.

1. ChefInfrastructure as code

2. Chef

3. Background Opscode (HJK Solutions)

4. Chef has Recipes Resources Roles Nodes Cookbooks Knife

5. Fully Automated Infrastructure

6. Provisioning Bare-metal: Kickstart/jumpstart VM: libvert Cloud: AWS/vCloud Cloud: fog (http://fog.io/)

7. Configuration Management

8. Systems Integration the last mile of fully automated infrastructure Metadata stored & indexed Search API

9. Chef principles Idempotent Thick Clients, Thin Server Order Matters

10. Why chef? Economics Efficiency Scalability Community

11. Flavors of Chef Chef client & Chef server Hosted Chef Chef solo

12. Architecture

14. A Chef run

16. Chef client Client does all the work, and can run recipes for multiple Nodes.

17. Chef server API service. Management Console (optional). AMQP Server Search indexer and Search Engine. Data store with CouchDB.

18. Chef solo -c, --config CONFIG -j, --json-attributes JSON_ATTRIBS -r, --recipe-url RECIPE_URL

19. Cookbook

20. Cookbook Cookbooks are the fundamental units of distribution in Chef.

21. Cookbook attributes/ definitions/ files/ libraries/ metadata.rb providers/ recipes/ resources/ templates/

22. Cookbook Dev in chef-repo Create our own cookbook Or download from community Upload to Chef server

23. Cookbook command knife cookbook list knife cookbook create COOKBOOK knife cookbook download COOKBOOK knife cookbook upload [COOKBOOKS...] knife cookbook delete COOKBOOK knife cookbook metadata COOKBOOK

24. Chef Community Cookbook Site knife cookbook site list knife cookbook site share COOKBOOK CATEGORY knife cookbook site install COOKBOOK knife cookbook site unshare COOKBOOK knife cookbook site search QUERY knife cookbook site download COOKBOOK

25. Cookbook Dependencies In metadata.rb: depends "apache2", ">= 0.99.4" depends "mysql", ">= 1.0.5"

26. Attributes node.default[:apache][:dir] = "/etc/apache2" node.default[:apache][:listen_ports] = [ "80", "443" ] if node.apache.attribute?(”dir") # do something end

27. Nodes Nodes in Chef are the thing that are configured by Recipes. recipe/role attribute

28. Roles name "webserver" description "The base role for systems that serve HTTP traffic" run_list "recipe[apache2]", "recipe[apache2::mod_ssl]", "role[monitor]" env_run_lists "prod" => ["recipe[apache2]"], "staging" => ["recipe[apache2::staging]"] default_attributes "apache2" => { "listen_ports" => [ "80", "443" ] } override_attributes "apache2" => { "max_children" => "50" }

29. Search knife search node "id:foo OR id:abc” search(:node, 'run_list:recipefoobar') do |matching_node| puts matching_node.to_s end

30. Libraries your_cookbook/libraries/your_example_library.rb module YourExampleLibrary def your_function() # ... do something useful end End your_cookbook/recipes/default.rb class Chef::Recipe include YourExampleLibrary end your_function()

31. Metadata maintainter "bob" maintainer_email "bob@gmail.com" license "Apache v2.0" description "A cookbook" long_description "blablabla" depends "mysql", ">= 1.0.1" version "2.0.1" recipe "A recipe", "blablabla"

32. Templates template "/etc/sudoers" do source "sudoers.erb" mode 0440 owner "root" group "root" variables( :sudoers_groups => node[:authorization][:sudo][:groups], :sudoers_users => node[:authorization][:sudo][:users] ) end

33. Recipes stored in Cookbooks. executed in the order they appear. evaluated as Ruby code. Recipes from other Cookbooks can be included with include_recipe. All the attributes of the current Node are available via the node object.

34. Resources such as: packages services users files directories

35. Resources: cookbook_file cookbook_file "/tmp/testfile" do source "testfile" # this is the value that would be inferred from the path parameter mode "0644" end

36. Resources: directory %w{dir1 dir2 dir3}.each do |dir| directory "/tmp/mydirs/#{dir}" do mode 0775 owner "root" group "root" action :create recursive true end end

37. Resources: remote file remote_file "/tmp/testfile" do source "http://www.example.com/tempfiles/testfile" mode "0644" checksum "08da002l" # A SHA256 (or portion thereof) of the file. end

38. Resources: package package "tar" do version "1.16.1-1" action :install end

39. Resources: script script "install_something" do interpreter "bash" user "root" cwd "/tmp" code <<-EOH wget http://www.example.com/tarball.tar.gz tar -zxftarball.tar.gz cdtarball ./configure make make install EOH end

40. Quick start

42. Local workstation(MaxOSX)

47. Verify node data List all the node: knife node list List the run list for a specific node: knife node show nodename –r

48. Working with git

49. get chef-repo git clone git://github.com/opscode/chef-repo.git

50. repo tree config/ - Contains the Rake configuration file, rake.rb. cookbooks/ - Cookbooks you download or create. data_bags/ - Store data bags and items in .json in the repository. roles/ - Store roles in .rb or .json in the repository. certificates/ - SSL certificates generated by rake ssl_cert live here.

51. working with git Building a new cookbook and saving it to the local repository. Downloading an existing cookbook from the Chef Community Site. Modifying an existing cookbook in the local repository for new updates.

52. Doc & Help

53. working with git wik: http://wiki.opscode.com/display/chef/Home community: http://community.opscode.com/cookbooks

54. Q&A thanks~