Trotter Cashion 4.42
System provisioning is a difficult task that is often done using a set of instructions saved in a text file on someone’s computer. Even the places that are “doing it right” rely on a large number of bash scripts with directories full of one off templates for each host; a system utterly unmaintainable. Chef is a tool that seeks to change all of this by allowing developers and system administrators to write and maintain their provisioning scripts in Ruby and then to share these scripts as cookbooks with others. This results in much simpler system provisioning and allows inexperienced administrators to leverage the knowledge of experts by importing their cookbooks. Chef takes the arduous, multi-hour and even multi-day task of setting up new boxes and reduces it to something that can be done in as little as five minutes. Though it is not the first automated provisioning framework (Puppet is still quite popular), it is definitely the current best.
In this talk, I’ll be covering how easy it is to get going with Chef using Chef Solo. Chef Solo requires very little setup on either the developer’s machine or the machine to be provisioned and is a much smaller time investment than the larger Chef Server. Though the current Chef documentation online is very thorough, it is also very difficult to understand if you don’t already understand Chef’s point of view of provisioning. This talk will help participants gain enough knowledge know why they should use Chef, how to get started with Chef Solo, and what parts of the documentation are most important to them as they get going.