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.
In this post, I am going to review the deployment steps for installing and configuring the newly available VMware App Launchpad. Also, I will be doing a high-level overview as I am learning about this new VCD addition.
First, the VMware App Launchpad is a platform that allows for the ability to create application catalogs within VMware Cloud Director (VCD) for self-service. The value behind this is Bitnami’s entire catalog platform, which is integrated into VMware App Launchpad. A provider can also create custom applications and expose these through the plugin.
In this post, I’m going to highlight the new technical additions that are now part of the VMware vCloud Availability 3.5. VMware vCloud Availability 3.5, or vCAv, is a comprehensive Disaster Recovery as a Service and Migration platform.
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.