How to Avoid a Chef Horror Show

Anna Fowles-Winkler Software Developer

Oracle @flexlingie

http://tinyurl.com/q94ulrp

3 Environments Development, Staging, Production

2 Different Networks 2 Chef Servers

One for dev/staging and one for production

http://tinyurl.com/p763wx5

Dev ~25 servers

Staging ~70 servers

Production > 500 servers

http://tinyurl.com/myke7om

http://tinyurl.com/k58p54b

http://tinyurl.com/k6daae5

Breathe

http://tinyurl.com/mbegds6

production, staging, all of your environments;

plan your attributes.

consistency wins for names of things and objects.

it’s a new season.

http://tinyurl.com/qhthoxt

http://tinyurl.com/px8ce4f

Chef cookbooks of mine must not be special snowflakes

across environs.

http://tinyurl.com/ox8cv7s

http://tinyurl.com/owyxnn7

Idempotent

http://tinyurl.com/pl43mle

http://tinyurl.com/pk6qsw5

a recipe small, focused on an element;

the server lives on.

http://tinyurl.com/kaveqkl

Will this work?

http://tinyurl.com/o36h2rv

Gatekeepers

http://tinyurl.com/maevge3

Communicate

This brings us to the big question.

Plan Consistent Names

Auto-update Chef Server Use Roles

Idempotent Cookbooks Test

Gatekeepers

Witness the changes, Trust automation with Chef.

The sun shines anew.Thanks!Questions?Comments?I’d love to hear how you’re using Chef.@flexlingie