Chef Infrastructure as a Code

Agendal

Agenda

l Why chef ?

l Basics of Chef

l Demo

l Question?

Why chef ?

• Manual system administration

• Non-repeatable

• No version control

• Takes too long

Install, configure & control

... servers in your sleep

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.

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

Chef - IaaC

- Programmatically provision and configure

- Treat like any other code base

- Reconstruct business from code repository, data backup, and bare metal resources.

Chef - IaaC

Knife

Cookbook

- Fundamental unit of configuration

- Cookbooks contain recipes, templates, files, custom resources, etc

- Code re-use and modularity

- Hundreds already onCommunity.opscode.com

Cookbook

l recipes - list of instructions l attributes - variablesl definitions - macros of resourcesl files - files used by resourcesl libraries - Ruby to extend Chef DSLl metadata.rb l templates - ERB templates

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

DEMO

Hosted Chef

- Sign up for Opscode Hosted Chef - https://community.opscode.com/

- Create an Organization

thanks~