Until now, we have created cookbooks based on a particular technology. We created a cookbook for MariaDB, one for Apache HTTPd, and one for our app (including all the dependencies). What about the role of each of those infrastructure elements? A database role can include what is now running our database (MariaDB), but maybe tomorrow it can run something else (migrate back to MySQL, or switch to PostgreSQL). As roles in Chef have a dedicated run list, it's common to see a role include the product recipes, and everything related to it, think monitoring for example. Roles can do a lot more, like overriding attributes or have different run lists for each environment. Here, we'll create two generic database and webserver roles that might be simply reused later for another project that just need those services and a mysite role, that will include the two other roles. A role can include other roles as well as recipes. This way, the role for mysite will be enough to run...
Infrastructure as Code (IAC) Cookbook
By :
Infrastructure as Code (IAC) Cookbook
By:
Overview of this book
Para 1: Infrastructure as code is transforming the way we solve infrastructural challenges. This book will show you how to make managing servers in the cloud faster, easier and more effective than ever before. With over 90 practical recipes for success, make the very most out of IAC.
Table of Contents (18 chapters)
Infrastructure as Code (IAC) Cookbook
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Free Chapter
Vagrant Development Environments
Provisioning IaaS with Terraform
Going Further with Terraform
Automating Complete Infrastructures with Terraform
Provisioning the Last Mile with Cloud-Init
Fundamentals of Managing Servers with Chef and Puppet
Testing and Writing Better Infrastructure Code with Chef and Puppet
Maintaining Systems Using Chef and Puppet
Working with Docker
Maintaining Docker Containers
Index
Customer Reviews