The main thing I like about Ansible is that it has a very easy onramp. If you’ve done even a little bit of administration of a *nix system you’ve been exposed to the shell to interact with the system and ssh to connect you to a remote computer where you can interact with the remote system’s shell. At its most basic level, Ansible is just building on those pieces of knowledge.
For instance, let’s say you have a few computers at your house for you and your wife and your kids and the neighbors’ kids and the cat to use as a warm bed when the sun isn’t shining. You want to install a new piece of software on all of them. How do you do that?
Pre-Ansible it might look like this:
$ ssh host1 $ sudo yum -y install tmux $ exit $ ssh host2 $ sudo yum -y install tmux $ exit [...]
If you were feeling luc^Wconfident in your shell scripting you might try to automate some of that:
$ for host in host1 host2 [...] ; do for> ssh -t $host1 sudo yum -y install tmux for> done [sudo] password for badger: [types password] [waits while stuff gets done] Connection to host1 closed. [sudo] password for badger: [types password again] [waits while stuff gets done] Connection to host2 closed. [...]
A little better but we still have to type your sudo password prompt once for every host. You still have to wait between typing in your password. You still have the tasks running one-by-one on the remote hosts even though they could be done in parallel.
At this point, depending on what type of person you are you’ll be thinking one of three things:
- Yay! Automation!
- I bet I can do better… let me just crack open the expect manual, open up
my text editor, and maybe rewrite this in perl….
- You know, someone else must have written an application for this…
I’m a programmer by nature so once upon a time I probably would have found myself running down path 2 with nary a backwards glance. But if time, grey hairs, and the prodding of your more experienced sysadmin friends teaches you anything, it’s that you shouldn’t invent your own security sensitive wheel when someone else’s is perfectly serviceable. So let’s reach for Ansible and see what it can do here:
ansible '*' -i 'host1,host2,[...]' -a 'yum -y install tmux' -K --sudo sudo password: fedora20 | success | rc=0 >> Resolving Dependencies --> Running transaction check [...] Installed: tmux.x86_64 0:1.9a-2.fc20 Complete! katahdin | success | rc=0 >> Loaded plugins: langpacks Resolving Dependencies --> Running transaction check [...] Installed: tmux.x86_64 0:1.9a-2.fc20 Complete!
Nice! So now I can run ad hoc commands on multiple ad hoc hosts, using sudo if I want to. I type my sudo password just once at the very beginning and then go do other things while Ansible runs my task on all the hosts I specified! That certainly makes managing my home network easier. I think I’ll be using this tool more often….