In this chapter, we'll explore some advanced and highly interesting areas that probably most developers today are already used to. Infrastructure code is still code, so it should be no different than software code; the same principle should apply. This means that the Docker code should be testable, the builds automatic, and the CI systems connected to our Git servers so they could continuously apply the tests. In addition to this, security checks should be part of the mandatory release process and the logs easy to access, even if the application is scaled on multiple machines. Also note that containers shouldn't be black boxes, and highly performant debugging tools should be available for us to do our work. The good news is that these topics will be covered in this chapter, because all of this can be done easily.
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