Utilization metering performs an essential function for companions who want to make the most of VMware merchandise on a pay-as-you-grow foundation. It is a vital a part of the VCCP program as a result of it provides suppliers visibility on their VMware product utilization, which helps them plan their infrastructure spending and development technique. The metering of the primary VMware merchandise which can be a part of this system is automated and facilitated by the Utilization Meter digital equipment.
Certainly one of these VMware merchandise is vSAN. VMware vSAN is a software-defined, enterprise storage resolution that helps hyper-converged infrastructure (HCI) methods. vSAN aggregates native or direct-attached information storage units to create a single storage pool shared throughout all hosts in a vSAN cluster.
How is vSAN utilization metered?
When a vCenter server is added for metering within the Utilization Meter net software, Utilization Meter robotically detects a cluster with enabled vSAN. The metering of vSAN begins instantly after the vCenter product certificates is accepted within the Utilization Meter net software.
vSAN utilization is metered on a cluster stage. Utilization Meter collects information each 1 hour for the used storage capability and checks which vSAN options are used on a vSAN cluster stage.
If a vSAN characteristic is detected for use by a VM a part of the vSAN cluster, then the entire vSAN cluster is taken into account utilizing this characteristic.
Which vSAN variations are suitable with Utilization Meter?
With the most recent Utilization Meter 4.5, we purpose to meet up with metering the vSAN options which can be accessible at the moment. The checklist of options accessible for metering at the moment corresponds to vSAN 7.0 Replace 1. Right here is the checklist of all vSAN editions that Utilization Meter 4.4 and 4.5 are suitable with:
|vCloud Utilization Meter 4.5||vCloud Utilization Meter 4.4|
|VMware vSAN™ 7.0.3||Suitable||Suitable|
|VMware vSAN™ 7.0.2||Suitable||Suitable|
|VMware vSAN™ 7.0.1||Suitable||Suitable|
|VMware vSAN™ 7.0||Suitable||Suitable|
|VMware vSAN™ 6.7.3||Suitable||Suitable|
|VMware vSAN™ 6.7.2||Suitable||Suitable|
|VMware vSAN™ 6.7.1||Suitable||Suitable|
|VMware vSAN™ 6.7||Suitable||Suitable|
|VMware vSAN™ 220.127.116.11||Suitable||Suitable|
|VMware vSAN™ 6.6.1||Suitable||Suitable|
The next checklist reveals which vSAN options are metered by Utilization Meter 4.4 and 4.5:
|vSAN Options||Utilization Meter 4.4||Utilization Meter 4.5|
|Raid 5/6 Erasure Coding||X||X|
|Deduplication and Compression||X||X|
|vSphere distribution swap||X||X|
|Software program Checksum||X||X|
|iSCI Goal service||X||X|
|QoS- IOPS limits||X||X|
|HTML5 Person Interface||X||X|
|Information in Transit Encryption||X|
|Cloud Native Storage||X|
Guide reporting of vSAN utilization
The reported license of the vSAN cluster that makes use of options that can not be robotically metered (as seen within the above checklist) have to be manually adjusted in VMware Commerce Portal MBO on the finish of the reporting month if that options will change the reported license.
Utilization Meter robotically detects the used storage capability per vSAN cluster, but it surely doesn’t robotically meter all accessible vSAN options. The vSAN options utilized by a VM a part of a vSAN cluster may be seen in vSphere.
To see the corresponding vSAN license version to every vSAN characteristic, your vSAN cluster makes use of, examine the most recent VCPP Product Utilization Information.
How is vSAN utilization reported?
vSAN used storage capability is reported in opposition to the license version with that are related the options utilized by the VMs within the vSAN cluster.
Despite the fact that the enabled license version for the cluster may very well be larger, e.g., vSAN Enterprise, the license that can be reported would be the one which corresponds to the detected by Utilization Meter vSAN options. That may very well be vSAN Normal if all of the detected options for the reporting interval fall into that license version.
If vSAN options are current in a number of editions, Utilization Meter will take the bottom license version. For instance, in case you have a cluster utilizing solely Deduplication and Compression for the reporting interval, then the used storage capability of that cluster can be reported in opposition to the vSAN Superior license.
How is vSAN utilization calculated?
vSAN utilization is calculated based mostly on the common consumed storage capability per vSAN license version all through the month in GB.
“Used Capability” means the storage capability consumed by vSAN Overhead (deduplication and compression metadata reservation) and all VM Objects (like VMDK, SWAP information, VMX, Snapshots, and many others.) and never accessible for brand spanking new allocations.
The consumed storage capability for the month is aggregated illustration of the information accessible within the vSAN Cluster Historical past Report. The vSAN Cluster historical past report’s consumed storage is MB per cluster and time interval. To match it with the consumed storage capability within the Month-to-month Utilization Report, calculate the common used storage capability for the month and switch it from MB to GB. Additionally, you will must spherical down the calculated common vSAN consumed storage capability to a complete quantity.
vSAN utilization within the Month-to-month Utilization Report
In Utilization Perception, there a utilization stories that show you how to monitor your aggregated utilization.
The aggregated utilization is proven beneath Utilization & Commerce within the Cloud Companion Navigator portal and reveals the vSAN utilization per license in the intervening time of reference. You can even examine your utilization per thirty days, which is a snapshot of the utilization for that month.
vSAN Cluster Historical past Report
The vSAN Cluster historical past report, because the title suggests, is a historical past report just for vSAN clusters. It consists of detailed info on the storage capability that has been utilized by a cluster for a selected time interval. It additionally reveals the kind of vSAN license enabled per vSAN cluster and the int sum of the vSAN options used for that cluster (proven within the vSANFint column).
Notice: The utilized vSAN license for a cluster will not be reported by Utilization Meter because it compares the detected options in opposition to the vSAN version with which they’re related. Which means in case you are not utilizing all options included in your vSAN license, then Utilization Meter will solely report the consumed storage capability in opposition to the license to which belong the detected options.
How is vSAN utilization billed?
vSAN utilization is billed based mostly on common consumed storage capability in GB multiplied by the factors given for the license version to which all detected vSAN options for the month belong. At the moment, there are three vSAN license editions accessible: vSAN Normal, Superior, and Enterprise.
Every vSAN license version has a unique VCPP level utilized to the used storage capability in GB.
Here’s a glimpse of the factors for every vSAN license version. They’re multiplied by the common storage capability for the month in GB.
Have extra questions?
Attain out to us at firstname.lastname@example.org.