VMware vsphere 5.1 cluster Walkthrough (13) resource pooling and control

Cluster aggregation ESXi The capacity of the host into a large pool and provides an abstraction layer between the resource provider (ESXi host) and the resource consumer (virtual machine), which creates an additional abstraction layer that provides resources for sharing resource pools and isolating resource pools.

Complete isolation and resource sharing resources skilled use of allocation control: Reservations, shares and restrictions, these resource allocations set up resource allocation settings similar to virtual machines, explained in 12 chapters, how to set up work in the resource pool level? What is the impact of a virtual machine load?

Root resource pool

When DRS is enabled, the root resource pool is built at the cluster level, and whenever the ESXi host is added to the DRS cluster, the host's resources are added to the root resource pool, requiring that the resources running at the ESXi virtualization layer be unavailable to the cluster.

Total host Resources-Virtualization overhead = cluster available resources

If HA is enabled, the resources required to meet the HA failover are derived from the root resource pool. Because of the virtual seat in the root resource pool for ha failover, when viewing the capacity of a resource pool, the resources required to run the virtualization layer are not visible, and reserved resources are marked as HA failover to meet the HA resource requirements.

For example, if the cluster consists of 3 hosts, the root resource pool on the cluster contains a total of 36GB of memory resources, and each host provides 12GB of available memory

Figure 63: Root resource pool

Resource pools

As a cluster allocates resources from the host to the virtual machine, the host acts as the resource provider, the virtual machine acts as the consumer of the resource, and the resource pool plays the 2 roles because they consume the resources of the cluster and provide it to the virtual machine.

Figure 64: Resource providers and consumers

One important thing to realize is that a resource pool can be both a resource's consumer and a provider, from a shared perspective because it may affect your design of your resource pool.

Expand or shrink a resource pool

The resource pool spans the entire cluster, and when the host is added to the cluster, its resources are immediately added to the resource pool, and conversely, if the host is removed from the cluster, the resource provided by the ESXi host is subtracted from the cluster, and the resource will not be used by the resource pool and its child objects.

Note that removing the master opportunity will allow the cluster to be in an excessive state of resources, which occurs when the cluster resource does not meet the reservation of all resource pools, and the resources allocated to the virtual machine are reduced during excessive periods.

Local Host resource pool

Using a resource pool, you can partition the CPU and memory resources from the cluster to multiple levels, resources in a pool can be shared with other child objects while providing isolation between different resource pools, which can have two types of child objects: virtual machines or resource pools, and how are these resources shared or isolated?

The load of the virtual machine is performed by the local host CPU and memory scheduler, and the requirements settings for the resource pool are converted from the cluster level to the level of the ESXi host, in the previous section, DRS maps and mirrors the cluster resource pool tree to each host, and DRS allocates resources through the local host resource pool tree. By separating the available resources from the active virtual machines on the host and their dynamic quotas, the local host's CPU and memory scheduler takes care of the actual resource allocations once the resource pool allocation is propagated to the local host resource pool tree.

Tips

In Vsphere 5.0, vcenter specifically manages the resource pool structure, and in Vsphere 4.0, changes the local host resource pool

The structure overrides the management resource pool structure on the vcenter, and the Vcenter host view does not match the actual resource schema on the host, which can also have unpredictable effects.

When a resource is already managed by the DRS, in order to prevent users from directly connecting to the host to modify the resource settings, the resources are not modified to allow execution, in which case all resources are set to read-only and vcenter displays the following information.

Figure 65: Host Management