Create a local, temporary file of the new hosts and environment variable
ANSIBLE_INVENTORY?
Mike
> On Aug 16, 2019, at 00:34, Zolvaring wrote:
>
> I'm not sure I understand fully, but none of the hosts you are configuring
> need Ansible to be installed for you make changes remotely. Instead o
Seeing that you may want to loop through actual guests, I would still define
them as Ansible inventory hosts if you know them ahead of time, and if you need
to run tasks from a different host by invoking VMware module then try:
- name: do a thing to a guest
vmware_module:
regular_module_ar
I'm not sure I understand fully, but none of the hosts you are configuring need
Ansible to be installed for you make changes remotely. Instead of defining your
hosts in a CSV, define your hosts as part of Ansible inventory and your tasks
will loop through them naturally. You can also group hosts
I'm not sure I understand fully, but none of the hosts you are configuring
need Ansible to be installed for you make changes remotely. Instead of
defining your hosts in a CSV, define your hosts as part of Ansible
inventory and your tasks will loop through them naturally. You can also
group hosts as
I intend to Ansible to run deployment configuration on a number of Dell
ESXi hosts in VMware using VMware and OpenManage modules.
In my past ansible training, my playbooks have always run from hosts that I
have defined in an inventory file. The machines I wish to configure don't
have ansible in
