vCloud Director 8.10.1 for Service Providers Release Notes

vCloud Director 8.10.1 for Service Providers | 06 DEC 2016 | Build 4655197 (installer build 4655196)

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

What's New

  • JRE Version Update
    vCloud Director 8.10.1 for Service Providers uses JRE version 1.8.0_111.

  • Enhanced Boot Options
    New boot customization options added to delay the boot time and to enter into the BIOS setup screen. You can use the vCloud Director Web console or the vCloud API to set Boot Delay and EnterBIOS mode options.

System Requirements and Installation

Compatibility

The VMware Product Interoperability Matrixes provides details about the compatibility of current and earlier versions of vCloud Director:

  • vCloud Director interoperability with other VMware platforms
  • Supported vCloud Director databases
  • Upgrade paths

Supported vCloud Director Server Operating Systems

  • CentOS 6
  • CentOS 7
  • Red Hat Enterprise Linux 5, update 4-10
  • Red Hat Enterprise Linux 6, updates 1-7
  • Red Hat Enterprise Linux 7

Supported vCloud Director Databases

The most current information about supported databases for this release of vCloud Director is available from the VMware Product Interoperability Matrixes. For database server configurations, see the vCloud Director Installation and Upgrade Guide.

Supported Databases for Storing Historic Metric Data

You can configure your vCloud Director installation to store metrics that vCloud Director collects about virtual machine performance and resource consumption. Data for historic metrics is stored in a KairosDB database backed by Cassandra. vCloud Director supports the following KairosDB and Cassandra versions.

  • KairosDB 0.9.1
  • Cassandra 1.2, 2.0, and 2.2

For more information, see the vCloud Director Installation and Upgrade Guide.

Top of Page

Disk Space Requirements

Each vCloud Director server requires approximately 2100 MB of free space for the installation and log files.

Memory Requirements

Each vCloud Director server must be provisioned with at least 6 GB of memory.

Required Linux Software Packages

Each vCloud Director server must include installations of several common Linux software packages. These packages are typically installed by default with the operating system software. If any are missing, the installer fails with a diagnostic message.

alsa-lib    
bash
chkconfig
coreutils
findutils
glibc
grep
initscripts
krb5-libs
libgcc
libICE
libSM
libstdc
libX11
libXau
libXdmcp
libXext
libXi
libXt
libXtst
module-init-tools
net-tools
pciutils
procps
redhat-lsb
sed
tar
which

In addition to the packages that the installer requires, several procedures for configuring network connections and creating SSL certificates require the use of the Linux nslookup command, which is available in the Linux bind-utils package.

Supported LDAP Servers

vCloud Director supports import of users and groups from the following LDAP services.

Platform LDAP Service Authentication Methods
Windows Server 2003 Active Directory Simple, Simple SSL, Kerberos, Kerberos SSL
Windows Server 2008 Active Directory Simple
Windows Server 2012 Active Directory Simple, Simple SSL, Kerberos, Kerberos SSL
Windows 7 (2008 R2) Active Directory Simple, Simple SSL, Kerberos, Kerberos SSL
Linux OpenLDAP Simple, Simple SSL

Supported Security Protocols and Cipher Suites

vCloud Director supports the following security protocols that the server offers to use when making a client connection:

  • TLS version 1.0
  • TLS version 1.1
  • TLS version 1.2

Supported cipher suites include:

  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
  • TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
  • TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
  • TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_256_CBC_SHA
  • TLS_RSA_WITH_AES_128_CBC_SHA
  • TLS_RSA_WITH_3DES_EDE_CBC_SHA

You can use the cell management tool to reconfigure the set of supported TLS protocols or ciphers. See the Cell Management Tool Reference in the vCloud Director Administrator's Guide.

Top of Page

Supported Browsers

The vCloud Director Web console is compatible with recent versions of Google Chrome, Mozilla Firefox, and Microsoft Internet Explorer.

Browsers Supported on Linux Platforms

On these Linux platforms, the vCloud Director Web console is compatible with the most recent version of Mozilla Firefox and Google Chrome, and with their immediate predecessor versions.

  • CentOS 7.x
  • Red Hat Enterprise Linux 7.x
  • Ubuntu 14.x

Browsers Supported on Windows Platforms

On Windows platforms, the vCloud Director Web console is compatible with at least one version of Microsoft Internet Explorer. Some Windows platforms are also compatible with the most recent version of Mozilla Firefox and Google Chrome, and with their immediate predecessor versions.

The vCloud Director Web console is not compatible with the Microsoft Edge browser.

Platform Google Chrome Mozilla Firefox Internet Explorer
Windows XP Professional YES YES 10.x, 11.x
Windows Server 2003 Enterprise Edition YES YES 10.x, 11.x
Windows Server 2008 YES YES 10.x, 11.x
Windows Server 2008 R2 YES YES 10.x, 11.x
Windows Vista YES No 10.x, 11.x
Windows 7 YES YES 10.x, 11.x
Windows 8 YES YES 10.x, 11.x

Browsers Supported on Macintosh Platforms

On Macintosh platforms, the vCloud Director Web console is compatible with the most recent version of Mozilla Firefox and Google Chrome, and with their immediate predecessor versions.

Supported Versions of Adobe Flash Player

The vCloud Director Web console requires Adobe Flash Player 11.2 or later. Only the 32-bit version is supported.

Supported Versions of Java

vCloud Director clients must have JRE 1.6.0 update 10 or later installed and enabled. Only the 32-bit version is supported.

Top of Page

Supported Guest Operating Systems

vCloud Director supports a wide variety of 32-bit and 64-bit operating systems in its virtual machine templates and virtual machines. You can use version 11, but you can import version 4, 7, 8, 9, and 10 virtual machines.

Microsoft Windows Guest Operating System Support

The following Microsoft Windows guest operating systems are supported. Unless stated otherwise, all OS variants and 32-bit/64-bit editions are supported. Unless specified, all SP, minor and maintenance versions are supported.

  • Microsoft Windows Server 2012 R2 64-bit
  • Microsoft Windows Server 2012 64-bit
  • Microsoft Windows 10
  • Microsoft Windows 8
  • Microsoft Windows 7
  • Microsoft Windows Server 2008 R2 64-bit
  • Microsoft Windows Server 2008
  • Microsoft Windows Server 2003
  • Microsoft Windows Small Business Sever 32-bit
  • Microsoft Windows Vista
  • Microsoft Windows XP Professional

UNIX/Linux Guest Operating System Support

The following UNIX and Linux guest operating systems are supported. Unless stated otherwise, all OS variants and 32-bit/64-bit editions are supported. Unless specified, all SP, minor or maintenance versions are supported.

  • Red Hat Enterprise Linux 4-7
  • SUSE Enterprise Linux 10-12
  • Oracle Linux 4-7
  • CentOS
  • Ubuntu Linux
  • Other 3.x Linux
  • Other 2.6.x Linux
  • Other 2.4.x Linux
  • Other Linux

Top of Page

Documentation

To view the full set of vCloud Director 8.10 for Service Providers documentation, go to the vCloud Director for Service Providers Documentation page.

Resolved Issues

  • Deployment of vApp template in My Cloud with Hardware Modification fails with null UI Error
    Attempts to deploy vApp in My Cloud from the vApp template with hardware modifications fail with null UI error in a Storage DRS enabled datastore cluster.

    This issue is resolved in vCloud Director 8.10.1.

  • After vCloud Director upgrade, the vCloud Director version does not change in vCenter Solutions Manager
    After successful upgrade of the vCloud Director from version 8.0.1 to 8.10.0, the vCloud Director version in vCenter Solutions Manager does not update and remains 8.0.1.

    This issue is resolved in vCloud Director 8.10.1.

  • Uploading ISO media file does not consume quota that is set after the storage policy is configured to organization vDC
    When you configure the storage policy to organization virtual datacenter (vDC) and set a quota limit, the quota is not consumed while uploading the ISO media file.

    This issue is resolved in vCloud Director 8.10.1.

  • When a new upload or download is initiated, the Ovftool connects to the vCloud Director using the IP address but not the FQDN
    Ovftool does not send all vCloud API requests in the FQDN format. The initial vCloud Director API requests use the IP address of the vCloud Director cell but later starts using the FQDN.

    This issue is resolved in vCloud Director 8.10.1 Client Integration Plug-In available at KB 2145401.

  • vCloud Director Organization Administrators cannot instantiate organization vDC from the template in the UI
    Organization Administrators are unable to instantiate organization vDC from the template in the vCloud Director UI in spite of having the ORG_VDC_TEMPLATE_INSTANTIATE privilege.

    This issue is resolved in vCloud Director 8.10.1.

  • vCloud Director database upgrade takes long time to complete when the audit_event table contains millions of records
    Database upgrade of vCloud Director from versions 5.5.x, 5.6.x to versions 8.0, 8.0.x, 8.10 might take up to 8 hours time to complete if the audit_event table contains millions of records.

    This issue is resolved in vCloud Director 8.10.1. The database upgrade might now take up to 20 minutes.

  • VMware vCloud Director (vmware-vcd) services do not start automatically upon a reboot
    The VMware vCloud Director (vmware-vcd) services do not start automatically after a reboot because of an issue in the systemd-219-19.el7 module of Red Hat Enterprise Linux 7.2. For further details, see Red Hat Bugzilla – Bug 1285492.

    This issue is resolved in vCloud Director 8.10.1 that includes the upgrade to Red Hat Enterprise Linux 7.3.

    Note: To resolve this issue with Red Hat Enterprise Linux 7.2, see KB 2148034.

Top of Page

Known Issues

The known issues applicable for this release are grouped as follows:

General Issues

  • Non system users and organization administrators unable to add vApp to catalog
    Non system users and organization administrators with roles like Catalog Author and vApp Author are unable to add vApps to catalogs after upgrading to vCloud Director 8.10.

    Workaround: Provide the Organization -> View Organizations privilege to the non system users and organization administrators to allow them to Add vApp to catalog.

Localization Issues

  • Some keys in the non-English keyboard layouts do not work in the WebMKS console
    Some keys in the non-English keyboards layout are not mapped correctly in the virtual machine. When you press these keys with non-English Windows or Mac keyboard, the keys might not work or a wrong key might be entered in the WebMKS console. For information about the keys, see KB 2148037.

    Workaround: Use the VMware Remote Console.

Known Issues from Earlier Releases

To view a list of known issues applicable from earlier releases, click here.

General Issues

  • Limits on Queued Resource-Intensive Operations Might Not be Respected When vCloud Director is Using an Oracle Database.
    In a vCloud Director installation that uses an Oracle database, configured system limits that specify values for Number of Resource-Intensive Operations to be Queued per User or Number of Resource-Intensive Operations to be Queued per Organization might be exceeded. The issue does not affect a vCloud Director installation that uses a Microsoft SQL Server database.

    Workaround: None.

  • Disabled vCenter Server Continues to Accept vCloud Director Operations
    After you have used the vCloud Director Web console to disable a vCenter server, requests that trigger vCenter operations such as powering on a virtual machine are still accepted.

    Workaround: To disable a vCenter server registered to vCloud Director, use the vCloud Director Web console to disable all Provider VDCs backed by the vCenter server.

Installation and Upgrade Issues

  • NSX 6.2 Edge Redeployment Fails when Edge Gateway has a Complex Configuration
    After you upgrade to NSX 6.2, redeployment of Edge Gateways that have a complex configuration (including many firewall rules, NAT rules, and static routes) can fail with an error of the form "Cannot redeploy edge gateway ... Redeploy failed to upgrade" putting vCloud Director into a "Failed Redeployment" status and leaving all options but Redeploy unavailable in the UI.

    Workaround: Re-run the redeploy operation on the Edge Gateway.

  • After Unattended Installation, vCloud Director Does Not Start Automatically When the System Reboots
    If you install vCloud Director using the -unattended option, the installation succeeds but the server is not configured to start vCloud Director when it reboots.

    Workaround: After installation completes, run the Linux chkconfig command:

    chkconfig --add vmware-vcd

    This command configures the system to start vCloud Director automatically.

Networking Issues

  • Provider VDC > External Network tab does not list all available external networks.
    When you use the vCloud Director Web console to list external networks available in a Provider VDC, some of the available networks might not be shown.

    Workaround: Use the vCloud API to list the external networks in the Provider VDC.

Virtual Machine and vApp Issues

  • Affinity Rule Limitations with Elastic VDC and vSAN
    In an elastic VDC (one that has multiple resource pools) that includes one or more datstores on vSAN volumes, you cannot create an affinity rule that requires migrating any of the VMs to a different resource pool.

    Workaround: When creating an affinity rule, specify only VMs on a shared datastore.

  • Failed Request to Create Independent Disk Appears to Have Succeeded
    A request to create an independent disk can sometimes fail even though the operation is recorded as successful. The disk does not exist, and the log includes a message of the form:

    The requested operation cannot be performed because disk "{ID}" was not created properly.

    Workaround: Re-try the operation

API Issues

  • OperationLimitsSettings request body must include all elements.
    A vCloud API request of the following form:

    PUT https://vcloud.example.com/api/admin/extension/settings/operationLimitsSettings

    fails unless all elements in the request body are present, even those elements shown as optional in the schema reference.

    Workaround: Make a request like this one:

    GET https://vcloud.example.com/api/admin/extension/settings/operationLimitsSettings

    and use the response body as the template for a new request.

  • Incorrect List of vCloud API Changed Types in the Schema Reference
    The vCloud API Changed Types page of the vCloud API Schema Differences lists a number of types as removed in API version 9.0 and added in API version 20.0. Any types listed this way were actually not changed in either API version.

Collapse List of Earlier Known Issues

Top of Page