Re-learning Ansible From Scratch
March 25, 2021
For several years, all I heard about was Ansible. It was going to solve every one of your deployment problems. It was going to make life easier. Heck, it was going to take us to Mars - well as long as SpaceX used it…
But after a short while, Ansible seemed to fall flat. As the infrastructure-as-code movement grew and the immutable infrastructure alongside it, other tools seemed to overtake Ansible. I stopped learning it at this point since I started work on Kubernetes-based applications, which fully embraced immutable infrastructure.
Recently, however, I’ve been working on some applications that use traditional virtual machines rather than a cloud-native approach. To manage our fleet of 20+ VMs (in one environment!), we turned to Ansible. We use Ansible to perform configuration management of all of our VMs and run ad-hoc commands for debugging our system or recovering from a failure.
Since I’ve been re-learning Ansible, I thought it would be helpful to give some insights into what it is, what its components are, and a few gotchas I’ve encountered. I won’t get into all the nitty-gritty since Ansible gets complicated FAST. However, since Ansible does get so complicated so fast, it can be tricky to review. I’ll leave you with some tips on how to code review your Ansible for success and maintainability in the long term.
What is Ansible?
Ansible is essentially a provisioning and configuration management tool. You write mostly declarative
.yml files to specify the desired state of a machine. The idea is that instead of having to write a large bash script to install packages or move files around, you simply declare the desired state you want the machine to be in regardless of its current or present state.
When I say that Ansible is mostly declarative, what I mean is that Ansible strives to be as declarative as possible but there are cases it violates that principle. For instance, Ansible also has the ability to perform user-defined loops, set variables, and make simple boolean decisions. You can even run snippets of python code as filters to do more complex commands/transformations.
How Does it Work?
I’ll keep this brief since a full explanation could get very long and very complicated. Ansible works by essentially creating ssh connections to a set of target hosts, copying python code to those machines, and executing that python on those machines to make changes to the system. Micheal DeHaan (the creator) called it “ssh in a loop.”
Ansible is also stateless. What that means is that Ansible reads the present state of a machine while it is being run and makes the changes required to move it into the desired state. This is great in many ways as it allows you to start controlling a target machine almost instantly. But it also leads to odd problems. For example, if at one point you needed a file to be created on the machine, but you don’t need it anymore, Ansible won’t auto-cleanup that file for you - you would need to write a specific Ansible configuration to remove it.
How Do You Use It?
With Ansible, you typically have the following components:
- Inventory - a collection of machines/hosts you want to control/configure. You can group them into hierarchies with children, etc. You can also target multiple groups using various patterns and limit commands.
- Modules - modules are essentially abstractions to controlling a target host. Think of them as an API layer provided by Ansible for all the things you would want to do on a host. You use various modules to interact with different parts of the hosts you are changing. Modules tend to be aligned with either a specific machine sub-system (files, packages, networking), commonly used packages (systemctl), but also exist for cloud providers or specific vendor-related needs.
- Tasks - tasks are single invocations of a module. They tend to be extremely small and make incremental changes. Think of a task as interacting with a specific API for the host you are targeting. Tasks utilize modules to accomplish this interaction
- Roles - roles are effectively a grouping of tasks. In many Ansible projects, you will have playbooks that invoke a series of plays as roles with specific vars (see vars below). Roles tend to be thought of as the core building block for Ansible as they can allow someone to group all the tasks needed for a specific desired state. For example, installing and starting a database onto a host.
- Playbooks - a collection of “plays” that you run against a set of hosts. Plays tend to be specific groups of roles or tasks that wholistically apply one logical change.
- Vars - variables that are used dynamically in plays at runtime to configure the machines in your inventory. Vars get complicated fast, so knowing variable precedence is important.
What is Ansible Good At? Where Does it Fall Short?
Ansible is extremely good at the desired state model described above: make this machine have this state. This can be a great use case for creating or provisioning new machines or managing existing machines.
Ansible is also very good at making common commands you might need for debugging accessible and re-usable. Instead of logging into 20+ machines to search for a log entry or see if a service is up, you can target all the hosts using a playbook or ad-hoc command to look on all machines and report back.
The place Ansible falls short is really orchestration. Orchestration is the process of controlling how a fleet of machines is all updated to accomplish a larger goal. This is in contrast to controlling a single machine. A trivial but common example of orchestration is updating each machine in a specific order. This can be done in Ansible, but it usually requires running playbooks limited to specific hosts.
The other large issue with Ansible that I have found is it can easily feel like “cobwebs” or “spaghetti.” Vars can come from seemingly anywhere and be overridden at every level according to Ansible’s variable precedence rules. As the complexity of an environment grows, the complexity of the vars needed also grows. While powerful and flexible, I have spent hours frustrated with Ansible when a var I thought had a specific value got overridden in a place I didn’t think would apply.
What To Pay Attention To When Reviewing Ansible
With all of these pitfalls, it can be difficult to review Ansible code changes effectively. I’ve found that a few things can help.
- Use a Linter - anytime I talk about code reviews, I always recommend using a linter to help keep format and syntax standard acros your team. In Ansible, this is very important. “Spaces within curly braces?” “Qoutations here or not?” “True, true, or yes?” Just use the ansible-lint package and don’t look back :)
- Var Precedence - I’ve mentioned this several times already, but variable precedence is such a crucial thing to understand in Ansible. If you understand this poorly, you will spend hours at the keyboard not understanding why that value keeps changing on you.
- Host Group Organization - you use host groups to target the hosts you want specific plays and tasks to run on. You should know how they are organized! If you see changes that make it confusing to identify which host(s) a play will run on, speak up! When you can’t understand how your host groups are organized, all the rest of your Ansible setup is useless.
- Var Names - variable names come up in almost all forms of code reviews, but in Ansible, this is especially true. Vars in Ansible are set to either global scope, play scope, or host scope, but you will quickly discover that variables get referenced all over the play, and it can be hard to keep track. My recommendation is to name vars with specific intention and keep them as close to a host or play context as possible. Prefixing vars from your vault with
vault_is also a pattern I have used with a lot of success.
Last, always try to group related tasks into a role that you can reuse in different playbooks. This will pay dividends as your Ansible code grows.
This is just a short glimpse into the world of Ansible. I know it wasn’t an in-depth tutorial, but I hope some general guidelines and principles help you as you start to use it!
Happy coding (yaml-writing?)!
If you enjoyed this article you should join my newsletter! Every other Tuesday I send you tools, resources, and a new article to help you build great teams that build great software.
Dan Goslen is a software engineer, climber, and coffee drinker. He has spent 10 years writing software systems that range from monoliths to micro-services and everywhere in between. He's passionate about building great software teams that build great software. He currently works as a software engineer in Raleigh, NC where he lives with his wife and son.