Ansible Tutorial 11: Defining and Managing Tasks in Playbooks

In the previous article, we discussed the structure and syntax of Ansible Playbooks. This article delves deeper into how to define and manage tasks within Ansible Playbooks. Tasks are the fundamental building blocks of a Playbook—they specify exactly what actions to perform on target hosts. Understanding how to define and manage tasks is essential for writing effective, reliable Playbooks.

Basic Task Structure

In Ansible, tasks begin with the tasks keyword and follow this basic structure:

tasks:
  - name: Task description
    module_name:
      parameter1: value1
      parameter2: value2

Here, name provides a human-readable description of the task; module_name specifies the Ansible module to invoke; and the indented key-value pairs beneath it are the module’s parameters.

Example: Installing a Package

The following example demonstrates using the apt module to install a package:

---
- hosts: all
  tasks:
    - name: Install nginx
      apt:
        name: nginx
        state: present

In this example, we define a task named “Install nginx” that uses the apt module to ensure the nginx package is installed and present on the target system.

Task Management

Managing tasks effectively is critical when authoring Playbooks. Key aspects include:

1. Task Execution Order

Tasks execute sequentially—top to bottom—in the order they appear in the Playbook. You can leverage this deterministic ordering to enforce dependencies. For instance, you might update the system’s package cache before installing applications.

tasks:
  - name: Update apt cache
    apt:
      update_cache: yes

  - name: Install nginx
    apt:
      name: nginx
      state: present

2. Conditional Execution

Sometimes you want to run a task only when certain conditions are met. The when clause enables conditional execution. For example, install nginx only on Debian-family systems (e.g., Ubuntu):

tasks:
  - name: Install nginx (Debian-family only)
    apt:
      name: nginx
      state: present
    when: ansible_os_family == 'Debian'

3. Executing Tasks by Host Group

Ansible lets you assign tasks to specific host groups. By defining distinct play sections targeting different groups, you can tailor operations per environment or role.

---
- hosts: webservers
  tasks:
    - name: Install nginx
      apt:
        name: nginx
        state: present

- hosts: dbservers
  tasks:
    - name: Install MySQL server
      apt:
        name: mysql-server
        state: present

In this example, nginx is installed only on hosts in the webservers group, while mysql-server is installed only on hosts in the dbservers group.

4. Error Handling

Some tasks may fail under expected circumstances (e.g., attempting to remove a package that isn’t installed). To prevent such failures from halting the entire Playbook, use ignore_errors: yes.

tasks:
  - name: Attempt to uninstall nginx
    apt:
      name: nginx
      state: absent
    ignore_errors: yes

Task Reusability

To improve maintainability and reduce duplication, Ansible supports organizing reusable tasks into roles. Roles encapsulate related tasks, variables, files, templates, and handlers—making them portable across multiple Playbooks.

A typical role directory structure looks like this:

roles/
  my_role/
    tasks/
      main.yml

Then reference the role in your Playbook:

---
- hosts: all
  roles:
    - my_role

Conclusion

This tutorial covered how to define and manage tasks in Ansible Playbooks—including their basic structure, execution order, conditional logic, host-group targeting, error handling, and reuse via roles. Thoughtful organization and management of tasks form the foundation of efficient, scalable automation.

In the next article, we’ll explore how to use loops and conditional statements inside Playbooks—further enhancing flexibility and functionality in infrastructure automation. Stay tuned!