Section 5 - Administer and Manage vSphere 6.x
Resources
Objective 5.1 -
Configure Advanced/Multilevel Resource Pools
Describe a
Resource Pool hierarchy:
- By default, all resources for a host or cluster will
exist in the root resource pool
- In the resource pool hierarchy, there are 3 types of
resource pools:
-- parent (root is the
parent)
-- siblings
-- child
IMPORTANT: Don’t
use resource pools as a way to logically group virtual machines (use folders
for this)
Note: The
‘expandable reservation parameter’ allows a child resource pool to ask its
parent for more should the child need it.
Describe vFlash
architecture:
- vFlash Read cache allows for integrations and
management of flash devices that are locally attached to ESXi servers
- vFlash enables pooling of one or more flash devices
into a single pool of flash resources
- vFlash allows for write-through caching mode (read
cache)
- vFlash provides read caching on a per-vmdk basis
- When enabling vFlash on a vmdk, a subset of the vFlash
resource pool will be placed in the data path for that VMDK
- A VM must be powered on for data to be sitting in the
vFlash cache
- Requires Enterprise+ licensing
- Works with HA and DRS - migrate cache or not (rewarm)
Note: vFlash
Resource Pool configured via “Virtual Flash Resource Management” and “Virtual
Cache Host Swap Cache Configuration”
Note: Assign vFlash
resources to VMDKs via VM > Edit Settings > “Virtual flash read cache”
Evaluate
appropriate shares, reservations, and limits for a Resource Pool based on
virtual machine workloads:
- Shares: The
amount of shares you allocate to a resource pool are relative to the shares of
any sibling and relative to its parent’s total resources
- Reservations
are the minimum amount of resources the resource pool will get
Note: Contention
occurs if you have overcommitted the resources in your DRS cluster, or during
short-term spikes.
- Expandable
reservations gives you flexibility
- Limits is
the maximum amount of resources a resource pool can have
Comments
Post a Comment