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

Building My First AI Chatbot with Azure OpenAI Services

In April 2024, I embarked on an exciting journey into the world of artificial intelligence (AI), starting with learning Python. Coming from an infrastructure-focused background, diving into AI development felt like a monumental shift. Without prior coding experience, I realized that building AI tools or training models from scratch would require a long-term commitment. However, I was determined to take small, practical steps toward understanding this fascinating field. Exploring cloud AI services from providers like AWS and Azure led me to Azure OpenAI services. This platform showed me how AI could be leveraged to create applications— like chatbots—without deep coding expertise. I was especially intrigued by concepts such as indexing, semantic search, and retrieval-augmented generation (RAG). These tools enabled me to build my first business use case: a Microsoft Teams chatbot designed to resolve internal queries and reduce dependency on subject matter experts (SMEs). This blog is a s...
Post a Comment
Read more

How to enforce Day2 Action Policy in vRA 8.x

It's bit different when compared to vRA 7.x versions. If you do not have any Day 2 Action policies defined, then no governance is applied and all users have access to all the actions by default in vRA 8.x.Okay, let see this with an example By default all the deployments/machines are entitled with all actions for all users in the organization Once you a define Day 2 Action policy it goes into effect for specified users of vRA service broker and Cloud assembly. As a result, only the users for whom the first policy is true can run the selected actions. All others are excluded. I have created a Day2 Action policy to change deployment lease and create snapshot of cloud machine for Administrator user in the entire organization(includes all projects in the organization). As you can see below I logged in with an project administrator user and I am entitled with enforced Day2 action created and this will be applied for existing deployment as well. When I logged as a project member user as...
Post a Comment
Read more