vCloud Director 8.10 for Service Providers Release Notes

vCloud Director 8.10 for Service Providers | 26 MAY 2016 | Build 3879706 (installer build 3880025)

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Documentation

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

What's New in this Release

New Features

  • Expanded UI Access to Features
    Many operations that were previously accessible only from the vCloud API are now accessible in the vCloud Director Web Console.

  • Virtual Machine Affinity Rules
    Support has been added for creation of affinity and anti-affinity rules for virtual machines. You can use the vCloud Director Web Console or the vCloud API to create affinity rules that allow you to spread a group of virtual machines across different hosts or keep a group of virtual machines on a particular host

  • Object Extensibility
    A new Object Extensibility feature has been introduced. vCloud Director object extensions are external applications that can participate in, influence, or override the logic that vCloud Director applies to complex operations like vApp instantiation and placement.

  • Advanced Virtual Machine Properties and Host Configurations
    If your service provider has enabled custom configurations of ESXi hosts in a resource pool that backs a VDC in your organization, you can apply object metadata in the VCENTER domain to virtual machines that can take advantage of the special properties of those hosts. The system uses that metadata to place the virtual machines on appropriate hosts.

  • VDC Permissions
    Tenant administrators can limit access to organization VDCs for all organization members or selected users.

  • Tenant throttling
    The system administrator can limit the number of resources that a user or organization could consume. This ensures that no tenant can consume excessive system resources with concurrent long-running operations.

  • Unattended Installation
    The system configuration utility now supports scripted, unattended installation.

  • Expanded Hardware Version and Guest OS support
    The system now supports Hardware Version 11 and Windows 10.

Other Changes

  • No Support for vShield Manager
    This release of vCloud Director does not support integration with VMware vShield Manager. Existing installations that are using vShield Manager must migrate their vShield Manager installations to VMware NSX Manager before upgrading to vCloud Director 8.10. Legacy vShield Manager Edge appliances are still supported in this release, but we recommend upgrading those Edges to NSX Edges as soon as possible. For information about upgrading NSX Edges, see the vCloud Director Installation and Upgrade Guide.

  • Older vCloud API Versions have been Deprecated
    As of vCloud Director 8.10, the following versions of the vCloud API are deprecated:

    • 1.5
    • 5.1
    • 5.7
    • 5.8
    • 5.9
    • 5.10
    • 5.11
    • 5.12
    • 6.0
    • 7.0
    • 11.0
    • 12.0
    • 14.0
    • 16.0
    • 18.0
    • 19.0

    An API version can be deprecated whenever a newer version of the API supports an equivalent set of features. Use of a deprecated API version is not recommended. Support for an API version can be removed in the release following deprecation.

  • vcloud-console-debug.log no longer used
    Beginning with this release, information formerly logged to vcloud-console-debug.log is now logged to console-proxy.log. Because of this change, existing vcloud-console-debug.log files and any numbered backups are no longer rolled over and removed. You can remove these files manually to reclaim the disk space they consume.

System Requirements and Installation

Compatibility Matrix

See the VMware Product Interoperability Matrixes for current information about:

  • 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 recommended 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.

Disk Space Requirements

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

Memory Requirements

Each vCloud Director server must be provisioned with at least 6GB 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
indutils
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 these packages, which 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 allows you to import 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 requires client connections to be secure. SSL version 3 has been found to have serious security vulnerabilities and is no longer included in the default set of protocols that the server offers to use when making a client connection. The following security protocols are supported:

  • 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 SSL protocols or ciphers. See the Cell Management Tool Reference in the vCloud Director Administrator's Guide.

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 Pro 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.

Supported Guest Operating Systems

Cloud Director supports a wide variety of 32-bit and 64-bit operating systems in its virtual machine templates and virtual machines. VMware recommends that you use version 10, but you can import version 4, 7, 8, and 9 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 or 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

Known Issues

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.