Ansible

Notes

Ansible can be thought of as a for-loop over SSH scripts, but it's also much more than that.

Basic Features

Ansible config management scripts (playbooks) are in YAML. This is like executable documentation - kind of like a readme containing all the commands you would otherwise be running, all typed out, except instructions won't go out of date because they're actually being executed.

Ansible servers require SSH and Python.

Push Based

Ansible is push-based, which means the workflow looks like this:

• You make a change to the playbook
• You run the new playbook
• Ansible connects to servers and executes modules, changing the server state

The ansible-playbook command is the gateway to connecting to the remote server.

The push-based approach means you control when things happen to the server, making scaling easier.

Scaling Down, Too

Ansible obeys Alan Kay’s maxim: “Simple things should be simple; complex things should be possible.”

Modules

Ansible allows you to execute arbitrary shell commands.

Ansible also offers more powerful feature: modules, which perform tasks like installing packages restarting services, or copying config files.

Modules are declarative: describe/declare the state you want the server to be in. Example: invoke the user module to ensure there is an account named "deploy" that is in the group "web"

user: name=deploy group=web

Ansible is idempotent - meaning, if the user already exists, it will do nothing. This makes it safe to run the Ansible script multiple times.

What You Should Know

List of things you should know how to do before getting started:

• connect to remote machine via SSH
• interact with bash command line shell (pipes and redirects)
• install packages
• use sudo command
• check and set file permissions
• start/stop services
• set env vars
• write scripts (any language)

Ansible also uses uses YAML and Jinja and is Python-based.

Directory Structure

The basic directory structure we'll use with Ansible is to create a playbooks directory to hold everything:

playbooks/
    .vagrant/   <-- directory used by vagrant for keys/machines
    hosts       <-- ansible inventory file

Using Ansible Locally with Vagrant

Vagrant allows you to set up virtual machine(s) using VirtualBox, which can give you a way of testing Ansible scripts locally (without using the AWS or Google Cloud platforms). You can then connect Ansible with vagrant to manage and set up compute nodes using Ansible.

Before you begin: set up vagrant box

See the Basic Startup and Shutdown Procedure section of the Vagrant page for steps to set up a Vagrant box, connect to it via SSH, and (when we're done) shut down the box.

Connect Ansible to Vagrant

Once we start up a Vagrant box, we can get Ansible working with the Vagrant boxes by telling Ansible about how to connect to the machines that Vagrant created.

To do this, we create an inventory file in playbooks/hosts. Recall from the Vagrant page that Vagrant started a Ubuntu server, which was available via IP address 127.0.0.1 on port 2222 (see output of vagrant ssh-config from Connect to Vagrant Machine section). We were able to SSH to the machine both using the vagrant ssh command, and a plain ssh command that used the private key in the .vagrant directory.

These details should all be passed to Ansible via the inventory file:

$ cat playbooks/hosts

testserver ansible_host=127.0.0.1 ansible_port=2222 ansible_user=vagrant ansible_private_key_file=.vagrant/machines/default/virtualbox/private_key

(Note that the private key file is shown when you run vagrant ssh-config with the vagrant box running.)

Side note: once you are ready to run with an AWS EC2 node, you would specify the hostname of the EC2 node and the AWS .pem private key, like so:

$ cat playbooks/hosts

testserver ansible_host=ec2-203-0-113-120.compute-1.amazonaws.com ansible_user=ubuntu ansible_private_key_file=/path/to/keyfile.pem