Better Resource Efficiency with Cross Cluster eDRS

December 13, 2022

The elastic Distributed Resource Scheduler (eDRS) capability lets you scale your VMware Cloud on AWS clusters according to demand by adding or removing hosts automatically based on specific policies. This feature further extends the availability and resiliency of the SDDC cluster and removes the infrastructure operations burden from the customer.

eDRS helps with the optimum utilization of resources. However, the boundary for DRS is the cluster construct. Customers have multiple clusters for their business segregations, and cloud computing resources are shared within these clusters. The Cross Cluster eDRS capability helps customers to understand what clusters in their SDDCs can be scaled-in if there are clusters that are 'under-utilized'. By doing so, customers achieve the most optimal use of resources within their subscriptions.

Whenever eDRS recommends a scale-out for a specific cluster, depending on the eDRS policy, eDRS will proactively check cluster utilization for all clusters in a customer org. When it sees a cluster under-utilized, eDRS will send a notification by e-mail with the recommendation to scale in that specific cluster.

eDRS cross cluster recommendations

The workflow for cross-cluster eDRS recommendations is as follows:

  1. Find all the clusters in the organization.
  2. Retrieve resource utilization values for all clusters in all SDDCs.
  3. Filter out the clusters with scale in thresholds below CPU=65%, Memory=65%
  4. If candidate clusters are found, notify the customer about underutilized capacity in the candidate cluster.
  5. If no cluster is found with the agreed scale-in threshold values, find the cluster with the least corresponding resource utilization values and at least 4 hosts.
  6. Check if a potential host removal from that cluster would violate vSAN slack space requirements. If not, select the cluster as a candidate and notify the customer about underutilization.
  7. If vSAN slack space requirements are violated, then the workflow concludes that there is no candidate cluster for resource optimization.


eDRS cross cluster recommendation email

The recommendation by e-mail would look similar to this example. Remember, today the cross-cluster eDRS capability is recommendation only. Customers still need to manually remove a host from an under-utilized cluster. The goal here is to make sure all clusters and hosts are utilized most efficiently. Therefore we encourage customers to review the eDRS policies in the Cloud Console, as using the correct policy for your environment results in potential cost savings.

Associated Content

From the action bar MORE button.

Filter Tags

General Compute VMware Cloud on AWS Blog What's New Intermediate Optimize