Book Image

Learning Ansible 2.7 - Third Edition

By : Fabio Alessandro Locati
Book Image

Learning Ansible 2.7 - Third Edition

By: Fabio Alessandro Locati

Overview of this book

Ansible is an open source automation platform that assists organizations with tasks such as application deployment, orchestration, and task automation. With the release of Ansible 2.7, even complex tasks can be handled much more easily than before. Learning Ansible 2.7 will help you take your first steps toward understanding the fundamentals and practical aspects of Ansible by introducing you to topics such as playbooks, modules, and the installation of Linux, Berkeley Software Distribution (BSD), and Windows support. In addition to this, you will focus on various testing strategies, deployment, and orchestration to build on your knowledge. The book will then help you get accustomed to features including cleaner architecture, task blocks, and playbook parsing, which can help you to streamline automation processes. Next, you will learn how to integrate Ansible with cloud platforms such as Amazon Web Services (AWS) before gaining insights into the enterprise versions of Ansible, Ansible Tower and Ansible Galaxy. This will help you to use Ansible to interact with different operating systems and improve your working efficiency. By the end of this book, you will be equipped with the Ansible skills you need to automate complex tasks for your organization.
Table of Contents (18 chapters)
Free Chapter
1
Section 1: Creating a Web Server Using Ansible
4
Section 2: Deploying Playbooks in a Production Environment
9
Section 3: Deploying an Application with Ansible
13
Section 4: Deploying an Application with Ansible

Transforming your playbooks in a full Ansible project

Let's see how to transform the three playbooks we used to set up our web infrastructure (common_tasks.yaml, firstrun.yaml, and webserver.yaml) to fit this file organization. We have to remember that we also used two files (index.html.j2 and motd) in those roles, so we have to place these files properly too.

First, we are going to create the folder structure we have seen in the previous paragraph.

The easiest playbook to port is firstrun.yaml, since we only need to copy it into the playbooks folder. This playbook will remain a playbook because it's a set of operations that will have to be run just one time for each server.

We now move to the common_tasks.yaml playbook, which will need a little bit of a rework to match the role paradigm.