The vCloud Availability Portal provides a graphic user interface to facilitate the management of vCloud Availability operations.
The vCloud Availability Portal back end (PBE) scales horizontally. You can deploy a new vCloud Availability Portal instance on demand connected to the same load balancer that all the vCloud Availability Portal instances are under. The load balancer must support sticky sessions, so that the same PBE instance processes user requests within a session. This setting ensures that all the information displayed in the vCloud Availability Portal is consistent.
vCloud Availability Portal Sizing
Deployment Type |
Size and Sessions |
---|---|
Small |
Appliance size is 2 CPUs, 2 GB of memory, 10 GB of disk space, and 512 MB of Java Virtual Memory. Suitable for hosting up to 150 concurrent sessions. |
Meduium |
Appliance size is 2 CPUs, 4 GB of memory, 10 GB of disk space, and 1.5 GB of Java Virtual Memory. Suitable for hosting up to 400 concurrent sessions. |
Large |
Appliance size is 4 CPUs, 6 GB of memory, 10 GB of disk space, and 3 GB of Java Virtual Memory. Suitable for hosting up to 800 concurrent sessions. |
Deploy the appliance using below command.
Create a new Variable with below information.
#export UI01_ADDRESS=192.168.110.164
we will use this variable in subsequent commands. Next is to configure Trust
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. This also need to be deployed using appliance sizing consideration.
vCloud Availability Administration Portal Sizing
Deployment Type |
Size and Sessions |
---|---|
Small |
Appliance size is 2 CPUs, 2 GB of memory, 10 GB of disk space, and 512 MB of Java Virtual Memory. Suitable for hosting up to 150 concurrent sessions. |
Meduium |
Appliance size is 2 CPUs, 4 GB of memory, 10 GB of disk space, and 1.5 GB of Java Virtual Memory. Suitable for hosting up to 400 concurrent sessions. |
Large |
Appliance size is 4 CPUs, 6 GB of memory, 10 GB of disk space, and 3 GB of Java Virtual Memory. Suitable for hosting up to 800 concurrent sessions. |
Now lets create vCloud Availability Administration Portal host by running the following command.
Create a new Variable with below information.
#export UI02_ADDRESS=192.168.110.165
if the deployment succeed then you will see that command returns IP address of the deployed Appliance. that represent that appliance has been deployed successfully.
Update the truststore file with the vCloud Availability Administration Portal virtual machine credentials using below command:
#echo ‘VMware1!’ > ~/.ssh/.truststore
Run trust-ssh command to trust the certificate vCAV FQDN.
now to validate that our deployments are ready for configuration , run below commands and must return “OK”.
“OK” means till now we have deployed components are ready for configuration.This successfully completes install of the all the appliances and components for vCAV. now we need to integrate these components to each other and with vCD.