Book Image

Mastering Chef Provisioning

By : Earl Waud
Book Image

Mastering Chef Provisioning

By: Earl Waud

Overview of this book

This book will show you the best practices to describe your entire infrastructure as code. With the help of this book you can expand your knowledge of Chef because and implement robust and scalable automation solutions. You can automate and document every aspect of your network, from the hardware to software, middleware, and all your containers. You will become familiar with the Chef’s Chef Provisioning tool. You will be able to make a perfect model system where everything is represented as code beneath your fingertips. Make the best possible use of your resources, and deliver infrastructure as code, making it as versionable, testable and repeatable as application software
Table of Contents (17 chapters)
Mastering Chef Provisioning
Credits
Foreword
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface
Index

Using Chef environments


If your code development cycle goes through phases, such as development, test, stage, preproduction, and production, then you should also have servers that represent those same phases of development. Environments allow us to reproduce the workflow of the development life cycle by assigning servers to the different phases of that life cycle. Environments offer a way to designate a server as being within a specific part of the development process, such as test or production. Each server can be in one and only one environment. Put another way, a server cannot be in both development and production at the same time. The obvious benefit of using environments is that changes made to one environment will not impact other environments.

The _default environment

Every Chef server will have an environment created automatically when the server is deployed. That environment is named "_default". It is a permanent environment that cannot be renamed, modified, or deleted. Any node that...