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

Creating a Custom Module

This chapter will focus on how to write and test custom modules. We've already discussed how modules work and how to use them within your tasks. To quickly recap, a module in Ansible is a piece of code that is transferred and executed onto your remote host every time you run an Ansible task (it can also run locally if you've used local_action).

From my experience, I've seen custom modules being written whenever a certain functionality needs to be exposed as a first-class task. The same functionality can be achieved without the module, but it will require a series of tasks with existing modules to accomplish the end goal (and sometimes, command and shell modules too). For example, let's say that you want to provision a server through Preboot Execution Environment (PXE). Without a custom module, you would probably use a few shell or command...