Chef is an open-source tool for automating configuration management and infrastructure as code, developed by Opscode, enabling companies to manage changing infrastructures efficiently. It consists of components like workstations, servers, and nodes, where cookbooks are created and utilized to ensure continuous deployment and system robustness. The document also outlines the benefits of using Chef, including its adaptability to cloud environments and the types of Chef architectures available, such as Chef Solo and Hosted Chef.

2. What’s in it for you?
Chef demo
Chef architecture
Why use Chef?
What is Chef?
Configuration Management
Components of Chef
Infrastructure as Code
Flavours of Chef

3. Why use Chef?

4. Large companies have a constantly changing
infrastructure that requires to be configured and
maintained time to time
Why use Chef?

5. Large companies have a constantly changing
infrastructure that requires to be configured and
maintained time to time
Why use Chef?
New nodes may get added
Existing systems may fail

6. Large companies have a constantly changing
infrastructure that requires to be configured and
maintained time to time
Why use Chef?
New nodes may get added
Existing systems may fail
I can’t do it all by myself..

7. Large companies have a constantly changing
infrastructure that requires to be configured and
maintained time to time
Why use Chef?
This is where Chef comes in and automates the entire
process

8. Continuous deployment:
-Software is deployed continuously enabling a company to keep in
pace with the market requirements
Why use Chef?
Chef provides:

9. Continuous deployment:
-Software is deployed continuously enabling a company to keep in
pace with the market requirements
Increase system robustness:
-Infrastructure automation ensures all bugs are caught and removed
before deploying the software
Why use Chef?
Chef provides:

10. Continuous deployment:
-Software is deployed continuously enabling a company to keep in
pace with the market requirements
Increase system robustness:
-Infrastructure automation ensures all bugs are caught and removed
before deploying the software
Adapt to the Cloud:
-Chef easily integrates with infrastructure on cloud
Why use Chef?
Chef provides:

11. What is Chef?

12. Chef is an open source tool developed by OpsCode
What is Chef?

13. Chef is an open source tool developed by OpsCode
What is Chef?
It is written in Ruby and Erlang

14. Chef is an open source tool developed by OpsCode
It is written in Ruby and Erlang
It automates configuration and maintenance of multiple servers
What is Chef?

15. Configuration Management

16. Configuration Management
Configuration management is a collection of engineering practices that provides a systematic
way to manage entities for efficient deployment.These entities include

17. Code Infrastructure people
Configuration Management
Configuration management is a collection of engineering practices that provides a systematic
way to manage entities for efficient deployment.These entities include

18. Code Infrastructure people
Configuration Management
Code needs to be
updated and stored
Infrastructure needs to
be configured
People need
coordination

19. Configuration Management
A configuration management tool automates these activities. There are two
types of configuration management
Server Server

20. Configuration Management
Chef follows pull configuration
Server Server

21. Infrastructure as code

22. Infrastructure as code
This isTim. He’s working at a large scale company as a system
administrator

23. Infrastructure as code
I must set up a server and install 20
software applications over it

24. Infrastructure as code
I must set up a server and install 20
software applications over it
Server is set up

25. Infrastructure as code
I must set up a server and install 20
software applications over it
Server is set up
It will take me all night to install all 20
software applications though

26. Infrastructure as code
Server is set up
This wouldn’t be the case if i had a code for installing all
the software rather than doing it manually
I must set up a server and install 20
software applications over it
It will take me all night to install all 20
software applications though

27. Infrastructure as code
modified
tested
deployed
I could modify the code to meet the software
installation requirements

28. Infrastructure as code
modified
tested
deployed
Code could be tested to catch any bugs

29. Infrastructure as code
modified
tested
deployed
Code can be easily deployed and all
installations would take place automatically

30. Infrastructure as code
Policies and configurations Code
written as
This makes configuration management simpler and
more efficient
Infrastructure as code is a type of it infrastructure where the operations
team manages the code rather than a manual procedure

31. Components of Chef

32. workstation
The code for configuring and managing the infrastructure is
created here
Knife is a command line tool that uploads the cookbook to the server
Components of Chef

33. SERVER
The server is where the Cookbooks are stored
It provides tools required to drive the node configurations
Server may be hosted local or remote
The server is the middle man between workstation and the nodes
Components of Chef

34. node
Ohai fetches the current state of the node it’s located in
Chef client is responsible for the communication with the server
Each node can have a different configuration requirement
Nodes are the systems that require the configuration
Components of Chef

35. Chef architecture

36. Recipes are created at the workstation
Chef architecture
Template ‘etc/simplilearn’ do
source ‘simplilearn1.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Recipes
workstation SERVER
node
node

37. Recipes are created at the workstation
Chef architecture
workstation SERVER
node
node
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn2.erb’
owner ‘root’
group ‘root’
mode ‘0655’
end
Recipes

38. Chef architecture
Collection of recipes forms a cookbook
workstation SERVER
node
node
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn2.erb’
owner ‘root’
group ‘root’
mode ‘0655’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Recipes

39. The Cookbook is uploaded to the server using the knife
Chef architecture
workstation SERVER
node
nodeKnife
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn2.erb’
owner ‘root’
group ‘root’
mode ‘0655’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Recipes

40. The Cookbook is uploaded to the server using the knife
Chef architecture
workstation
Knife
SERVER
node
node
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn2.erb’
owner ‘root’
group ‘root’
mode ‘0655’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Recipes
$ knife upload simpli-db

41. Ohai, a component of the node checks the system’s
state and sends it to the chef client
Chef architecture
ohai
workstation
ohai
Knife
SERVER
node
node
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn2.erb’
owner ‘root’
group ‘root’
mode ‘0655’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Recipes
$ knife upload simpli-db

42. Chef architecture
$ chef-client
The chef client ensures that the node’s state is
consistent with the cookbook
ohai
workstation
ohai
Knife
SERVER
node
node
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn2.erb’
owner ‘root’
group ‘root’
mode ‘0655’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Recipes
$ knife upload simpli-db

43. Chef architecture
If not, the client pulls the cookbook from the server
ohai
workstation
ohai
Knife
SERVER
node
node
$ chef-client
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn2.erb’
owner ‘root’
group ‘root’
mode ‘0655’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Recipes
$ knife upload simpli-db

44. Chef architecture
The node then configures itself with respect to the
cookbook to the right state
ohai
workstation
ohai
Knife
SERVER
node
node
$ chef-client
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn2.erb’
owner ‘root’
group ‘root’
mode ‘0655’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Recipes
$ knife upload simpli-db

45. Chef architecture
The node then configures itself with respect to the
cookbook to the right state
ohai
workstation
ohai
Knife
SERVER
node
node
$ chef-client
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn2.erb’
owner ‘root’
group ‘root’
mode ‘0655’
end
Template ‘etc/simplilearn’ do
source ‘simplilearn3.erb’
owner ‘root’
group ‘root’
mode ‘0755’
end
Recipes
$ knife upload simpli-db

46. Flavours of Chef

47. Chef solo has no remote server.The cookbooks are located at the local site itself
Chef server is provided as a service on the cloud.Thus, there is no need to setup a
server yourselfHosted chef
Flavours of Chef
workstation
server
Node
Chef solo

48. Chef client/server
This is the traditional chef architecture where a remote server is hosted that
communicates between workstation and node
Flavours of Chef
workstation server
workstation server node
node
private chef
This is the enterprise version of chef where the server is hosted within the
enterprise infrastructure

49. Chef demo

50. Chef demo
Workstation – CentOS 7 Server - Cloud Service Node - CentOS 7

51. Chef demo
Download and install Chefdk
on workstation
Make a cookbook and write
the recipe
Set up the server
Link the workstation and upload
the recipe to the server
Configure the node

52. Key Takeaways
Why use chef? What is chef?
Infrastructure as codeConfiguration management

53. Key Takeaways
Components of chef architecture of chef
Chef demoFlavours of chef