To help you manage your virtual infrastructure, Embotics® vCommander® tracks the average and peak capacity of your hosts and clusters. This data is used to make the best choice for deployment placement and to provide operators with the information shown on the Capacity & Waste Reclamation solution page.

VM Workloads

Embotics vCommander measures capacity in VM workloads, which are operational baselines for how much CPU, Memory and Storage are expected to be consumed by a VM. The VM workload as configured out of the box is:

CPU (GHZ): 0.5
Memory (GB): 0.5
Storage (GB): 8.0

When working at the global level, you can use the defaults or set new values based on what you know about your virtual environment. You can also override the global defaults for each cluster or host. When overriding the global values you can also calculate the averages based on the previous 7 days’ resource consumption by VMs on that cluster or host.

To update the global values:

  1. Under the Configuration menu, choose System Configuration.
  2. Switch to the Capacity tab.
  3. Under Typical VM Workload click Edit.
  4. Set new values for CPU, Memory and Storage and click OK.

To override the global values:
  1. Choose a cluster or host with which to work. You can only configure the override for a standalone host or a cluster, not each host in a cluster.
  2. Right-click the cluster or host and choose Set VM Workload.

  3. Choose Use Overridden VM Workload and enter the values you want for the cluster or host. Alternatively, click Calculate Average to populate the fields based on averages across the previous 7 days.
  4. Click OK,

Important! The current capacity information is not updated immediately when you change the typical VM workload.

Constraining Resource

In most cases, whenever Embotics vCommander reports remaining capacity to users, it will also indicate the constraining resource. Constraining resources show whether the capacity is most limited by the available CPU, memory or storage space available for new virtual machines.

Looking at the chart above, the remaining capacity for the five stand-alone hosts represented is 35 VM workloads, constrained by CPU and memory. This means there is storage space available for more than 35 VMs, but the CPU and memory will limit the placement of further VMs, to help you avoid over-provisioning and impacting your users.

You can view all the hosts under a single cloud account (managed system) by selecting the cloud account (managed system) and switching to the Hosts tab. This view provides an excellent overview of the capacity of each host and what its constraining resources are. As with any listgrid in Embotics vCommander you can add many useful columns, including one that will display to which cluster the host belongs.

Updating Capacity

Capacity information is updated when:

  • A managed system is connected or disconnected
  • A cluster or host is added
  • You manually update capacity by choosing Update Performance and Capacity for a cluster or host

Capacity information is not updated when:

  • You update the global value for Typical VM Workload
  • You override Typical VM Workload for a cluster or host