I regularly consume resources from the VMware vCenter private cloud setup here at ElasticBox. I’m not alone in that. vCenter is the most commonly used private cloud out there. Enterprises and developers, you will see why the changes we recently made will help you scale automated deployments in vCenter.
Those of you deploying to vCenter, you know about datacenters, templates, hosts, clusters, resource pools, compute resources, datastores, and such. ElasticBox simplifies vCenter deployments by abstracting these infrastructure metadata from application metadata in boxes. Infrastructure metadata is in the deployment profile that you select right before deploying. Here we made it easy to visualize exactly where in the vCenter you’d like to place your VM and consume resources.
Placing your VM
Until recently, to deploy an instance in vCenter, you selected a datacenter and from it a resource pool and virtual network. If you had several clusters or standalone hosts not part of a resource pool, you did not see them. Now you do.
Now you see even the clusters and standalone hosts not part of a resource pool in a datacenter. In effect, you can place your VM in a resource pool, a cluster, or a standalone host provided they exist of course.
Allocating the right resources
While you do that, you can also place the VM inside a folder if they are there in the datacenter. With these enhancements, you get more control over where you allocate resources and locate your instance.
Finding resources easily
Finally, we added a small but handy feature. When the list of compute resources exceed 10, you can search to look them up quickly rather than scroll. The search is also available when you try to locate a datastore for default and additional disks you add to the instance.