In this blog post, I will show all of the steps required to operationalize vCloud Usage Meter 4.3, or UM, within your data center. With the end of availability of Usage Meter 3.6.1, it is imperative that all VMware Cloud Providers start a plan of action to migrate to the 4.3 codebase.
Moreover, I’ll provide the full context on how UM works with Usage Insight and the VMware Commerce Portal.
While this is a long blog post, it’s important we highlight all of the necessary steps within the VMware consumption operational model for VMware Cloud Providers.
With version 4.0, VMware Cloud Director Availability (VCDA) introduced enhancements that detect if a Usage Meter instance is connected to the Cloud Manager instance. If it’s not, the provider administrator will see an orange banner that shows Usage Meter connectivity is not established –
Last week, the VMware Cloud Provider team released a hot patch for VMware vCloud Usage Meter 3.6.1. Usage Meter can now automatically meter vCloud Availability (vCAv) 3.x instances. This also covers Site Recovery Manager (SRM) virtual appliances along with a few bug fixes.
Prior to this hot patch, a VMware Cloud Provider would need to manually report usage by exporting the vCAv Manager report on a monthly basis. This hot patch mitigates that process by now providing automatic metering of vCAv instances within a Usage Meter appliance.
This is intended for Cloud Providers that are participating in the VMware Cloud Provider Program (VCPP).
In this post, I will review the setup instructions and what needs to be done so proper metering is in place for vCAv 3.0.