Describe the Resource Pool hierarchy
- Root Resource Pool
A resource pool can contain other resource pools, vApps, and VM's. vApps and VMs share the same type of hierarchy, meaning if a VM is at the same level as a Resource Pool, they are considered to be siblings.
Why Use Resource Pools?
- Flexible Hierarchical Organization – Resource Pools give you the ability to lay out resources the way you want, and dynamically change them on the fly.
- Isolation Between pools, sharing within pools – Could assign pools to departments, changes in resources in one pool would not affect others.
- Access Control and Delegation – Could delegate administrative rights to one resource pool to someone, and thus that person would have access to create and manage resource pools within the top level resource pools
- Separation of Resources from Hardware – Resource from all hosts will be assigned to the cluster, thus allowing them to share resources.
- Management of Sets of VMs running as a multi-tiered service – group VMs from a multi-tiered service in a RP, which would allow you to allocate resources to the service by just changing on the the RP, not each individual VM
Define the Expandable Reservation parameter
- Select the object on which you wish to create the RP in and select File->New->Resource Pool
- Name the resource pool
- Specify how to allocate CPU and Memory resources.
- Shares – Assign shares to a RP just as you would a VM that will draw from its parent resource pool. Options are Low, Medium, and High in a 1:2:4 ratio as well as custom
- Reservation – Guarantees a certain amount of physical CPU and Memory to the resource pool. This is defaulted to 0
- Expandable Reservation – explained above.
- Specifies the upper limit of the hosts memory and cpu that it can use. Normally left at unlimited
Configure Resource Pool attributes
- The virtual machines reservation and limit do not change. If a reservation or limit was set on the VM, it is maintained.
- If the VMs shares are set to low, medium, or high, then the % shares value will adjust accordingly depending on how many shares are available in the resource pool.
- If the VMs shares value is set to a custom value, that number is maintained. You may need to change the shares value after this as it is now relative to the resource pools total shares. A warning is generated if a VM is going to receive a very high or a very low amount of shares.
- The resource allocations tab will change to reflect the values of the new VM (reserved and unreserved capacity). This only happens if the VM is powered on. Powered off VMs will not reflect in these values.
Removing a VM from a Resource Pool
When you remove a VM from a Resource Pool the overall number of shares for the Resource Pool decreases, however each share will then represent more resources. You can remove a VM from a resource pool by either deleting it, or simply moving it out of the RP.
- You must be connected to vCenter
- A host must be selected in the inventory that is 3.0 or greater OR a DRS enabled cluster must be selected.
The cloning is quite simple and much the same as cloning a VM. Select Inventory->vApp->Clone. Select a destination, a new name, a datastore, a network, you're done!