Skip to main content

vCloud Director Availability On-premises installation

In my previous post Provider setup we have seen vCDA provider installation. Here, we will see vCDA 4.0.1 On-premises installation.

Download the On-premise OVA from  VMware Download and deploy it in your vCenter. 

Note: Ensure that vCenter Server, ESXi, Platform Services Controller, VMware Cloud Director, and the VMware Cloud Director Availability appliance all use the same NTP server. 

Before I deploy vCDA On-premises in my environment I had taken a screen shot of available vCenter client plugin for reference

 

 

  • Once the OVA is deployed in vCenter, access the replicator web page using https://applianceIP. Change the password for appliance as you are logging for the first time.

 

  

  • Run the initial setup wizard

 

 Enter the vCenter details for lookup service configuration 

 

Enable "provide cloud pairing details later" and finish the setup

 

You would be able to see vCDA plugin in vCenter web client now 

 

  • Configure site pairing

Choose the DRaaS option under Menu in vSphere webclient  

  

Click on Pair Now

 

Provide on-premises site name and enter the lookup service info

 

 

Provide the remote site details and finish the wizard by enabling Edit/Configure local placement now

  

 


  • You will eventually find the newly paired On-premises site in vCloud Director tenant portal. That's it, you can start enabling DRaaS and migrate the workload.


Labels:

Comments

Post a Comment

Popular posts from this blog

Deleting stale kubernetes clusters in vCD

Unlike the previous version the CSE 4.x is a stateless appliance and its data is stored in VMware Cloud Director Database.  The cluster creation and deletion compared with CSE 3.x version has improved. Besides, there are some scenarios where the cluster deletion is failing even when the "Force Delete" option is chosen. We can use vCD API explorer to delete it, the following are the API queries you can execute  Under definedEntity POST /1.0.0/entities/{id}/resolve DELETE /1.0.0/entities/{id}
Post a Comment
Read more

Manage RabbitMQ using VCP LCM

I have been working in vCD for quite some time, and most of the implementation engineers or consultants faced issues during the deployment or upgrade of RabbitMQ for the vCD message queuing service. From vCD 10.2.2, we can use the built-in MQTT client instead of RabbitMQ however, for VCD multisite configuration or some 3rd party applications need RabbitMQ, such as Veeam or VMware HCX. Using the VCP LCM, we can create a new RabbitMQ environment or manage an existing environment. The reason for this blog is that none of the VMware documentation has the information that registering an existing RMQ instance is only going to work if the RMQ instance was previously deployed by the VCP LCM (or at least, if it is a similar setup based on a Bitnami RMQ VM). Other RMQ instances (e.g., running in CentOS) are not supported and cannot be imported into the VCP LCM 1.5. I hope this information will be useful for someone who is performing green field deployment or upgrading an existing setup.  
Post a Comment
Read more