Make your Ansible playbooks flexible, maintainable, and scalable - AnsibleFest Austin 2018 Presentation

Last year, at AnsibleFest Austin 2018, I presented Make your Ansible playbooks flexible, maintainable, and scalable. All the sessions at AnsibleFest were recorded, and I thought I'd be doubly safe since I presented my session on both days of AnsibleFest! Alas, due to some technical glitch, all the session recordings were lost, and so the only recordings available online today are those which were re-recorded by presenters.

As life happened... re-recording the session was put on the back burner. And after many months, I started to forget the structure of the presentation (I haven't given it since AnsibleFest), so I figured I might never get around to re-recording it at home.

Luckily, though, when I was running through Final Cut Pro to archive the previous years' completed projects, I found a practice recording of the session from the week before AnsibleFest. It was thankfully pretty good, and only needed a few slight edits:

It doesn't capture the feeling of the room as well as a live recording, but hopefully it conveys more helpful information than the slides alone (which I posted last year).

AnsibleFest Atlanta is fast approaching, and I'd love to see you there! I'll be presenting There's a role for that! How to evaluate community roles for your playbooks, and maybe I'll even get some time to finish pushing out the first part of Ansible for Kubernetes by then!


Hi Jeff, using Ansible playbook, I was trying to format, install, configure and open the luks_device using the plain-text keyfile but it at the level of opening the luks_device it won't work. I always end up getting the Key File / password error message. Can you please check and help. Thanks in advanced.

I'm not sure what luks_device is for (seems to be related to disk encryption), but I would imagine you'd be able to get support for it somewhere else (maybe in the Ansible Project mailing list), as it sounds like something that's more specific to your use case and not a general Ansible thing.