Chef is a configuration management framework that allows infrastructure to be described in code. It uses nodes, code, and data to configure, deploy, and manage applications across infrastructure. Nodes contain attributes and a run list of configuration steps. Code is written in recipes and cookbooks to manage common resources like installing software or configuring servers. Data bags store searchable JSON data. Chef brings benefits like version controlling infrastructure code, reusable configuration across environments, and testable infrastructure definitions.

1. CHEF
A Meme filled Overview

2. WHAT IS CHEF?

3. IT’S NOT HIM!
It’s A Configuration
Management Framework

4. WHAT’S A CONFIGURATION
MANAGEMENT FRAMEWORK?
• Software that allows us to write code that:
• describes our infrastructure
• automates how applications are configured,
deployed and managed

5. WHAT’S AN INFRASTRUCTURE?
everything that supports the flow and processing of
information

6. WHAT ARETHE COMPONENTS?
Nodes, Code and Data

7. THE NODE
usually just a server
has attributes
and a run list

8. OHAI ATTRIBUTES!

9. ATTRIBUTES
Defined via code, overridable

10. RUN LIST!
All of the configuration
necessary to put a node in
the desired state.
• “Install Java”
• “Configure the web server”
• “Configure the database”
• “Configure the firewall”

11. THE CODE
Written in recipes which are
collected in cookbooks

12. DOMAIN SPECIFIC
LANGUAGE
• A programing language
dedicated to a particular
aspect of a system
• Ruby syntax
• “Resources” provided to
manage common things

13. EXTENSIBLE
we can write our own
resources and extend the
DSL

14. IDEMPOTENT
operations that can be
applied multiple times without
changing the result beyond
the initial application

15. THE DATA
data bags

16. DATA BAGS
searchable, JSON format, encryption

17. WHAT ARE SOME BENEFITS
OF CHEF?
• Same code used to
configure all environments
• Infrastructure is version
controlled like your apps
• Infrastructure code is
testable

18. REUSABLE CODE

19. WHAT HAVE WE DONE SO
FAR?
• Repository to store our built
artifacts and 3rd party
dependencies
• Automate the backup of our
databases
• Automate the service
wrapper that all of our apps
use
• More in progress