Sometimes a customer's environment is much slower than we planned for.  We saw a scenario where disk moves and copies were taking several hours while still completing successfully.  The vSphere connector was timing out much earlier, though.  The ability to configure the timeouts is in 4.3 and all later versions.

---

Instructions

The config file is called:  /usr/local/lib/node_modules/unidesk-vsphere-connector/config.json

If you are not already familiar with EMACS or vi as text editors, you may fine "nano" is most usable.  Login as root, and enter this command:

nano /usr/local/lib/node_modules/unidesk-vsphere-connector/config.json

The section with the timeouts, by default, looks like this:

"vsphereTimeouts": {
  "defaultTimeoutInSec": 600,
  "moveVirtualDiskTimeoutInSec": 7200,
  "copyVirtualDiskTimeoutInSec": 1200
}

Here's what they do:

moveVirtualDiskTimeoutInSec: Time in seconds to wait for hypervisor to convert to a sparse disk.  This happens after the connector uploads a new disk when publishing an image or a creating a new packaging machine.

copyVirutalDiskTimeoutInSec: Time in seconds to wait for hypervisor to make a clone of a cached disk.  This happens when a new packaging machine is deployed from the cache on the hypervisor.

defaultTimeoutInSec: Time in seconds to wait for all other hypervisor actions such as powering a VM on/off, deleting a VM, re-configuring a VM, creating/cloning a VM and searching for a VM.

After you edit the config file and save it, simply reboot the ELM.

The timeouts for the vSphere Connector are configurable starting in 4.3. You will need to edit a config file and restart the connector.