How to implement continuous deployment of operational configurations using Chef and Git. Given as a lightning talk at the "Continuous Deployment ArchCamp, 03/30/2011. http://www.meetup.com/ArchCamp/events/16419122/

1. Continuous Deployment for
Ops
(who use Chef and git)
@mikebabineau
EA2D

3. Infrastructure as Code
“Enable the reconstruction of the business from nothing but a
source code repository, an application data backup, and bare
metal resources”
- Jesse Robbins

4. Chef primer
Client-server config management tool
Cookbooks - modules with recipes for doing stuff
Roles - which recipes? what settings?
Data Bags - JSON object storage
Knife - CLI tool

5. Bad:
$ knife role edit myrole

6. Better:
$ knife role from file roles/myrole.json

7. How?
$ tree -a chef-repo
chef-repo
├── .chef
├── .git
├── cookbooks
│ └── myapp
├── databags
└── roles
└── myrole.json

8. Best:
$ git push origin master

9. How?
for cookbook in $(git_diff("cookbooks")); do
knife cookbook upload $cookbook
done
for role in $(git_diff("roles")); do
knife role from file $role
done
for bag in $(git_diff("databags")); do
for item in $(git_diff("items", $bag)); do
knife data bag from file $bag $item
done
done

10. How do you test?
$ git push origin dev

11. $ cat .chef/knife.rb
...
# (original by jtimberman@opscode.com)
require 'grit'
branch = Grit::Repo.new("#{current_dir}/..").head.name
case branch
when "master"
orgname = "ea2d"
else
orgname = "ea2d-dev"
end
validation_key "#{current_dir}/#{orgname}-validator.pem"
chef_server_url "https://api.opscode.com/organizations/#{orgname}"
validation_client_name "#{orgname}-validator"
...
https://gist.github.com/829733

12. Questions?
mikeb@ea2d.com
We're hiring:
AWS, Java, Chef, Python,
JS, GAE, NoSQL, DevOps, etc.
http://ea2d.com/jobs/