Do not misunderstand the concept error handling in this document with error handling in usual software programming terminology. Usually when one writes a program, a syntax check will check for syntax including indentation, spacing, etc. But…
At times when certain tasks are executed by a playbook, it may be desired to run certain other task immediately. However, if the first task did not get executed successfully for what ever reason, we may…
At times one may want to run certain tasks or command only if certain conditions are met. For example add a user called “RedhatUser01” only if the managed node is a Redhat node. Similarly add…
At times you may want to execute a single tasks with multiple variable values one after the other. For example create 3 user accounts using one task. One way is to write three tasks in the…
This document is indented to demonstrate various playbooks that makes use of different modules and their functionalities. Pinging managed nodes [root@centos9vm ~]# cat inventory ====== ======= = 192.168.48.128 192.168.48.129 [testGRP] 192.168.48.128 192.168.48.129 ===== ===== [root@centos9vm…
Ansible got a set of modules that will allow playbooks to run different operations in managed nodes. This includes configurations to install yum packages using dnf utility, copy files from controller node to manage nodes,…
Ansible templates allows users to dynamically generate text-based files using templates, variables, and facts for configuration and other purposes. The difference between Ansible Facts and Templates is as follows: An ansible Fact stores variables that…
FACTS are variables related to remote systems. Ansible has the capability to discover and retrieve certain values from a remote node and store then in variables. This includes capturing the number of CPUs in the…
Ansible vault is a tool that helps to encrypt, decrypt and manage sensitive data such as passwords, playbooks, files, etc. If a playbook is encrypted, ansible-navigator will prompt for the password if ones tries to…
In the below example variables are defined in the host inventory file. [root@centos9vm ~]# cat inventory === === === 192.168.132.129 192.168.132.130 servera.example.com [webservers] servera.example.com serverb.example.com [dbservers] serverc.example.com serverb.example.com servera.example.com [myGroups:children] webservers dbservers [testGRP] 192.168.132.130 [testGRP:vars]…