vCloud Director 9.1 for Service Providers | 08 March 2018 | Release Build 7905839 (installed build 7905680);
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- What's New in this Release
- System Requirements and Installation
- Deprecated and Discontinued Functionality
- Known Issues
What's New in this Release
For information on the new and updated features of this release, see the VMware Technical White Paper What’s New with VMware vCloud Director 9.1
System Requirements and Installation
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
- Oracle Linux 6
- Oracle Linux 7
- Red Hat Enterprise Linux 6
- Red Hat Enterprise Linux 7
Supported AMQP Servers
vCloud Director uses AMQP to provide the message bus used by extension services, object extensions, and notifications. This release of vCloud Director requires RabbitMQ version 3.6.
For more information, 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 Cassandra database. vCloud Director supports the following Cassandra versions.
- Cassandra 2.2.6 (Deprecated for new installations. Supported for legacy upgrades still using KairosDB.)
- Cassandra 3.x (3.9 recommended)
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.
Each vCloud Director server must be provisioned with at least 6GB of memory.
vCloud Director is a CPU-bound application. CPU overcommittment guidelines for the appropriate version of vSphere should be followed. In virtualized environments, regardless of number of cores available to vCloud Director, there must be a sensible vCPU to physical CPU ratio, one that doesn't result in extreme overcommitting.
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 wget 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|
|New Windows Server 2016||Active Directory||Simple, Simple SSL|
|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 and TLS version 1.0 have been found to have serious security vulnerabilities and are 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.1
- TLS version 1.2
Supported cipher suites include:
Note: Interoperation with releases of vCenter earlier than 5.5-update-3e and versions of
ovftool earlier than 4.2 require vCloud Director to support TLS version 1.0. 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.
The vCloud Director is compatible with the current and last major revision of browsers. Version 9.1 of vCloud Director was tested with and supports:
- Google Chrome 64
- Mozilla Firefox 58
- Microsoft Edge 41
- Microsoft Internet Explorer 11
Note: Flash must be enabled in the browser to access the vCloud Director Web Console.
Note: Use of Microsoft Edge is not supported with vCloud Director installations that use self-signed certificates. Edge also does not support plugins, so functions such as console redirection and OVF upload do not work with Edge.
Supported Guest Operating Systems and Virtual Hardware Versions
vCloud Director supports all guest operating systems and virtual hardware versions supported by the ESXi hosts that back each resource pool.
Deprecated and Discontinued Functionality
End of Life and End of Support Warnings
- Upcoming End of Support for Oracle Database
- vCloud Director 9.1 is the last release of vCloud Director to support Oracle database.
- Upcoming End of Support for vCloud Network Isolation (VCDNI)
- vCloud Director 9.1 is the last release of vCloud Director to support vCloud Network Isolation (VCDNI).
- End of Support for Older vCloud API Versions
- vCloud Director 9.1 no longer supports vCloud API versions 1.5 and 5.1. These API versions were deprecated in a previous release.
- vCloud Director 9.1 is the last release of vCloud Director to support any vCloud API versions earlier than 20.0. Those API versions are deprecated in this release and will not be supported in future releases.
- New Guest customization fails for a Debian guest operating system
If the settings on a Debian guest virtual machine are not in sync with vCloud Director or an attempt to perform a guest customization failed, you cannot power on and force the recustomization of the virtual machine.
vcloud.debian9Guest.isPersonalizationEnabled=trueto the vCloud Director
global.propertiesfile and restart the service.
- New VCDNI deployments of networks do not work in vCloud Director 9.1
Current VCDNI deployments still function upon an upgrade to version 9.1. However, new deployments of networks and edges do not work when a VCDNI network pool is in use, for example, creation of a new network or powering on a vApp, which creates vApp networks and edges. VCDNI is deprecated and is no longer supported.
Workaround: Before upgrading the underlying environment to vCenter Server 6.5 and NSX 6.3.x, you must migrate your VCDNI pools to VXLAN.
- A fast-provisioned VM created on a VAAI enabled NFS array (or VVOLS) cannot be consolidated.
In-place consolidation of a fast provisioned VM is not supported when native snapshot is used. Native snapshots are always used by VAAI enabled datastores, as well as by VVOLs. When a fast provisioned VM is deployed to one of these storage containers that VM cannot be consolidated.
Workaround: Avoid enabling fast provisioning for an organization VDC that uses VAAI-enabled NFS or VVOLS. To consolidate a snapshotted VM on a VAAI/VVOL datastore, relocate it to a different storage container.
- vCloud Director 9.1 supports only the following input parameters of vRealize Orchestrator workflows:
- vCloud Director does not enter in maintenance mode if an LDAP synchronization task is scheduled.
An active vCloud Director cell does not enter in maintenance mode if there is a scheduled
LdapSyncJobtask in the task scheduler queue.
- The vCloud Director REST API does not suggest a POST request link for vApps, virtual datacenters, and organizations.
The vCloud Director REST API suggests only a GET request link for vApps, virtual datacenters, and organizations. For example:
<Link rel="metrics" href="https://vcloud.example.com:8443/api/vApp/vapp-8/metrics/historic" type="application/vnd.vmware.vcloud.metrics.historicUsageSpec+xml"/>
Workaround: Create the POST request link manually. For example:
<Link rel="down" href="https://vcloud.example.com:8443/api/vApp/vapp-8/metrics/historic" type="application/vnd.vmware.vcloud.metrics.historicUsageSpec+xml"/>
- When the runtime lease of a vApp expires, the vApp instance enters in a suspended state.
In vCloud Director 9.1, unlike versions 8.20 and 9.0, after a runtime lease of a vApp expires, the default action is to suspend the vApp instance, instead of power it off.
Use the vCloud API to change this behavior by setting the value of the vApp's PowerOffOnRuntimeLeaseExpiration element to true.
- In the vCloud Director Tenant Portal, the certificates included in an OVF file are not verified during upload.
When uploading an OVF file for creating a vApp or a vApp template in the vCloud Director Tenant Portal, the certificates, if any, available in the OVF file are not verified.
- You cannot specify a name for a media file that is downloaded though the vCloud Director Tenant Portal.
The media files you download though the vCloud Director Tenant Portal are downloaded with a random file name and no file extension.
- The virtual machine console fails to open if you have VMware Workstation or VMware Fusion but do not have VMware Remote Console installed.
If you have either VMware Workstation, or VMware Fusion installed on your local machine but do not have the VMware Remote Console client installed, when you use the Launch VM Remote Console option for a virtual machine, the VMware Workstation or VMware Fusion application opens but fails to load the virtual machine console. The pop-up window that prompts you to install VMware Remote Console does not display either.
Workaround: Install the VMware Remote Console client manually before launching the virtual machine console.
- vCloud Director Tenant Portal users experience HTTP 502 (bad gateway) error responses when the vRO integration is in use.
Additional network traffic generated by this integration can overwhelm load balancers used by vCloud Director and cause this HTTP error.
Workaround: Load balancers used by vCloud Director must be configured with larger buffers (100KB recommended). You might also need to use the cell management tool manage-config subcommand to update the following configuration property:
cell-management-tool manage-config -n vcloud.http.responseHeaderMax -v new-value
where new-value is an integer number of bytes greater than the default value, 65536
- *+json types unsupported by the vCloud API
These output content types have been defined for most vCloud API operations but are not supported for customer use in vCloud API version 30.0