I installed the vSphere cloud plugin and was able to connect to my vSphere Cloud using the Test Connection button. But my build job kept failing with an Unable to find SourceName or something along those lines.

My goal is to create VMs from templates, but I ran into a few snags along the way.
I am using the VMware vSphere Essentials with VSA product from VMware. This is an SMB product which uses internal storage as a Virtual SAN or Virtual Storage Appliance. The license does not support DRS and therefore I cannot define resources pools.

The vSphere Essentials does create a VSA HA Cluster, which seems to me to be a root resource pool, although I am not sure how to specify it in a way that jenkins will like.

I was able to get my build job to work finally by specifying a separate ESX host, which is not part of the VSA cluster and creating a resource pool on that.
Now I'm thinking It might make sense just to get a separate ESX host which is dedicated to on-demand build systems.
I guess as long as the host is managed by my vCenter server, this should work.
I have only one vCenter server and so this isn't really a cluster, but that doesn't seem to matter. So I have two questions really:
Given that it is not possible to create a resource pool with vSphere Essentials, is there a way to specify root resource pools which are there by default?
What is the downside to using a standalone ESX host for on-demand build systems? I call them on-demand, meaning that I can create templates for base systems that can be modified and managed by users.

Thanks,

Lisa