community.vmware.vmware_host_inventory inventory – VMware ESXi hostsystem inventory source
Note
This inventory plugin is part of the community.vmware collection (version 1.18.2).
You might already have this collection installed if you are using the ansible package.
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install community.vmware.
To use it in a playbook, specify: community.vmware.vmware_host_inventory.
New in version 1.11.0: of community.vmware
Synopsis
Get VMware ESXi hostsystem as inventory hosts from VMware environment.
Uses any file which ends with vmware.yml, vmware.yaml, vmware_host_inventory.yml, or vmware_host_inventory.yaml as a YAML configuration file.
Requirements
The below requirements are needed on the local controller node that executes this inventory.
Python >= 2.7
PyVmomi
requests >= 2.3
vSphere Automation SDK - For tag feature
Parameters
Parameter |
Comments |
|---|---|
Toggle to enable/disable the caching of the inventory’s source data, requires a cache plugin setup to work. Choices:
Configuration:
|
|
Cache connection data or path, read cache plugin documentation for specifics. Configuration:
|
|
Cache plugin to use for the inventory’s source data. Default: “memory” Configuration:
|
|
Prefix to use for cache plugin files/tables Default: “ansible_inventory_” Configuration:
|
|
Cache duration in seconds Default: 3600 Configuration:
|
|
Create vars from jinja2 expressions. Default: {} |
|
This option allows client-side filtering hosts with jinja templating. When server-side filtering is introduced, it should be preferred over this. Default: [] |
|
Add hosts to group based on Jinja2 conditionals. Default: {} |
|
Name of vCenter or ESXi server. Configuration:
|
|
A list of templates in order of precedence to compose inventory_hostname. Ignores template if resulted in an empty string or None value. You can use property specified in properties as variables in the template. Default: [“name”] |
|
Add hosts to group based on the values of a variable. Default: [{“key”: “summary.runtime.powerState”, “separator”: “”}] |
|
The default value when the host variable’s value is an empty string. This option is mutually exclusive with |
|
The key from input dictionary used to generate groups |
|
parent group for keyed group |
|
A keyed group name will start with this prefix Default: “” |
|
separator used to build the keyed group name Default: “_” |
|
Set this option to False to omit the This option is mutually exclusive with Choices:
|
|
Use in conjunction with keyed_groups. By default, a keyed group that does not have a prefix or a separator provided will have a name that starts with an underscore. This is because the default prefix is “” and the default separator is “_”. Set this option to False to omit the leading underscore (or other separator) if no prefix is given. If the group name is derived from a mapping the separator is still used to concatenate the items. To not use a separator in the group name at all, set the separator for the keyed group to an empty string instead. Choices:
|
|
Password of vSphere user. Accepts vault encrypted variable. Configuration:
|
|
Port number used to connect to vCenter or ESXi Server. Default: 443 Configuration:
|
|
Specify the list of VMware schema properties associated with the ESXi hostsystem. These properties will be populated in hostvars of the given ESXi hostsystem. Each value in the list can be a path to a specific property in hostsystem object or a path to a collection of hostsystem objects.
Please make sure that all the properties that are used in other parameters are included in this options. In addition to ESXi hostsystem’s properties, the following are special values Use Use Default: [“name”, “customValue”, “summary.runtime.powerState”] |
|
Address of a proxy that will receive all HTTPS requests and relay them. The format is a hostname or a IP. This feature depends on a version of pyvmomi>=v6.7.1.2018.12. Configuration:
|
|
Port of the HTTP proxy that will receive all HTTPS requests and relay them. Configuration:
|
|
A list of resources to limit search scope. Each resource item is represented by exactly one Key name is based on snake case of a vim type name; e.g Default: [] |
|
If Since it is possible to use facts in the expressions they might not always be available and we ignore those errors by default. Choices:
|
|
Merge extra vars into the available variables for composition (highest precedence). Choices:
Configuration:
|
|
Name of vSphere user. Accepts vault encrypted variable. Configuration:
|
|
Allows connection when SSL certificates are not valid. Set to Choices:
Configuration:
|
|
This option transform flatten properties name to nested dictionary. Choices:
|
|
Include ESXi hostsystem’s path. Set this option to a string value to replace root name from ‘Datacenters’. Choices:
|
|
This option allows property name sanitization to create safe property names for use in Ansible. Also, transforms property name to snake case. Choices:
|
|
Include tags and associated hosts. Requires ‘vSphere Automation SDK’ library to be installed on the given controller machine. Please refer following URLs for installation steps https://code.vmware.com/web/sdk/7.0/vsphere-automation-python Choices:
|
Examples
# Sample configuration file for VMware Host dynamic inventory
plugin: community.vmware.vmware_host_inventory
strict: False
hostname: 10.65.223.31
username: [email protected]
password: Esxi@123$%
validate_certs: False
with_tags: True
# Using compose
plugin: community.vmware.vmware_host_inventory
hostname: 10.65.223.31
username: [email protected]
password: Esxi@123$%
validate_certs: False
properties:
- name
- summary
- config.lockdownMode
compose:
ansible_user: "'root'"
ansible_connection: "'ssh'"
Authors
Abhijeet Kasurde (@Akasurde)
Hint
Configuration entries for each entry type have a low to high priority order. For example, a variable that is lower in the list will override a variable that is higher up.