Ansible Playbooks Fundamentals

# CHAPTER 5

Ansible Playbooks Fundamentals #

1. Introduction #

2. Learning Objectives #

• Understand the structural hierarchy of Ansible Playbooks (Plays -> Tasks -> Modules).

• Write syntactically correct YAML code.

• Create a Playbook that executes multiple tasks sequentially.

• Implement privilege escalation (become) at the Play and Task levels.

• Execute a Playbook using the ansible-playbook CLI command.

3. Beginner-Friendly Explanation #

• The Playbook: The entire instruction manual (The file itself).

• The Play: A specific chapter in the manual aimed at a specific worker. E.g., "Chapter 1: Instructions for the Plumbers."

• The Task: A specific bullet point in that chapter. E.g., "Task 1: Install the kitchen sink."

• The Module: The actual tool the worker uses to complete the task. E.g., "Use the Wrench Tool to tighten the pipes."

In Ansible, a Playbook contains Plays (targeting specific server groups), which contain Tasks (the sequence of actions), which use Modules (the python scripts that do the work).

4. YAML Syntax Basics #

1. 1. It MUST start with three dashes ---.

1. 2. It relies strictly on indentation to show hierarchy. You MUST use spaces, never the Tab key. (Standard is 2 spaces per level).

1. 3. Lists begin with a dash and a space - .

1. 4. Key-Value pairs are separated by a colon and a space key: value.

5. Anatomy of a Playbook #

---
# THIS IS A PLAY
- name: Configure Web Servers # Human-readable description
  hosts: webservers           # Target group from the inventory
  become: yes                 # Run everything as root!

  # THESE ARE THE TASKS
  tasks:
    - name: Ensure Nginx is installed
      apt:                    # The Module being used
        name: nginx           # Module arguments
        state: present

    - name: Ensure Nginx is running
      service:                # The Module being used
        name: nginx
        state: started
        enabled: yes          # Start automatically on server reboot

6. Mini Project: Create First Ansible Playbook #

Step-by-Step Walkthrough:

1. 1. Create a file named setup_server.yml in your project directory.

1. 2. Paste the following YAML code:

---
- name: Standardize Linux Server Configuration
  hosts: all
  become: yes

  tasks:
    - name: Set timezone to UTC
      timezone:
        name: UTC

    - name: Install htop monitoring tool
      apt:
        name: htop
        state: present

    - name: Create a welcome message file
      copy:
        dest: /etc/motd
        content: "Welcome to this server, managed securely by Ansible!"

1. 3. Execute the playbook using the specific command for playbooks:

ansible-playbook setup_server.yml

Observation: The terminal will output a "Gathering Facts" status, and then execute each task one by one, showing changed or ok for every server in your inventory. At the end, a "PLAY RECAP" summarizes exactly how many servers were modified.

7. Real-World Scenarios #

8. Best Practices #

• Human Readable Names: Always, always, *always* provide a descriptive name: for every Play and every Task. Do not write - apt: name=nginx. Write - name: Install the Nginx Web Server. When a playbook runs, the terminal prints the name of the task. If a playbook has 50 tasks and fails on task 32, a descriptive name tells you instantly exactly what broke.

9. Security Recommendations #

• Granular Privilege Escalation: In our examples, we put become: yes at the Play level, meaning *every* task runs as root. This violates the Principle of Least Privilege. If a task is just copying a file to a normal user's home directory, it doesn't need root access. It is safer to apply become: yes ONLY on the specific tasks that require it (like package installations).

10. Troubleshooting Tips #

• Syntax Checks: YAML indentation is incredibly easy to mess up. One missing space will cause the entire playbook to crash. Before you execute a playbook, always run a dry syntax check:

ansible-playbook setup_server.yml --syntax-check

Ansible will validate the YAML without actually connecting to the servers.

11. Exercises #

1. 1. What is the fundamental formatting difference between a YAML dictionary (key-value) and a YAML list?

1. 2. Write a single Task that uses the user module to create a user named devops.

12. FAQs #

13. Interview Questions #

• Q: Explain the structural hierarchy of an Ansible Playbook, defining the relationship between Plays, Tasks, and Modules.

• Q: A playbook fails immediately with a Syntax Error before attempting to connect to any hosts. What is the most likely cause, and what specific CLI flag would you use in a CI/CD pipeline to prevent malformed playbooks from executing?

14. Summary #

15. Next Chapter Recommendation #