The Capacity tab provides Time Remaining and Capacity Remaining data for the selected object. Virtual Machine Remaining data is available for datastores, datastore clusters, clusters, data centers, CDC, and VC based on the average profile, or when you enable one or more custom profiles in the policy.
Where You Find the Capacity Tab
- From the left menu, click Environment, then select a group, custom data center, application, or inventory object. The Object details screen appears. Click the Capacity tab.
- From the left menu, click Troubleshoot, and then select Alerts to display the All Alerts screen. Click an alert to show the alert details on the right, then click View Additional Metrics to see more information about the alert and the object that triggered the alert. Click the Capacity tab.
Understanding the Capacity Tab
For the selected object, the Capacity tab lists two panes with the Time Remaining and Capacity information. These panes display the value of the resources remaining till they run out.
Below the Time Remaining, Capacity and Virtual Machine Remaining panes, the time and capacity utilization metric for CPU, memory, and disk space are displayed in three panes. By default, the most constrained resource is selected. Click CPU, Memory, or Disk Space to change the views to these resources. These panes display the resource information based on the Demand model (default) or Allocation model (if configured).
For datastores, if you have enabled Allocation Model and Capacity buffer in the assigned profile, you see the Disk Space information based on Allocation and Usage.
- Time Remaining Pane
When you select the Time Remaining pane and click one of the resource types, the utilization graph displays the historical value of the utilization metric and its forecast plotted against time, projecting how swiftly resource utilization is approaching the usable capacity.
RESET in the
Time Remaining pane if you want to change the date from when the historical utilization is calculated. By default, it is calculated from the object creation or
vRealize Operations installation date. When you click
RESET, you can change the date from which
vRealize Operations calculates historical utilization.
This affects the capacity calculation for the future trend, which will impact Capacity Remaining, Time Remaining, Recommended Size, and VM Remaining (if it is available for the particular resource, namely, Datastore, Cluster, Datastore Cluster). It will also impact all the resource containers (CPU, Memory, Disk Space, etc.)
- For example, if the capacity calculation is using historical data based on the duration when you were provisioning a large number of VMs, but in the recent past, there was no provisioning done. Then, vRealize Operations may not project a trend that is based on the recent data when there was no provisioning, but still will consider historical data when there were a large number of VMs provisioned. In this case, you can change the capacity computation to start from a date after the VM provisioning is complete.
Note: If you are unable to see the RESET button in the Time Remaining pane, make sure you have the Manage Capacity Calculation permission under
- Capacity Pane
The Capacity Remaining pane indicates the unused capacity of your virtual environment to accommodate new virtual machines. vRealize Operations calculates the Capacity Remaining as a percentage of the remaining capacity, compared to the total. Capacity Remaining is calculated as the utilization metric forecast 3 days from now subtracted from the Usable Capacity. vRealize Operations calculates the average profile and always computes the virtual machine remaining number based on the average profile. You can change the profile by clicking the + icon above the bar chart. vRealize Operations calculates virtual machine remaining numbers when you enable one or more custom profiles from the policy. The overall virtual machine remaining is based on the most constrained profile.
When you select Capacity and click one of the resource types, a bar chart and a table of values based on the Demand and Allocation model (if configured) appears. The bar chart displays total usable resource, the percentage used, the percentage allocated for high availability and buffer, and the percentage remaining based on the Demand and Allocation models (if configured).The table displays the following information for each resource type:
- Total: The total usable capacity for each resource type based on the Demand model or Allocation model (if configured). The difference in Total capacity and Usable capacity is set in the HA (admission control) that is set in the clusters in vSphere.
- Usable: The total usable capacity for each resource type based on the Demand model or Allocation model (if configured).
- Used: Approximate value how much utilization do you have now. Shows the forecast value of utilization metric in 3 days from now. If Capacity Remaining is greater than zero, then Used = Usable - Capacity Remaining.
- Recommended Size:The Total Capacity that must be available for a green level of Time Remaining. The slider in the policy controls the Time Remaining green zone, and the default value is 150 days.
- Remaining: The Capacity Remaining metric value and also the percentage. The value of Capacity Remaining metric is calculated by forecasting the utilization metric 3 days from now and subtracting it from Usable capacity.
- Buffer: The percentage of the capacity buffer based on the buffer value that you set in the policy. The Capacity Buffer element determines how much extra headroom you have and ensures that you have extra space for growth inside the cluster when required.
- High Availbility: The percentage of the high avaibility based on the high availability buffer.
- Virtual Machine Remaining
- The virtual machine remaining number is based on the average profile. The virtual machine remaining numbers are calculated when you enable one or more custom profiles from the policy. The overall virtual machine remaining is based on the most constrained profile.
- When you click on Virual Machine Remaining, you see the number of virtual machines based on the Average Profile. Click the + sign next to the number of virtual machines to add a different profile.
- Only vSAN datastore objects, and not other datastore objects, display disk space based on Buffer and HA.
The Capacity tab is a subset of the Capacity optimization capability. For additional details, refer to Optimize Capacity.
Capacity VM Shortfall
vRealize Operations has a new metric known as VM shortfall, the VM shortfall value is always positive. The metric counts all the negative VMs Remaining and then turns them into positive. The VM shortfall metric will be available for Clusters, Datastores, and Datastore Cluster objects only. The VM Shortfall metric details is displayed in the Capacity Summary pages next to VM Remaining, in case if VM Remaining is equal to zero.
For all these objects you can create custom profiles directly from the capacity page. In the Capacity tab, click the + sign under Virtual Machine remaining. From the Applicable Profiles page, click Add to add a new profile. You can either add new profile or import from existing object. You can modify the required metric value and click OK.
How Does VM Shortfall Work
When the cluster has more VMs than its usable capacity can handle, the shortfall of capacity is shown by the VM counter. VM remaining will show zero and not negative. The shortfall appears only when the usable capacity is zero.
Whenever there is no capacity in that case, VM shortfall detects the VM profiles in the setup and finds the profile for which we have the maximum number of VMs that are overcommitted.
VM Shortfall Formula
It is possible that when one datastore is connected with multiple clusters, each cluster thinks that the whole diskspace available in the datastore is for itself. We can calculate the VM shortfall as:
VM Shortfall = (Used - Usable Capacity) / Profile Sizes
If you have two clusters, one cluster has 20 VMs remaining and the other cluster has shortfall of 20 VMs, then the number of VMs remaining for the datacenter will be 20 VMs, however, if you have a shortfall of VMs in the datastore connected to that cluster, then we will see on the datacenter the remaining VMs as zero.
- Capacity Remaining Profile (Average)
- Capacity Shortfall Profile (Average)
vSAN HCI Mesh
The vSAN HCI Mesh allows vSAN clusters to remotely mount the datastore of another (remote) vSAN cluster, hence sharing the storage capacity and span its usage to a wider pool of compute resources. HCI Mesh allows multiple vSAN clusters to share their datastores remotely. If the vCenter version is 7.0U1 and greater you can share other cluster datastores and provision VMs to the remotely shared data stores.
A new card is created under. The vSAN HCI Mesh card is displayed only when there are eligible clusters which can be part of the vSAN HCI mesh. If the version of the vCenter is less than 7.0U1 for the selected datacenter, this card is not displayed. If the mesh is not configured, click the link, which lets you configure the clusters from vCenter.
- Total Capacity - Displays the total capacity of all the vSAN datastores connected to the mesh.
- vSAN Mesh - Displays how the datastores are interconnected in the HCI mesh.
- Inner Circle - Represents the local datastore and displays capacity details like, free capacity, used capacity, and total capacity.
- Outer Circle - Represents the remote datastore and displays capacity details like, total mounted capacity, free capacity, and total capacity usage percentage.
- Arrow Heads - The arrow heads points to the clients connected to the server vSAN cluster.
- Datastore View
- Displays the capacity consumption details for the selected datastore. You can also identify which are the client and server clusters.
- Cluster View
- Displays the capacity details of the remote datastores. You can also view the capacity details for the mounted datastores. The Total Usage % displays the total capacity consumed by all the client clusters connected to these mounted datastores including the selected cluster.