So we have decided to push the required configuration through Chef into our infrastructure. However, any configuration management system gets true power once it allows us to provision different kinds of machines using a minimal piece of code. Imagine having different types of systems in your infrastructure such as dev machines running over laptops, staging environments that are set up on virtual machines, and production environments running on a beefy hardware. It's quite likely that for one class of application, the configuration for these three different sets of machines might be different. However, in most cases, the amount of difference between these configurations is minimal. For example, let's say you are managing infrastructure, running Hadoop. It's pretty obvious that the amount of data that you'll be working with in a staging environment would be substantially less than in a production environment. This would lead to a difference in the configuration...
Mastering Chef
By :
Mastering Chef
By:
Overview of this book
Table of Contents (20 chapters)
Mastering Chef
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
Introduction to the Chef Ecosystem
Knife and Its Associated Plugins
Chef and Ruby
Controlling Access to Resources
Starting the Journey to the World of Recipes
Cookbooks and LWRPs
Roles and Environments
Attributes and Their Uses
Ohai and Its Plugin Ecosystem
Data Bags and Templates
Chef API and Search
Extending Chef
(Ab)Using Chef
Index
Customer Reviews