Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Mastering Chef Provisioning

You're reading from   Mastering Chef Provisioning Render your entire infrastructure as code with Chef

Arrow left icon
Product type Paperback
Published in Jun 2016
Publisher Packt
ISBN-13 9781785888915
Length 262 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
 Waud Waud
Author Profile Icon Waud
Waud
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Mastering Chef Provisioning
Credits
Foreword
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface
1. Setting Up a Development Environment on Your Workstation 2. Knife Tooling and Plugins FREE CHAPTER 3. Leveraging Roles, Environments, and Policies 4. Custom Resources 5. Provisioning in the Traditional Data Center 6. Provisioning in the Cloud 7. Test-Driven Development 8. Using Chef Provisioning Index

Chapter 8. Using Chef Provisioning

In this chapter, you're going to learn to use Chef provisioning.

Wait… what? This is the last chapter in the book titled Chef Provisioning, and now you are going to learn to use Chef provisioning? What were we doing in Chapters 1–7?

Yes, in Chapters 1–7, we were doing Chef provisioning, but ChefDK actually comes with a feature named Chef Provisioning. In the earlier chapters, you learned how to use Chef to provision into a variety of hosting solutions, both in the data center and the cloud. However, most of the work we did to provision our environments was done in single-instance bites, creating one server instance at a time. All perfectly acceptable and very valuable. However, in the world of a DevOps Engineer, it is a rare situation when a single instance is all that is needed for an application. These days, distributed applications are built in clusters. An app will require multiple web servers, databases, app servers, networking and load balancers, and...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime
Visually different images