Book Image

Practical Ansible - Second Edition

By : James Freeman, Fabio Alessandro Locati, Daniel Oh
Book Image

Practical Ansible - Second Edition

By: James Freeman, Fabio Alessandro Locati, Daniel Oh

Overview of this book

Ansible empowers you to automate a myriad of tasks, including software provisioning, configuration management, infrastructure deployment, and application rollouts. It can be used as a deployment tool as well as an orchestration tool. While Ansible provides simple yet powerful features to automate multi-layer environments using agentless communication, it can also solve other critical IT challenges, such as ensuring continuous integration and continuous deployment (CI/CD) with zero downtime. In this book, you'll work with the latest release of Ansible and learn how to solve complex issues quickly with the help of task-oriented scenarios. You'll start by installing and configuring Ansible on Linux and macOS to automate monotonous and repetitive IT tasks and learn concepts such as playbooks, inventories, and roles. As you progress, you'll gain insight into the YAML syntax and learn how to port between Ansible versions. Additionally, you'll understand how Ansible enables you to orchestrate multi-layer environments such as networks, containers, and the cloud. By the end of this Ansible book, you'll be well versed in writing playbooks and other related Ansible code to overcome all your IT challenges, from infrastructure-as-a-code provisioning to application deployments and handling mundane day-to-day maintenance tasks.
Table of Contents (21 chapters)
Free Chapter
1
Part 1:Learning the Fundamentals of Ansible
6
Part 2:Expanding the Capabilities of Ansible
12
Part 3:Using Ansible in an Enterprise

Differentiating between different environment types

In almost every business, you will need to split your technology environment by type. For example, you will almost certainly have a development environment, where all the testing and development work is performed, and a production environment, where all of the stable test code is run. The environments should (in a best-case scenario) make use of the same Ansible playbooks—after all, the logic is that if you can successfully deploy and test an application in your development environment, then you should be able to deploy it in the same way in a production environment and have it work just as well. However, there are always differences between the two environments, not just in the hostnames but also sometimes in the parameters, the load balancer names, the port numbers, and so on—the list can seem endless.

In the The preferred directory layout section of this chapter, we covered a way of differentiating between a development...