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.
I wanted to summarize a few things I’ve found when working with VMware vCloud Availability 3.0 (vCAv) over the past few months that will be helpful to providers and tenants. I’m sure there’s others, but these are the ones that come to mind.
Tunnel (Public API) Endpoint
This is a very important step for production deployments – setting the URL endpoint to ensure proper cloud access from tenants and other vCD instances.
The public API endpoint can be configured from the Cloud Replication Management (CRM) under Configuration:
Or can be configured directly on the tunnel:
When one configures it from the CRM, it does push this change to the tunnel appliance over port 8047 (internal communication port between CRM and the tunnel appliance).
Recently, I had this come up where I had to remove the vCloud Availability 3.0 (vCAv) plugin from my lab vCenter. Today, there is not a way to do this through the vCAv on-premises appliance UI – it must be done directly on the vCenter. Therefore, after speaking with a colleague (Bill Leck), I received the steps on removing it from the vCenter instance.
The following steps will work with vSphere 6.5x and 6.7U1. With 6.7U2, you can skip step 2 – thanks Vladimir Velikov.
Here are the high-level steps:
SSH to the vCenter
Remove endpoints from the lookup service
Restart vCenter UI services
This is a very easy and straight forward process. I’ve documented the step by step directions below.