Ansible for VMware Concepts
Some of these concepts are common to all uses of Ansible, including VMware automation; some are specific to VMware. You need to understand them to use Ansible for VMware automation. This introduction provides the background you need to follow the scenarios in this guide.
Any machine with Ansible installed. You can run commands and playbooks, invoking
/usr/bin/ansible-playbook, from any control node. You can use any computer that has Python installed on it as a control node - laptops, shared desktops, and servers can all run Ansible. However, you cannot use a Windows machine as a control node. You can have multiple control nodes.
Delegation allows you to select the system that executes a given task. If you do not have
pyVmomi installed on your control node, use the
delegate_to keyword on VMware-specific tasks to execute them on any host where you have
The units of code Ansible executes. Each module has a particular use, from creating virtual machines on vCenter to managing distributed virtual switches in the vCenter environment. You can invoke a single module with a task, or invoke several different modules in a playbook.
Ordered lists of tasks, saved so you can run those tasks in that order repeatedly. Playbooks can include variables as well as tasks. Playbooks are written in YAML and are easy to read, write, share and understand.
Ansible VMware modules are written on top of pyVmomi.
pyVmomi is the official Python SDK for the VMware vSphere API that allows user to manage ESX, ESXi, and vCenter infrastructure.
You need to install this Python SDK on host from where you want to invoke VMware automation. For example, if you are using control node then
pyVmomi must be installed on control node.
If you are using any
delegate_to host which is different from your control node then you need to install
pyVmomi on that
You can install pyVmomi using pip:
$ pip install pyvmomi