vCloud Availability for vCloud Director: Part 9-Create vCloud Availability Portal Host

In the last post of this series, we deployed the VRCS and VR appliances. In this post, we will deploy the VCAV Portal.

If you are not following along with this series, then I recommend reading earlier posts of this series from links below:

1: vCloud Availability Introduction

2: vCloud Availability Architecture & Components

3: VCAV Deployment

4: Install Cloud Proxy for vCD

5: Deploy Cassandra Cluster

6: RabbitMQ Cluster Deployment and vCD Integration

7: Deploy VRMS Appliance

8: Deploy vRCS and VR Server

What is vCloud Availability Portal?

The vCloud Availability Portal provides a graphic user interface for the management of vCloud Availability operations. The vCloud Availability Portal back end scales horizontally, and we can deploy more than one portal host for HA and load balancing.

VCAV portal host size varies from small to medium to large, depending on the number of concurrent sessions that the portal host will be handling.

For lab purposes, a small deployment works just fine.

To deploy the portal host appliance, run the following commands from the VCAV appliance.

Create a new Variable for the VCAV-UI appliance IP

Update the truststore file with the vCloud Availability Portal virtual machine credentials.

Trust the VCAV-UI host certificate

Create vCloud Availability Administration Portal

The vCloud Availability Administration Portal is a graphic user interface that helps service providers to monitor and manage their DR environments. Like the VCAV portal host, the administration portal can also be deployed in small, medium, and large sizes.

To create a vCloud Availability Administration Portal host, run the following command from the VCAV appliance:

Create a new Variable for the VCAV Admin Portal appliance IP

Trust the VCAV-Admin Portal host certificate

Validate VCAV Deployment

Before you configure vCloud Availability, you must confirm that all appliances are ready to be configured. Use the commands below to perform a validation check.

An OK message means that the deployed components are ready for configuration.

And that’s it for this post. In the next post of this series, we will integrate these components with vCD.

I hope you enjoyed reading this post. Feel free to share this on social media if it’s worth sharing. 

Leave a Reply