Imagine you work in an environment with more than 1500 virtual machines and the numbers are still rapidly growing. When you work with a lot of resource pools, it’s an administrative burden to recalculate all your pools after you have deployed new virtual machines. The Dynamic Resource Pool Calculator recalculates all your resource pools. Depending on the numbers of virtual machines per resource pool, the resource pool reservations for memory and CPU are automatically lifted. The script also respects the existing individual virtual machine reservations and adds those value’s to the total RP sum. When you start the script and logon to an ESX or Virtual Center server with some resource pools present, you will see a real Windows user interface and the script will actually talk to you.
I'd like to better understand the resource pool use case for which this tool is targeted. It seems like the tool is meant to be used in situations where the reservation setting of a resource pool is completely determined by the size and reservations of the VMs in the pool. If that is correct, then what is the main benefit of using resource pools in such an environment? Why not put the VMs in folders instead, and make sure that each individual VM's reservation is set correctly?
Please educate me.
Thanks
Ulana Legedza