VMware vCloud Availability for vCloud Director 1.0.1.2 Release Notes

|

VMware vCloud Availability for vCloud Director 1.0.1.2 | 13 JUL 2017 | Build 5974651

Last updated: 10 OCT 2017

Check for additions and updates to these release notes.

What's in the Release Notes

These release notes cover the following topics:

What's New

This release introduces Service Manager Portal for Service Providers to allow them to monitor and manage their DR environments. The new portal provides the following features:

  • Service Provider Admin Dashboard -  It provides insights into IaaS consumption including:
    • Overall allocated storage, memory and compute allocation.
    • Storage Utilization per Organization.
    • Number of replications per Organization.
  • Replication Details - It provides details on Replication Connections including:
    • Number of active replications across the DR set-up.
    • Replication status, RPO, storage consumption per replication and other details.
  • Generate Replication Reports: It allows the Service Providers to generate and download reports on:
    • Detailed Replication status.
    • Replication Scrubbing.
    • Storage Migration.
  • Manage Replications Cleanup and Storage Migration: It allows the Service Providers to:
    • Clean up the staled failover replication connections. 
    • Migrate failover replications from one storage to another.

This release introduces new vcav vcd-ui configure-smp command of the vCloud Availability Installer appliance for configuring the Service Manager Portal. The Service Manager Portal must be deployed separately from the vCloud Availability for vCloud Director Portal host.

The Service Manager Portal has a scheduler to generate reports. By default, the Service Manager Portal generates a report every twelve hours. You can adjust the frequency of Service Manager Portal report generation. Use a text editor to open the  /opt/vmware/vcav-smp/conf/application.yml file and set the trigger value.

Browser Support

The Service Manager Portal supports the following Web browsers:

  • Google Chrome 60.0.3112.90 (Official Build) (64-bit)
  • Mozilla Firefox 54.0.1 (32-bit)
  • Mozilla Firefox 52.3.0 (32-bit)

Upgrade

To upgrade your vCloud Availability for vCloud Director environment to version 1.0.1.2, you must upgrade the vCloud Availability Installer appliance and the vCloud Availability for vCloud Director Portal appliance. All other components remain unchanged.

Upgrading the vCloud Availability Installer Appliance

Appliance Upgrade

You can download the vCloud Availability Installer as an OVA file and deploy a new virtual machine. By performing an appliance redeployment, you lose all previously created registry records, password and trust information. For more information, see chapter Upgrading vCloud Availability for vCloud Director in the vCloud Availability for vCloud Director 1.0.1 Documentation Center.

Upgrading the vCloud Availability for vCloud Director Portal Host

You must upgrade the vCloud Availability for vCloud Director Portal Host to version 1.0.1.2 to gain the capability to maintain resources across multiple organizations.

First, you deploy a new virtual machine to host the vCloud Availability for vCloud Director Portal services.

  1. In a Web browser, navigate to the download page.
  2. Download the vcloud-availability-for-vcd-ui-ova-1.0.1.2-xxxx-build_number.ova file.
  3. Upload the file to the root user's home directory of your vCloud Availability Installer appliance.
  4. Create an SSH connection to the vCloud Availability Installer appliance in your environment.
  5. Create a new vCloud Availability for vCloud Director Portal Host. For more information, see topic Create vCloud Availability for vCloud Director Portal Host in the vCloud Availability for vCloud Director 1.0.1 Documentation Center.

After the creation, you may configure the virtual appliance as:

NOTE: The second step in the procedure for configuring the vCloud Availability for vCloud Director Portal Host is not needed in version 1.0.1.2.

  • A service to support the service provider administrators to maintain multiple organization resources - Configure the new vCloud Availability for vCloud Director Service Manager Portal host with the vCloud Director server and start system services using the vcav vcd-ui configure-smp command.

   vcav vcd-ui configure-smp \

  --ui-address=$UI01_ADDRESS \

  --keep-self-signed-certificate \

  --truststore-password-file=~/.ssh/.truststore \

  --vcd=vcd-01 \

  --mongodb-password-file=.ssh/.root

NOTE: It is strongly recommended to deploy the Service Manager Portal behind a VPN to limit access. 

Product Documentation

In addition to the current release notes, you can use the documentation set for vCloud Availability for vCloud Director 1.0.1 that includes the following deliverables.

Known Issues

The known issues are grouped as follows.

Installation and Configuration
  • `vcav vsphere trust-ssh` command stalls without any output

    This issue can occur if there is a firewall between the vCloud Availability Installer and the ESXi hosts to which the target appliance is deployed.

    Workaround: To work around this issue, run the same vcav [hms|hcs|hbr|vcd-ui] connect command for the appliance and add the --trust-ssh option. You should run the following command:

    `vcav [hms|hcs|hbr|vcd-ui] connect \

    --trust-ssh --vm-address=IP-address \

    --root-password-file=~/.ssh/.root` 

  • Running `vcav [hms|hcs|hbr|vcd-ui] create` returns an error

    If there is a firewall between the vCloud Availability Installer and the ESXi hosts to which you are deploying appliances, when you run vcav create commands on the vCloud Availability Installer, you might receive the following error message:

    ERROR - Failed to send http data

    Workaround: To work around this issue, allow HTTPS access to all ESXi servers from the vCloud Availability Installer. You can revert this change after the installation is complete.

vCloud Availability for vCloud Director Service Manager Portal

The issues in this section pertain to the vCloud Availability for vCloud Director Service Manager Portal features.

  • If you delete stale replications generated as part of removing VMs from a tenant site, VMs will not show up in the vCloud Availability for vCloud Director Service Manager Portal scrub replication feature.

    When you stop replications for all replicated VM's from a tenant vCenter Server, you delete all replication group IDs in the tenant database, but the replication CGID remains in the Provider site and the replication status remains in OK state. If you try to scrub replications in the vCloud Availability for vCloud Director Service Manager Portal the VM's are not displayed as the replications status is OK.

    Workaround: None.

  • VMs that are created during from-cloud replications are not displayed in the vCloud Availability for vCloud Director Service Manager Portal

    VMs that are failed back from the cloud to the tenant site are not displayed in the vCloud Availability for vCloud Director Service Manager Portal. As a result, you cannot migrate such VMs from one datastore to another, you cannot scrub replications for such VMs, and you cannot delete stale failback replications.

    Workaround: None.

  • When the pairing from tenant to cloud is disconnected, the VMs in the provider vCloud Director are not considered as stale entries as the replication status is OK and these replication VMs are not shown in the vCloud Availability for vCloud Director Service Manager Portal for scrub replication

    When all the replication in the tenant site are forcefully removed and the pairing from the tenant site is disconnected from the cloud, the VM replication group IDs are still available in provider site. These are stale entries in vCloud Director and should be considered as scrub replication. These replication VMs are not shown in the vCloud Availability for vCloud Director Service Manager Portal for scrub replication.

    Workaround: None.

  • The vCloud Availability for vCloud Director Portal home page takes too long to load when one or more vSphere Replication Servers are offline

    If a vSphere Replication Server is inaccessible, a portion of the vCloud Availability for vCloud Director Portal requests to load replication status from vCloud Director fail with a timeout error. As a result, the vCloud Availability for vCloud Director Portal home page takes too long to load data. To confirm this issue, you can look for java.net.SocketTimeoutException: Read timed out error messages in the vcav-ui.log file of the vCloud Availability for vCloud Director Portal host.

    Workaround: To work around this issue, you can increase the timeout threshold values for the vCloud Director extensions for vSphere Replication and vCloud Availability for vCloud Director Portal. Increasing the timeout threshold values enables the vCloud Availability for vCloud Director Portal to load data successfully. To increase the vCloud Availability for vCloud Director Portal timeout threshold value, do the following:

    • For vCloud Director, add the following line in the  /opt/vmware/vcloud-director/etc/global.properties file:

               extensibility.timeout = 60

    • For vCloud Availability for vCloud Director Portal, add the following parameters in the /opt/vmware/conf/vcav-ui/config.yml file:

               vcd:

                     baseUrl: https://x.x.x.x:443

                     trustSelfSignedKey: false

                     trustKeyStore: '/opt/vmware/conf/vcav-ui/vcd.truststore'

                     connectTimout: 60000

                     socketTimeout: 60000

     

    As a side effect of the workaround, if there are many replications on an offline vSphere Replication Server, the vCloud Availability for vCloud Director Portal takes much longer to receive all timeout error responses from vCloud Director and vCloud Director extensions. As a result, the vCloud Availability for vCloud Director Portal may display a Connection to vCloud Director timed out error message. Subsequently, you can dismiss the error message, refresh the page every 2 or 3 minutes to keep your browser session active. The error message should not appear thereafter.

  • You cannot log in to the vCloud Availability for vCloud Director Service Manager Portal and certificate errors appear in the appliance log file

    If there is a self-signed certificate in the vCloud Director SSL certificate chain, you must import this certificate to the truststore of vCloud Availability for vCloud Director Service Manager Portal. Otherwise, the following error might appear in the /opt/vmware/logs/vcav-smp/dr-service-manager.log file:

    2017-07-18 12:21:13,720 ERROR [SimpleAsyncTaskExecutor-1] co.vm.dr.ut.VcdServiceUtils - VCD API Request Failed https://vcd.test.com/api/sessions
    2017-07-18 12:21:13,720 ERROR [SimpleAsyncTaskExecutor-1] co.vm.dr.ut.VcdServiceUtils - I/O error on POST request for "https://vcd.test.com/api/sessions": sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target; nested exception is javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

    Workaround: To work around this issue, check vCloud Director certificate information and import the self-signed certificate to the truststore of vCloud Availability for vCloud Director Service Manager Portal.

    1. Run the following command from the vCloud Availability Installer appliance to get the vCloud Director certificate information.
      openssl s_client -connect vCloud-Director-IP-Address:443

      The system returns the following vCloud Director certificate information:

      CONNECTED(00000003)
      depth=0 C = XX, L = Default City, O = Default Company Ltd
      verify error:num=18:self signed certificate
      verify return:1
      ---
      Certificate chain
      0 s:/C=XX/L=Default City/O=Default Company Ltd
      i:/C=XX/L=Default City/O=Default Company Ltd
      1 s:/C=XX/L=Default City/O=Default Company Ltd/CN=test
      i:/C=XX/L=Default City/O=Default Company Ltd/CN=test

    2. Create an SSH connection to the vCloud Director Service Manager Portal host.

    3. Run the following openssl command to retrieve the vCloud Director certificate.
      openssl s_client -connect $VCD-IP-Address:443 /dev/null| openssl x509 > /tmp/vcloud.pem

    4. If you previously imported a vCloud Director SSL certificate to the truststore of vCloud Availability for vCloud Director Service Manager Portal, remove it by running the keytool command. Otherwise, skip to step 5.
      /usr/java/jre-vmware/bin/keytool -noprompt \
                -delete -trustcacerts \
                -alias vcloud \
                -file /tmp/vcloud.pem \
                -keystore /usr/java/jre-vmware/lib/security/cacerts \
                -storepass changeit
    5. Import the vCloud Director SSL certificate to the truststore of vCloud Availability for vCloud Director Service Manager Portal.
      /usr/java/jre-vmware/bin/keytool -noprompt \
                -import -trustcacerts \
                -alias vcloud \
                -file /tmp/vcloud.pem \
                -keystore /usr/java/jre-vmware/lib/security/cacerts \
                -storepass changeit
    6. Restart the SMP service.
      systemctl restart vcav-smp
  • After you deploy and configure a vCloud Availability for vCloud Director Service Manager Portal host, no data appears in the Summary page

    If you deploy and configure vCloud Availability for vCloud Director Service Manager Portal with a vCloud Director instance that does not have any replication data, after you log in to the vCloud Availability for vCloud Director Service Manager Portal, the Summary page displays the following message:
    Getting summary data, please wait.

    Workaround: Тo work around this issue, create replication data in vCloud Director, log in to the vCloud Availability for vCloud Director Service Manager Portal, and generate a report.

Other
  • Storage Migration is not possible for VMs that are in Configuration error state at the tenant side and placeholder is not created in provider site

    When the VM's is in error state in tenant side and the error message displayed configure replication failed not able to create a placeholder at cloud provider. 

    If there is a network issue when you configure a replication from the tenant vCenter Server, the replication state changes to error state in the tenant site and you receive a Configure replication failed. Not able to create a placeholder at cloud provider error message.

    Workaround: To work around this issue, resolve any possible network issues, log in to the tenant vCenter Server and stop the replication for all the VMs that are in Configure replication error state and reconfigure the replication for these VMs.

  • Running vcav scripts on the vCloud Availability Installer appliance returns a vCloud Director authentication error

    If you run vcav login vcd command and then run another vcav command without specifying all required arguments, the operation fails and you receive the following error:

    ERROR - Unable to write password for --vcd-password-file to remote server

    Workaround:To work around this issue, provide the --vcd=vcd-registry-name argument pointing to a fully specified vCloud Director entry in the registry file, or provide the following vCloud Director arguments when running the command:

    --vcd-address=vcd-ip-address \
    --vcd-user=vcd-user \
    --vcd-password-file=filepath \
    --sso-user=administrator@vsphere.local \
    --sso-password-file=filepath
    
Documentation

The vCloud Availability for vCloud Director 1.0.1 Documentation Center is updated. For more information, see Update Information topic in the vCloud Availability for vCloud Director 1.0.1 Documentation Center.