Cloud Infrastructure Metering

Cloud Infrastructure Metering #

vCloud Usage Meter is a virtual appliance for tracking the usage of the VMware products part of the VMware Cloud Provider Program that are deployed on-prem and payed based on pay-as-you-grow model.

The Usage Meter appliance is installed on-prem through vSphere and connects to the metered products through their IPs and the users who are able to connect to them. After the successful connection to the metered products is established, the collection of usage data starts.

The data is collected every 1 hour for most VMware products and used by vCloud Usage Insight. The latter is a cloud service that aggregates the usage data and generated reports out of it. The aggregated data appears during the first few days of the following month in the VMware Commerce Portal (VCP). This data is used for the generation of the VCP Monthly Billing Order (MBO).

Here is a glimpse of how Usage Meter and Usage Insight work together:

Usage Meter Workflow

vCloud Usage Meter Deployment #

vCloud Usage Meter is deployed on-prem as a virtual appliance and tracks the usage of the VMware products that it meters.

One of the ways to deploy the appliance is to use the VMware Cloud Provider Lifecycle Manager.

See the following information on how to deploy vCloud Usage Meter by using the API calls of the VMware Cloud Provider Lifecycle Manager.

Another way to deploy the appliance is by installing its ova file through vSphere. See the process here.

vCloud Usage Meter Security and Privacy Guidelines #

vCloud Usage Meter collects usage data from the metered products in a transparent and secure way. It anonymizes data such as vSAN cluster name, VM name, hostname, target vCenter, etc. The anonymization is conducted prior to transmitting to VMware using SHA1 to create a one-way hash. From the hash, VMware cannot obtain the original value.

Moreover, vCloud Usage Meter does not collect any PII data. Providers can see at any time what data their Usage Meter collects by downloading the usage data locally.

The full list of data collected by vCloud Usage Meter per supported VMware product can be found in the Usage Meter Data Privacy and Sharing Guidelines whitepaper.

vCloud Usage Meter is also FIPS-compliant which testifies to its high level of security and data privacy.

How to start metering your VCPP products with Usage Meter #

To start metering the VMware products that you use, you need a signed VCPP contract with VMware and a deployed Usage Meter appliance. The latter must be registered with your VCPP license (Rental or Sovereing Cloud) before you can start metering the usage of your VMware products.

Then, you must add the details of each product like IP address or hostname, and the credentials of the user who is able to connect to it.

The process of adding a VMware product for metering is explained in details in the following page.

How does the metering work #

The following information helps you understand how the metering of product usage data works.

It also provides insight into how the reported usage data is calculated and appears in the vCloud Usage Insight reports.

The metering information goes into the following categories.

Metering Cloud Infrastructure Products #

  1. vCenter Server - Metered based on the average capped billed vRAM per a managed VM. ReportŠµd as part of the FLex Core bundle.

  2. VMware Cloud Foundation - Metering is based on the time-based average of host CPU core count aggregated by different VCF editions except for the SDDC Manager license edition. The SDDC Manager license edition is metered as an average Capped Billed vRAM GB per a VM. The VCF editon that is reported is the one selected when the VCF is added in the Usage Meter web application.

  3. vSAN - Metered based on Monthly average of an hourly count of used capacity (datastore space used). The vSAN license edition is determined by the vSAN features used by the vCenter VMs.

  4. NSX-V - Metering is based on the average capped billed vRAM GB per a VM using a NSX-V features if bundled or a monthly average of an hourly count of non-unique VMs serviced for the NSX-V Enterprise edition only. The edition is determined by the NSX- V features that are used by the vCenter VMs.

  5. NSX-T - Metered based on the average capped billed vRAM in GB per VM using NSX-T features. The reported license edition is determined by the NSX-T features used by the vCenter VMs.

  6. Cloud Director - Metered based on the number VMs under management.

Metering Other Solutions #

  1. Cloud Director Availability - Usage is calculated based on the number of protected VMs.

  2. Tanzu Kubenetes Grid Service - Usage is calculated based on the vRAM or CPU cores used by the TKGs-related VMs.

  3. Tanzu Kubenetes Grid Multi-cloud - Usage is calculated based on the vRAM or CPU cores used by the TKGm-related VMs.

  4. SRM - Metered based on the number of protected VMs.

  5. VMware Aria Operations - Usage is metered either based on the average capped billed vRAM used by the VMs monitored by vRealize Operations when the latter is used as a Flex Add-on product, or the hourly count of non-uniques VMs under monitoring throughout the month when vROPs is reported as a standalone product.

  6. VMware Aria Operations for Networks - Usage is metered either based on the average capped billed vRAM used by the VMs monitored by vRealize Operations when the latter is used as a Flex Add-on product, or the hourly count of non-uniques VMs under monitoring throughout the month when vROPs is reported as a standalone product.

  7. VMware Aria Automation 7.x - Usage is calculated based on the monthly average of an hourly count of non-unique vSphere VMs in the month.

  8. VMware Aria Automation 8.x - Usage is calculated based on the monthly average of an hourly count of non-unique VMs in the month residing on vSphere, AWS, Azure or GCP.

Metering Other Products #

  1. Horizon - Usage is calculated as a maximum number of desktop VMs under management for VDI or maximum number of sessions under management for RDSH.

  2. Horizon DaaS - Usage is calculated based on the maximum number of concurrent connections to a Horizon Connection Server per license edition.