The document discusses Chef, an infrastructure as code framework that automates system and cloud management. It highlights its benefits over manual administration, including version control, ease of use, and modularity through cookbooks and recipes. The presentation includes an overview of Chef's architecture, its components, and a demonstration of its capabilities.

1. Chef
Infrastructure as a Code

2. Agenda
l
Agenda
l
Why chef ?
l
Basics of Chef
l
Demo
l
Question?

3. Why chef ?
• Manual system administration
• Non-repeatable
• No version control
• Takes too long

4. Install,
configure
& control
... servers in your sleep

5. Chef
Chef is
a system and cloud infrastructure
automation framework.
You define recipes of how you
want your system to look and
then chef makes it so.

6. Chef
• Client-server architecture
• Embraces modern web technologies
• Best ideas from cfengine and Puppet
• Targeted to Linux, Solaris, Window, Mac OS
• Written in Ruby, recipes in Ruby

7. Chef - IaaC
- Programmatically provision and configure
- Treat like any other code base
- Reconstruct business from code repository,
data backup, and bare metal resources.

8. Chef - IaaC

9. Knife

10. Cookbook
- Fundamental unit of configuration
- Cookbooks contain recipes, templates, files,
custom resources, etc
- Code re-use and modularity
- Hundreds already on
Community.opscode.com

11. Cookbook
l recipes - list of instructions
l attributes - variables
l definitions - macros of resources
l files - files used by resources
l libraries - Ruby to extend Chef DSL
l metadata.rb
l templates - ERB templates

12. Node
• Chef-Client generates configuration Directly on
nodes from their run list
• Reduce management complexity through abstraction
• Store the configuration of your programs in version
control

13. DEMO

14. Hosted Chef
- Sign up for Opscode Hosted Chef
- https://community.opscode.com/
- Create an Organization

15. thanks~