You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to the support for including/excluding Folder values based on Managed Object ID (MOID), we can provide the same support for including/excluding ResourcePool values.
This would allow excluding the Resources parent pool from another cluster or host in the same datacenter.
Context
I recently encountered a scenario where a new offsite host (ComputeResource) was added to an existing vSphere Datacenter that was not made part of the same existing cluster (ClusterComputeResource). This added another "parent" resource pool to the mix also named Resources.
If we try to exclude the Resources pool by name we could end up matching both the Resources pool in the cluster and the Resources pool associated with the new non-clustered host.
Once support is available for filtering based on ResourcePool MOID we can reliably exclude the host-based Resources pool.
Overview
Similar to the support for including/excluding
Folder
values based on Managed Object ID (MOID), we can provide the same support for including/excludingResourcePool
values.This would allow excluding the
Resources
parent pool from another cluster or host in the same datacenter.Context
I recently encountered a scenario where a new offsite host (
ComputeResource
) was added to an existing vSphere Datacenter that was not made part of the same existing cluster (ClusterComputeResource
). This added another "parent" resource pool to the mix also namedResources
.If we try to exclude the
Resources
pool by name we could end up matching both theResources
pool in the cluster and theResources
pool associated with the new non-clustered host.Once support is available for filtering based on
ResourcePool
MOID we can reliably exclude the host-basedResources
pool.References
Folder
Managed Object ID (MOID) #809The text was updated successfully, but these errors were encountered: