Things I wish I knew about Ansible from day 1

When starting to learn anything new there are also tricks and tips the pros know that you'll eventually wish you knew when you started out. In this video I share those pro tips for Ansible to make you a better DevOps engineer from day 1.

[sharhanalhassan]

Key recommendations highlighted;
1. Roles 0:39
2. Use Playbooks to represent a solution 2:01
3. Inventories and Group variables 3:19
4. Ansible vault 5:59
5. Modules 7:30

[herdenq]

Thanks for the info. Your presentation would be a lot easier for me to digest if you were to include screenshots to illustrate what you are talking about. Cheers

[deladonics]

Dude. This is high value video. Every tip is has your built in hours of using this. I have an idea for the vault now in our k8s flow at work too. Excellent

[alain]

i would add molecule to the list and vscode dev containers this shorten dev times with 50%

[praecorloth]

Good stuff. I've made a dynamic inventory plugin that queries Nagios XI. One of the things I found INCREDIBLY helpful in this integration is that groups and vars in Ansible tie in quite nicely with hostgroups and host free variables in Nagios XI. So in XI, I can create a template with Ansible specific variables, pull the hosts, hostgroups, and variables out via the API, and then use all of it in Ansible roles and playbooks.

It makes so much sense. You want to monitor all your shit, right? That's where Nagios comes in. Might as well use it as your management database.

[marcinzpola]

Great video, thanks! Keep going :) Cheers

[lasseprimdahlsteffensen]

oh i can make my own modules? interesting.

[mohammedalzahrani]

Ansible vault is awesome. For me I was creating separate inventory file for each environment then selecting inventory file when running playbook. Is this a bad practice?
I was wondering what is the equivalent of Ansible for Windows Servers ?
Thanks for this video.