# VMware module to change CD rom from iso to client

**URL:** <https://forum.ansible.com/t/vmware-module-to-change-cd-rom-from-iso-to-client/38538>\
**Category:** Ansible Project\
**Tags:** vmware, aap\
**Created:** [October 20, 2023, 12:28pm UTC](https://forum.ansible.com/t/vmware-module-to-change-cd-rom-from-iso-to-client/38538 "2023-10-20T12:28:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kris\_Smith](https://avatars.discourse-cdn.com/v4/letter/k/5f9b8f/32.png) [@Kris\_Smith](https://forum.ansible.com/u/Kris_Smith)\
**Post date:** [October 20, 2023, 12:28pm UTC](https://forum.ansible.com/t/vmware-module-to-change-cd-rom-from-iso-to-client/38538/1 "2023-10-20T12:28:10Z")

</div>

So we have a workiing deploment for our VM’s using AAP. What I am trying to do is as the last step after everything is done, is change the cd from the bootable iso file we use to kickstart everything, back to client device. I cannot figure out how…

What I have attempted to do (since I really don’t know scripting) is edit one of the existing yml files which turns the VM on after all the infoblox and firewall objects are created…

Is there even a way using Ansible to just wait 30 min after the VM is powered on for it to do the full deploy, then set the CD-ROM back to client device?

---

<div class="post-metadata">

**Author:** ![Will\_McDonald](https://avatars.discourse-cdn.com/v4/letter/w/f475e1/32.png) [@Will\_McDonald](https://forum.ansible.com/u/Will_McDonald)\
**Post date:** [October 23, 2023, 2:30pm UTC](https://forum.ansible.com/t/vmware-module-to-change-cd-rom-from-iso-to-client/38538/2 "2023-10-23T14:30:08Z")

</div>

This is pretty much what wait\_for and wait\_for\_connection are designed to handle.

[https://docs.ansible.com/ansible/latest/collections/ansible/builtin/wait\_for\_connection\_module.html](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/wait_for_connection_module.html)  
[https://docs.ansible.com/ansible/latest/collections/ansible/builtin/wait\_for\_module.html](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/wait_for_module.html)

If you can key off a condition that indicates the provisioning has complete (i.e. we can SSH in, or validate from an API, or check a log entry), then you could continue through to switch the connected device.