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

Using AWX jobs

AWX jobs are executions of AWX jobs templates, in the same way as Ansible runs are executions of Ansible playbooks.

When you launch a job, you'll see a window just like the following one:

This is the AWX version of the output of Ansible, when run on the command line.

After a few seconds, in the right-hand grey box a very familiar output will start to pop out, since it's exactly the same stdout of Ansible, just redirected there.

If later you click on Jobs on the left menu bar, you will find yourself on a different screen, listing all previously run jobs:

As you can notice, we have two jobs that have been executed, while we've only executed the Demo Job Template. This is because the Demo Project has been pulled before and due to the Demo Job Template execution. This allows the operator to be always comfortable to run a job, knowing that it will always...