The vCloud Availability for vCloud Director Portal provides a graphic user interface to facilitate the management of vCloud Availability for vCloud Director operations.

About this task

The vCloud Availability for vCloud Director Portal back end (PBE) scales horizontally. You can deploy a new vCloud Availability for vCloud Director Portal instance on demand connected to the same load balancer that all the vCloud Availability for vCloud Director 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 for vCloud Director Portal is consistent.

Depending on the number of concurrent sessions that the vCloud Availability for vCloud Director Portal is expected to host, you can deploy small, medium, or large vCloud Availability for vCloud Director Portal host. The vCloud Availability for vCloud Director Portal sends requests to a vCloud Director instance and receives data from the same vCloud Director instance. To host the maximum number of concurrent sessions, ensure that the vCloud Director database can use similar compute resources that you allocate to the vCloud Availability for vCloud Director Portal host. You can find details about the vCloud Availability for vCloud Director Portal deployment types in the following table.

Table 1. vCloud Availability for vCloud Director Portal Host Deployment Types

Deployment Type

Description

Small

Deploys an appliance with 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.

Medium

Deploys an appliance with 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

Deploys an appliance with 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.

Procedure

  1. Create a vCloud Availability for vCloud Director Portal host by running the following command.
    Important:

    The --deployment-type argument in the following command defines the compute resources that you allocate to the vCloud Availability for vCloud Director Portal host. By default, the value is small. You can change the value depending on your requirements.

    Standard Command

    Command Using Registry

    # vcav vcd-ui create \
    --ovf-url=vcloud-availability-release_number-xxx-build_number_OVF10.ova \
    --deployment-type=small \
    --vsphere-address=$MGMT_VSPHERE_ADDRESS \
    --vsphere-user=$MGMT_VSPHERE_USER \
    --vsphere-password-file=~/.ssh/.vsphere.mgmt \
    "--network=$MGMT_VSPHERE_NETWORK" \
    "--vsphere-locator=$MGMT_VSPHERE_LOCATOR" \
    --datastore=$MGMT_VSPHERE_DATASTORE \
    --ntp=pool.ntp.org \
    --root-password-file=~/.ssh/.root \
    --vm-name=ui01-name
    
    # vcav vcd-ui create \
    --ovf-url=vcloud-availability-release_number-xxx-build_number_OVF10.ova \
    --deployment-type=small \
    --vsphere=mgmt-vsphere-name \
    --ntp=pool.ntp.org \
    --root-password-file=~/.ssh/.root \
    --vm-name=ui01-name
    

    The IP address of the new vCloud Availability for vCloud Director Portal virtual machine is displayed. Write it down because you need it during the configuration.

  2. Set a variable to the address of the created virtual machine.

    Standard Command

    Command Using Registry

    # UI01_ADDRESS=`vcav vsphere get-ip \
    --vsphere-address=$MGMT_VSPHERE_ADDRESS \
    --vsphere-user=$MGMT_VSPHERE_USER \
    --vsphere-password-file=~/.ssh/.vsphere.mgmt \
    "--network=$MGMT_VSPHERE_NETWORK" \
    --vm-name=ui01-name`
    # UI01_ADDRESS=`vcav vsphere get-ip \
    --vsphere=mgmt-vsphere-name \
    "--network=mgmt-network" \
    --vm-name=ui01-name`
  3. Update the truststore file with the vCloud Availability for vCloud Director Portal virtual machine credentials.
    # echo 'Portal-VM-Password' > ~/.ssh/.truststore
    
    # chmod 0600 ~/.ssh/.truststore
  4. If you use Fully Qualified Domain Names (FQDN) to access and manage appliances, you must verify that the DNS record matches the vCloud Availability for vCloud Director Portal IP address, and trusts the SSH certificate for this FQDN.
    1. Check the DNS server to ensure that the entry matches the IP address of the vCloud Availability for vCloud Director Portal host.
    2. Run the trust-ssh command to trust the certificate for the vCloud Availability for vCloud Director Portal FQDN.

      Standard Command

      Command Using Registry

      # vcav vsphere trust-ssh \
      --vsphere-address=$MGMT_VSPHERE_ADDRESS \
      --vsphere-user=$MGMT_VSPHERE_USER \
      --vsphere-password-file=~/.ssh/.vsphere.mgmt \
      --root-password-file=~/.ssh/.root \
      --vm-name=ui01-name \
      --vm-address=ui01-FQDN
      
      # vcav vsphere trust-ssh \
      --vsphere=mgmt-vsphere-name \
      --root-password-file=~/.ssh/.root \
      --vm-name=ui01-name \
      --vm-address=ui01-FQDN