Ansible Tips and Tricks

Some tips and tricks I've accumulated while working with Ansible...

In french, Ansible can be pronounced as "en cible", "in target".

If you have been doing a bit of Ansible, there is probably some coding style that has emerged from your work, especially if you work in a team around the same code. During my time as an Ansible developer, I had the opportunity to collect some tips I use on a regular basis when writing scripts. These tips will probably help you save some time.

I assume that you already know Ansible, Playbooks, YAML syntax and Ansible Galaxy roles.

1 - Always name everything.

It is possible to run Playbooks or Tasks without ever naming them:

- hosts: local
  - user:
      name: testuser1
      state: present
      groups: wheel


PLAY ***************************************************************************
TASK [user] *******************************************************************

This log is not particularly interesting. We can probably do better.

For example:

- name: "Prepare localhost"
  hosts: local
  - name: "Create testuser1"
      name: testuser1
      state: present
      groups: wheel

Will print out:

PLAY [Prepare localhost] ******************************************************
TASK [Create testuser1] *******************************************************

It's much more readable. To to even better, you can add more DEBUG informations in the Tasks names, such as:

- name: "Create folder {{ target_folder }}"
    path: "{{ target_folder }}"
    recurse: yes
    state: directory

As always, the message should contain as much information as possible to allow the developer to DEBUG in case of error. I always try to do that so that future analysis is easier to do. You never know: you might really be in a hurry next time you want to understand why your code fails.

Always name your Ansible Tasks.

2 - Use the YAML syntax, not the Ansible one

With Ansible, you can use a mix of two syntax when writing code. Either pure YAML:

- name: add user testuser1
    name: testuser1
    state: present
    groups: wheel

Or the hybrid YAML/Ansible syntax:

- name: add user testuser1
  user: name=testuser1 state=present groups=wheel

These two examples are identical in terms of Ansible description. In the first case, Ansible will parse the YAML document and then run the code. In the second case, Ansible will also parse name=testuser1 state=present groups=wheel before running the task user. This syntax is useful but forces you to do some intellectual work (= or :, YAML or inline, ...) before being able to write working code, especially when it is complex.

My suggestion is to use the YAML syntax every time, avoiding the = syntax. It will help you detect errors earlier, and a make your Ansible code easier to read.

With some practise, it also becomes easier to write than the usual Ansible/YAML mix

Always use the YAML syntax.

3 - Document your variables

Ansible supports variable overriding according to where it finds their declaration. In the official documentation, the priority of these declarations is as follow:

        role defaults
        inventory vars
        inventory group_vars
        inventory host_vars
        playbook group_vars
        playbook host_vars
        host facts
        play vars
        play vars_prompt
        play vars_files
        registered vars
        role and include vars
        block vars (only for tasks in block)
        task vars (only for the task)
        extra vars (always win precedence)

As you can see, the list is rather long and allows you to override a variable almost anywhere. This means that you have to be careful:

I tend to use use group and roles variable as much as possible before resorting to other declaration levels.

I also try to document these settings (for example, with a real life file):

# file: group_vars/all
# For data synchronisation from the server to localhost
local_source_folder: /Users/octplane/src/wiseman_r
remote_production_folder: /home/oct/prod

# app name to look for in the local registry
app_name: wiseman
# image name to search for in the local image registry
image_name: "octplane/{{ app_name }}"
# version to search for in the local image registry
version: 4
# where to export the docker image
export_folder: /tmp
# Exported file from docker after zipping
artefact_name: "{{ app_name }}-{{ version }}.docker.gz"

# where to copy the data on the remote server
# where is deployed the test application
    landing_folder: /home/oct/tmp
    test_folder: /home/oct/data/wiseman.test/

This way, when I'll come back on this code, or if anybody (such as you) reads it, it's easier to understand how it's working rather than switching between roles and variables all the time.

Always document your variables.

Try to minimise where you declare your variables.

4 - Use asserts to validate the parameters

With the documentation you've just written, you can check the parameters before using them and avoid many pitfalls. Not running things that will break down is a good thing to do.

    - name: "Validate version is a number, > 0"
          - "{{ version | int }} > 0"
        msg: "'version' must be a number and > 0, is \"{{version}}\""

As always, write meaningful error messages. There is a huge difference between a generic error message printed by Ansible and something you might have written yourself such as: 'version' must be a number and > 0, got "coucou".

Use assert to bail early in case of error.

Write meaningful error messages.

5 - Change the stdout default logger

The default stdout Ansible logger kinda sucks. It lacks useful timing information, takes a lot of screen estate. That's why I'd like to suggest you try an alternate logger:


I am the author of this logger and here are some of its features:

Don't forget to see what's new on the internet

If you use open-source code, contribute back, please.

6 - Write roles in a product-oriented way

As soon as you start writing an Ansible role, it's very tempting to put everything inside the same role in order to have some kind of reusable toolbox.

You actually need to separate role content by technical object: one role for MongoDB, one for HAProxy, another for Tomcat, and then use the playbook-provided glue to assemble and describe the behaviour you are looking for.

This segregation allows you to merge together all the administrative tasks you might need for a given component: installation, configuration, startup, halt, update, maintenance... and only for this component.

If you code needs to act on another technical component, try to move it to another role as soon as possible. If you really really need to orchestrate these tasks from a role, write a role whose sole purpose is to call others roles' actions.

The goal of this separation is to lower the dependency between the roles and the technical products, lowering the number of needed variable to run it. In the end, this will allows you to reuse roles much more quickly, which is really what we are looking for.

A role must only handle a single technical component.

Write abstract role to call the technical ones when needed.

7 - Use the same role for several operations

Technically, a role presents a single entry point, its tasks/main.yml. Because of this design, one might think it's difficult to have a role accomplish several actions (without using tags, cf below, or includes).

And still, there is a way to write re-usable role easily, including different unrelated operations.

Using a variable to decide which action to perform, you can have a small operation router inside your role:

# roles/service/vars/main.yml
# by default, we ensure that service is present, configured and running.
# allowed values: present, absent, install, configure, start, stop
state: present
# roles/service/tasks/main.yml
- include: "{{ state }}.yml"
# roles/service/tasks/present.yml
- include: "install.yml"
- include: "configure.yml"
- include: "start.yml"
# roles/service/tasks/install.yml
- name: add user testuser1
    name: testuser1
    state: present
    groups: wheel

Extend role so that they can fulfil several tasks.

8 - Be careful with set_fact

set_fact creates variable in your Ansible script, at runtime, to have a mode dynamic behaviour. It's very useful. However, these on-the-fly-created variables have several drawbacks, and you need to carefully think about it before creating one:

Moral of the story: be careful with there set_fact that can, like the proverbial poisoned apple, explode at your face at the worst time.

Limit the set_fact to where they are absolutely necessary.

9 - Use tag with moderation

As soon as you write a role with several uses, it's very tempting to use tags to filter out some tasks at runtime. It works in most case and allows you to run your deployments using the -t option (or --skip-tags to ignore them).

However, at least two problems can rise when using these in Ansible:

In the end, I strongly encourage you to use the routing system presented higher. It does not use another functionality in Ansible and forces the role developer to clearly separate its role functionalities. Tags will be reserved for the interactive use of Ansible in CLI, by opposition to the one driven though a script or an orchestrator.

Use the tags, but wisely.

10 - Don't hesitate to reconfigure Ansible

Thanks to a very simple overloading model, it's possible to give Ansible an ansible.cfg in which you can reconfigure parts of Ansible according to your needs: for an alternative hostfile (no need to -i myhosts in CLI every time), to remove the useless .retry files, or anything else, you can just create an ansible.cfg file where you run your playbooks so that Ansible can automatically fetch and merge its content with the global configuration. The precedence order is as follow:

* ANSIBLE_CONFIG (an environment variable)
* ansible.cfg (in the current directory)
* .ansible.cfg (in the home directory)
* /etc/ansible/ansible.cfg

(source http://docs.ansible.com/ansible/intro_configuration.html)

Customise your Ansible experience.


We saw together that the regular use of Ansible allows the emergence of good practices that will make the use of this tool easier every day. These tips are obviously extracted from my own personal experience and chats with developers. I probably over-simplified some of these things and forgotten others. Let's recap' together:

And you? How do you use Ansible? Got any tip to share? Now is your turn!