Ansible Playbook Structure Best Practices

Define and apply a company-wide consistent structure for all your Ansible Playbooks that allows for easy understanding and maximum reutilization

Ansible Playbook Structure

Ansible Playbook structure is defined in official documentation but the recommended way to group hosts and apply roles is something that each user would have to decide for itself.

Define and apply a company-wide consistent structure for all your Ansible Playbooks that allows for easy understanding and maximum reutilization.

  • Avoid using individual hostnames to select hosts. In the cloud, all hosts should be treated as cattle, not as pets.
  • Create groups of hosts by:
    • Operating System and major release
    • Application and application release
    • Environment
  • Give safe defaults to all roles and use the group_vars to redefine values
  • Use a single playbook definition file for each environment
group_vars\allContains default values for variables that will be applied to all hosts, independently from its membership to other groups.
group_vars\tag_app_wpContains values to variables from hosts in group tag_app_wp (AWS tag app=wp).
group_vars\tag_environment_preContains values to variables from hosts in group tag_environment_pre (AWS tag environment=pre).
group_vars\tag_environment_proContains values to variables from hosts in group tag_environment_pre (AWS tag environment=pro).
inventorySince we are using Ansible Dynamic Inventory, it has the ec2.ini and files.
roles\Root roles directory
roles\linux\add_packagesRole to install WordPress
roles\linux\host_nameRole to set the hostname of the instance
roles\linux\hosts_fileRole to modify local hosts file for resolver
roles\linux\pam_limitsRole to set various pam limits for kernel configuration
roles\linux\wordpressRole to install WordPress
ansible.cfgLocal ansible configuration
ditwl_pro.shSets environment variables for PRO environment
ditwl_pro.ymlPlaybook for PRO environment
Table of Contents
Primary Item (H2)Sub Item 1 (H3)Sub Item 2 (H4)
Sub Item 3 (H5)
Sub Item 4 (H6)

Related Cloud Tutorials

Ansible Multiple Environment Best Practices
Ansible Multiple Environment Handling multiple infrastructure environments with Ansible is easily done by targeting the environment tag that is included in the mandatory AWS Tags. See AWS Tagging Best Practices. Avoid mixing environments mistakes Have switches, configurations redundancies and different keys for each environment to reduce the possibility of applying changes to the wrong client […]
Ansible Roles Best Practices
Ansible Roles Granularity We recommend building Ansible roles that are highly reusable by configuration, but we also recommend pragmatism as our highest priority. Roles for systems and applications designed to be standalone, or before the Cloud was around, are called “non-native cloud applications”, often those are stateful applications that can not be clustered without sharing […]
Ansible Dynamic Inventory
Allows you to generate inventory (host and group information) dynamically rather than statically defining it in a static inventory file
AWS Terraform module
Infrastructure as Code IaC is an approach to managing and provisioning computing infrastructure through machine-readable code and automation, rather than manual processes. In IaC, infrastructure is defined, configured, and managed using code, which can be version-controlled and treated like any other software application. IaC involves: IaC provides several benefits, including improved efficiency, reduced manual errors, […]
LAN, NAT, HOST Only and Tunnel Kubernetes networks
Kubernetes Cluster using Vagrant and Ansible with Containerd (in 3 minutes)
Tutorial and full source code explaining how to create a Kubernetes cluster with Ansible and Vagrant for local development under 3 minutes.
How to use Ansible and Terraform together
This Ansible AWS tutorial shows how to use Ansible and its dynamic inventory to provision the software and configuration of infrastructure that has been created with Terraform.
AWS Public and Private Network in a VPC
AWS VPC, Route 53, RDS MariaDB, EC2 using Ansible and Terraform (1/5)
Tutorial and source code explaining how to provision and configure a VPC, Route 53, RDS MariaDB, Instances and security groups using Ansible and Terraform on AWS to run WordPress in an Ubuntu server with Nginx, PHP, and Let’s Encrypt.

Javier Ruiz

IT Wonder Lab tutorials are based on the rich and diverse experience of Javier Ruiz, who founded and bootstrapped a SaaS company in the energy sector. His company, which was later acquired by a NASDAQ traded company, managed over ‚ā¨2 billion per year of electricity for prominent energy producers across Europe and America. Javier has more than 20 years of experience in building and managing IT companies, developing cloud infrastructure, leading cross-functional teams, and transitioning his own company from on-premises, consulting, and custom software development to a successful SaaS model that scaled globally.

Leave a Reply

Your email address will not be published. Required fields are marked *

linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram