As per the Ansible documentation: An ad-hoc command is something that you might type in to do something really quick, but don’t want to save for later. For example, if you want to you can test a module, (e.g IOS_Facts), without having to write a Playbook by using Ad-Hoc commands such as this: ansible all -i 192.168.0.210, -c local -m ios_fact...
The Ansible tag documentation does a great job of explaining tags, tag re-used and tag inheritance. However, I’d like to dive a little deeper to show you just how useful they can be. To get the most out of this post you’ll need to be familiar with the ways in which you can structure your Playbooks. If you don’t know how they can be structured,...
I published my Ansible Playbook Structure post a few months ago. Upon re-reading it recently I felt that it lacked detailed around the components of a playbook. I therefore intend to fill in the gap with this post. 30,000 Foot View Ansible uses the following components to work: Inventory file(s) Group vars Host vars Playbooks Roles...
In Part 2 of this series we made our first API call and received over 200 lines of XML as a result. The reason why we received so much output is because we didn’t remove any desired-attributes and therefore the call retrieved about 90 pieces of information. When you multiply that by the number of queries we ran (2), you get 180 pieces of inform...
Picking up where I left off in Part 1 of this series, let’s continue our exploration of ZExplore :) Mandatory Parameters In part 1 I touched on the fact that the API documentation can be a little confusing when it comes to mandatory fields. Unfortunately the same is true for ZExplore. However, NetApp’s documentation explains it well: Red colo...