This article is about using Ansible on the command-line.
You …
-
… want a convenient way to do ad-hoc tasks on a bunch of machines.
-
… already have a few playbooks and machine groups defined in your inventory.
-
… don’t want to invest too much into Ansible because you have other things to do and Ansible is just a tool to deal with one aspect of what you want to do.
-
… live on the command-line.
-
… think
ansible-playbook
andansible
commands have too many knobs and too few knobs at the same time.
Taking a page from old school Posix tools, let’s make a script that encodes Ansible group names into the filename.
Then you can go from this:
$ ansible atlanta -m copy -a "src=/etc/hosts dest=/tmp/hosts"
$ ansible webservers -m service -a "name=httpd state=started"
To this:
$ atlanta copy "src=/etc/hosts dest=/tmp/hosts"
$ webservers service "name=https state=started"
Or from this:
$ ansible-playbook -l atlanta go-to-the-moon
$ ansible-playbook -l webservers do-the-other-things
To this:
$ atlanta go-to-the-moon
$ webservers do-the-other-things
These are just examples. Please don’t spend time bikeshedding names because you can use whichever names you like.
-
Download the contents of
ansible-by-proxy
from here. It’s a starter script that includes a bunch of sensible settings expressed via environment variables. Remove or change these to match your needs.Note that the script expects to find a sub-directory called
ansible
in the same directory as the script which contains the playbooks and the inventory file. -
Store this file somewhere on the system
PATH
.Don’t forget to mark the file as executable if it isn’t already.
$ chmod +x ansible-by-proxy
-
Create symlinks to the file that have the same name as hostnames or groups as described in the includes:
$ ln -s ansible-by-proxy atlanta $ ln -s ansible-by-proxy webservers
and so on.
That’s it. Now you can invoke playbooks and tasks just by using the name of host or group.