VMware Cloud Community
twoton
Enthusiast
Enthusiast

Help Understanding Resource Pool Memory Capacity

Hello-

We have our environment set up in a multi-tenant way, with resource pools at the root of the cluster to grant each tenant a guaranteed amount of memory and CPU.  Memory is managed by configuring limits to the amount each tenant can use.  If I look at a given resource pool in vRO, the configured capacity is way lower than the actual limit.  For instance, one of the top level resource pools has a configured limit of 1.2TB.  It has 3 child resource pools, 2 of which have their own memory limits and one of which is unlimited.  If I look at the RP in vRO --> ANalysis --> Capacity Remaining tab, it shows 0 KB configured in Total Capacity despite showing the correct 1.2TB configured memory limit.  If I look at Child1 RP, it shows the configured limit of 355GB but a configured capacity of 65.88 GB.  Child 2 is unlimited, 355GB configured, and child 3 is 455GB limit with 158GB configured.  Most of this is no big deal, but child 3 shows red alerts for capacity remaining and 0 days left because it recommends a size of 160GB. 

How is vRO calculating the capacity configured?  I've looked around in the policy settings but it's not immediately clear to me.  Is there a way to tell it to use the limits as the capacity configuration?  My main goal is to eliminate the false alarm condition on capacity remaining, but I think in order to have more useful capacity remaining alerts, it would be best to have configured capacities that more closely match what the RP memory cpacity limits actually are.  Any help is appreciated, thanks.

1 Reply
twoton
Enthusiast
Enthusiast

Here's a screenshot of child3 to help illustrate what I am talking about.  Notice the 458GB memory resource limit configured in the right pane, but vRO shows there is no room left to grow because memory only has 159GB configured and it needs more.  Does anyone know why this is happening?

vro.png