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.
In this post, we will be reviewing the steps on setting up and operationalizing vCloud Availability 3.0 (vCAv) for a provider site.
There is a presumption that you will be deploying for production, so that is what I’ll be reviewing. The consolidated (combined) appliance would be an easier deployment, but still requires the below configurations post-deployment.
Recap of the Provider steps:
Deployment of Cloud Replication Management (CRM) Instance
Initial Replication Management Setup
Initial Setup Wizard
Deploy vCAv Replicator(s)
Deploy vCAv Tunnel
Configuration of CRM instance and start of site wizard