This question comes up a lot and only recently did I ask this of engineering and the answer is quite simple. We all know that Preparing a host for vCloud Director essentially installs the vCloud Director Agent onto ESXi. However, the secondary question that usually gets asked is, “What does the vCloud Director Agent actually do?” I decided to ask that and I was also told I could publish the answer. Frankly, the answer is quite simple really.
The vCloud Director Agent is used for two things:
- Communicating with the cross host fencing vmkernel module that is installed when the agent is pushed. This is needed when you use VCD-NI network pools.
- Retrieving virtual machine thumbnails
I was pretty sure I knew about the VCD-NI aspect I just forgot about it. The image thumbnails on the other hand was quite news to me. Either way, now we know what the vCloud Director Agent does once it is installed as part of the host preparation. For information on ways to manually remove the agent see the related posts below.
Hi Chris,
You can check that when using esxcli and the vcloud namespace 🙂
Regards,
Hi there,
I’m using the VCA, but I don’t find the vcloud agent in the directory of my esxi (opt/vmware….). Neither, the directory vcloud-directo does not appear.
I’m trying to install the agent manuelly, because the vCD wasn’t able to install itself, due to some ESXCLI problem.
I’m counting on your help.
Best Regards,
Anouar HNINI
Depending on the version of ESXi the agent installs differently. You can see from my other article on how to remove the agent manually it differs by ESXi version. If you are having trouble I would suggest a call into support as there may be something else wrong. I have never personally had a host not get the agent installed from the Cell.