MORE ANSIBLE...
(Posted 2015-04-19 01:12:37 by corey_reichle)

So, I've finally refactored my Ansible playbook, in order to make it fit
the Ansible-provided best practices.  It can be cloned down
at: https://github.com/coreyreichle/ansible.git [
https://github.com/coreyreichle/ansible.git ]

The git log will keep track of the steps to create the playbook from
scratch, so you can read there, to build it yourself.  Really, just
starting with the make_dirs.sh script will get you well on your way if you
read the Ansible docs, which are very well written, to be honest.

This process also allows me to get handy with my git skills, in order to
keep the commit history nice and clean.  As I learn things in my
experiences with Ansible, I'll add them into the playbook.  Nothing that
isn't idempotent will not be added into the playbook (ie, no one-off shell
scripts) unless possible, in order to keep the playbook clean.  Having 23
changed every time irritates me.

My next steps will adding a basic set of plays for a Debian environment,
with a couple of plays for CentOS, to demo the way you would handle
separate distros.

Hopefully, over the next few days, a basic playbook will be there, which
will make you easily able to customize it and provision a set of machines.

--------

There are 2 comments on this post:

Comment #1 by Example Ansible Playbook | Corey Reichle (  ) on 2015-04-21
23:45:44
[...] the Ansible demo playbook I had started in another post is finished.
 If you follow the steps here, you'll got from nothing to fully provisioned
[...]

Comment #2 by Backups! | Corey Reichle (  ) on 2015-10-19 00:26:38
[...] thankfully, the server is configured using Ansible, so I had the new
server deployed in about 9 minutes.  It even pulled down the last git
commit of [...]


To submit a comment on this post, email corey.reichle@gmail.com or visit us
on the web [ https://www.coreyreichle.com ].