We've previously seen how to automate systems with code and how to properly test this code. Now we're ready for prime time; there's a whole set of features, constraints, and objectives to be properly set. We'll want to isolate environments such as dev, staging, and production. We'll need our infrastructure code to stay consistent without our intervention. Security and confidentiality will start becoming an issue, and maybe those passwords and secret keys should not be stored in clear text at all. After a few months, our automated infrastructure will grow into a large number of managed nodes, and it will become critical to have coherent behaviour according to systems profiles—we'll need to gather and process system information. We'll eventually end up deploying web applications directly from Chef. To keep a high level of quality while our code base gets more and more complex, we'll switch to the Test-Driven Development (TDD) approach for our workflow. And finally, we'll make...
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