Now that you've learned the key terminology that Chef uses and dissected an example infrastructure a bit, you can see the following:
Infrastructure can be decomposed into the various roles that resources (nodes) play within that infrastructure
A combination of recipes and configuration data provide us with roles that describe a part of our overall infrastructure
Chef analyzes the roles applied to hardware resources (nodes) and generates a run list that is specific to the node that those roles are being applied to
A run list is then combined with the cookbooks, recipes, templates, and configuration data to build a specific set of scripts that are executed on the node when the chef-client is run
We can apply these methodologies of automated configuration to cloud servers and physical systems alike.
Now that you understand how Chef models interact, let's take a look at how we can get started with cloud services using Chef.