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

Code based on the Git branch

Let's assume you have four environments to take care of, which are as follows:

  • Development
  • Testing
  • Stage
  • Production

In the Git branch-based method, you will have one environment per branch. You will always make changes to Development first, and then promote those changes to Testing (merge or cherry-pick, and tag commits in Git), Stage, and Production. In this approach, you will hold one single inventory file, one set of variable files, and, finally, a bunch of folders dedicated to roles and playbooks per branch.

A single stable branch with multiple folders

In this approach, you will always maintain the development and master branches. The initial code is committed to the development branch...