VMware

VMware vCloud Director 1.0.1 Release Notes

VMware vCloud Director 1.0.1 | 10 FEB 2011 | Build 356485

Last updated: 10 FEB 2011

VMware vCloud Director provides the interface, automation, and management required by enterprises and service providers to build private and public clouds. vCloud Director:

  • Supports multi tenancy/organizational isolation
  • Allows for the creation of central application catalogs and personalization of templates
  • Enables creation and deployment of vApps from catalogs/templates
  • Controls user resource usage through roles/rights, quotas and leases
  • Enables programmatic control through the RESTful vCloud API
  • Provides an additional level of abstraction from underlying hardware

What's in the Release Notes

The release notes cover the following topics:

New Features

This section describes the new features in vCloud Director 1.0.1.

vSphere 4.1 Update 1 Support

vCloud Director 1.0.1 adds support for vCenter Server 4.1 Update 1 and ESX/ESXi 4.1 Update 1.

Internationalization (I18N) Level 1 Support

vCloud Director 1.0.1 complies with I18N Level 1. Although vCloud Director is not localized, it can run on non-English operating systems and handle non-English text. See I18N Issues for known issues.

IP Translation for Organization Networks

vCloud Director 1.0.1 allows you to add IP translation rules for organization networks. When you create an IP translation rule for a network, vCloud Director adds a DNAT and SNAT rule to the vShield Edge associated with the network's port group. The DNAT rule translates an external IP address to an internal IP address for inbound traffic. The SNAT rule translates an internal IP address to an external IP address for outbound traffic. If the network is also using IP masquerade, the SNAT rule takes precedence.

Only system administrators and organization administrators can add IP translation rules. You must have an available external IP address and an external NAT-routed organization network.

To add an IP translation rule to an organization network:

  1. Right-click the organization network name and select Configure Services.
  2. Click the NAT- External IP Mapping tab and click Add.
  3. Select IP Translation and configure the IP translation rule.
    1. Select an external IP address.
    2. In the Internal IP field, type the IP address of the destination virtual machine.
      • If the virtual machine is fenced, type its external IP address.
      • If the virtual machine is not fenced, type its IP address.
  4. Click OK.
  5. Click OK.

System Requirements

vCloud Director 1.0.1 adds support for vCenter Server 4.1 Update 1 and ESX/ESXi 4.1 Update 1. Otherwise, vCloud Director 1.0.1 has the same system requirements as vCloud Director 1.0. See the VMware vCloud Director Installation and Configuration Guide.

Upgrading to vCloud Director 1.0.1

If you are installing vCloud Director for the first time, follow the installation instructions in the VMware vCloud Director Installation and Configuration Guide.

vCloud Director software is distributed as a Linux executable file named vmware-cloud-director-1.0.1-356485.bin. Running this file requires superuser (root) privileges.

The upgrade process is slightly different depending on whether your vCloud Director installation has one cloud cell or multiple cloud cells.

Upgrading a vCloud Director Installation with a Single Cloud Cell

This scenario describes how to upgrade a vCloud Director installation with a single cloud cell.

To upgrade a single cloud cell:

  1. Log in to the target server as root.
  2. Download the installation file to the target server.
  3. Ensure that the installation file is executable.
    The installation file requires execute permission. To be sure that it has this permission, open a console, shell, or terminal window and run the following command:

    chmod u+x installation-file

    where installation-file is the full pathname to the vCloud Director installation file.
    For example, chmod u+x ./vmware-cloud-director-1.0.1-356485.bin.
  4. Gracefully shut down the cell as described in KB 1033575.
  5. In a console, shell, or terminal window, run the installation file and type y to upgrade.

    You must type the full pathname to the installation file. For example, ./vmware-cloud-director-1.0.1-356485.bin.
    As part of the upgrade, the installer unpacks the vCloud Director RPM package, stops vCloud Director services on the server (if they are running), and backs up important configuration files.

  6. Start the cloud cell by typing the following command:

    service vmware-vcd start

Upgrading a vCloud Director Installation with Multiple Cloud Cells

This scenario describes how to upgrade a vCloud Director installation with multiple cloud cells that are behind a load balancer.

To upgrade a multi-cell installation:

  1. Split the cells into two pools (A and B).
  2. Edit the load balancer configuration so that all traffic is sent to pool A.
  3. Gracefully shut down all cells in pool B (see KB 1033575).
  4. For each cell in pool B, upgrade the cell.
    1. Log in to the target server as root.
    2. Download the installation file to the target server.
    3. Ensure that the installation file is executable.
      The installation file requires execute permission. To be sure that it has this permission, open a console, shell, or terminal window and run the following command:

      chmod u+x installation-file

      where installation-file is the full pathname to the vCloud Director installation file.
      For example, chmod u+x ./vmware-cloud-director-1.0.1-356485.bin.
    4. In a console, shell, or terminal window, run the installation file and type y to upgrade.

      You must type the full pathname to the installation file. For example, ./vmware-cloud-director-1.0.1-356485.bin.
      As part of the upgrade, the installer unpacks the vCloud Director RPM package, stops vCloud Director services on the server (if they are running), and backs up important configuration files.

  5. On one cell (machine C) in pool B, start the maintenance message by typing the following command:
    $VCLOUD_HOME/bin/vmware-vcd-cell maintenance
  6. Edit the load balancer configuration so that all traffic is sent to machine C.
  7. Gracefully shut down all cells in pool A (see KB 1033575).
  8. Start all the cells in pool B by typing the following command for each cell:

    service vmware-vcd start
  9. Edit the load balancer configuration so that all traffic is sent to pool B (except machine C).
  10. On machine C, shut down the maintenance message and then restart the cell:

    service vmware-vcd restart
  11. Edit the load balancer configuration so that all traffic is sent to pool B (including machine C).
  12. For each cell in pool A, upgrade the cell.
    1. Log in to the target server as root.
    2. Download the installation file to the target server.
    3. Ensure that the installation file is executable.
      The installation file requires execute permission. To be sure that it has this permission, open a console, shell, or terminal window and run the following command:

      chmod u+x installation-file

      where installation-file is the full pathname to the vCloud Director installation file.
      For example, chmod u+x ./vmware-cloud-director-1.0.1-xxxxxx.bin.
    4. In a console, shell, or terminal window, run the installation file and type y to upgrade.

      You must type the full pathname to the installation file. For example, ./vmware-cloud-director-1.0.1-xxxxxx.bin.
      As part of the upgrade, the installer unpacks the vCloud Director RPM package, stops vCloud Director services on the server (if they are running), and backs up important configuration files.

  13. Start all the cells in pool A by typing the following command for each cell:

    service vmware-vcd start
  14. Edit the load balancer configuration so that traffic is sent to all the cloud cells.

Known Issues

The following known issues have been discovered through rigorous testing and will help you understand some behavior you might encounter in this release.

The known issues are grouped as follows:

I18N Issues

Guest customization tab does not support non-ASCII characters
You cannot enter non-ASCII characters into any of the text fields on the Guest Customization tab of the Virtual Machine Properties page. This includes the local administrator password; the domain name and its user name and password; and the customization script.

Cannot upload OVFs with non-ASCII names
If you export a vSphere vApp that includes non-ASCII characters in its name and then try to import the resulting OVF into vCloud Director, the upload may fail. As a workaround, you can type a name using ASCII characters when you export the vSphere vApp as an OVF template.

Cannot create local user accounts with non-ASCII characters
vCloud Director does not support non-ASCII characters in the user names for local user accounts. You can import LDAP users whose names include non-ASCII characters.

Cannot create organization with non-ASCII characters
vCloud Director does not support non-ASCII characters in organization names.

General Issues

"Too many open files" errors
vCloud Director can require high open file limits. Make sure that every cell in your vCloud Director environment allows processes to open more than 1024 files. To see what the current limit is for a cell, log in to the cell, and type ulimit -n. If it says 1024 or less, then take the following steps to increase the open files limit:

  1. Type su -.
  2. Edit /etc/security/limits.conf and make sure it includes the following lines:

    * soft nofile 65535
    * hard nofile 65535
  3. Edit /etc/pam.d/login to include the following line:

    session required pam_limits.so
  4. Type the following command to restart the cell:
    service vmware-vcd restart
  5. Log out of the cell and log back in.
  6. Type ulimit -n to verify your changes.

Cannot change vCloud Director database user name or password while services are running
If you change the vCloud Director database user name or password while services are running, vCloud Director will fail at the next database access and log a message of the form "java.sql.SQLException: ORA-01017: invalid username/password; logon denied". Use the following procedure if you need to change the vCloud Director database user or password:

  1. Stop all vCloud Director services on all cells, as described in the VMware vCloud Director Installation and Configuration Guide.
  2. Using database tools, change the vCloud Director database user or password.
  3. Run the vCloud Director configuration script on all cells, as described in the VMware vCloud Director Installation and Configuration Guide (see "Configuring Network and Database Connections").
    The script first asks for the Java keystore path and password and then prompts you for the new user name/password for the database.

After you complete the script, it updates the information in the vCloud Director database and properties files and re-starts vCloud Director services.

Unable to create a Microsoft Sysprep deployment package
If you get a permission denied error when running the createSysprepPackage.sh script on a cell, you should check to see if SELinux is enabled and running in enforcing mode. To check, run the following command: /usr/sbin/getenforce. If it returns "Enforcing", perform the following workaround to grant the appropriate permissions to run the tool.

Workaround: Enable text-relocation for the shared library used by the script. Run following command as root after vCloud Director is installed: chcon -t textrel_shlib_t '/opt/vmware/cloud-director/deploymentPackageCreator/libCreatePkg.so'

"Running VMs" count includes VMs that provide network services and might include powered off VMs
The "Running VMs" column in the organizations list (Manage & Monitor > Organizations) displays the total number of virtual machines in started vApps. This includes virtual machines that provide network services (vShield Edge VMs) and might also include virtual machines that are not running (for example, powered off virtual machines).

Error when importing media files from vSphere
If you get a "String index out of range: -1" error when you attempt to import a media file from the root of a vSphere datastore, make sure the path starts with "/" (for example, /media-cd.iso) and try again.

Accessing vCloud Director with a Web browser
vCloud Director does not support logging in to different user accounts from the same browser at the same time. If you attempt to do so, the first user is logged out.

vSphere Issues

Empty folders in vSphere inventory
When you delete a provider vDC in vCloud Director, an empty folder representing the provider vDC continues to exist in the VMs and Templates inventory in the vSphere database. You can manually remove the folder to clean up the inventory.

Cannot import vSphere templates
vCloud Director does not support importing templates from vSphere, it only supports importing virtual machines. You can use the vSphere Client to convert a template to a virtual machine and then import it into vCloud Director. You can also use the vSphere Client to deploy a virtual machine from a template and then import the virtual machine into vCloud Director.

Organization vDC Issues

Cannot delete an organization vDC or catalog
If you are unable to delete an organization vDC or a catalog because it still contains vApps or vApp templates, make sure to check My Cloud > Expired Items. After you delete the expired vApps in an organization vDC, you can delete the organization vDC. After you delete the expired vApp templates in a catalog, you can delete the catalog.

Processor column incorrectly displays GHz
When you open an organization vDC and view the Processor column on the vApp tab, vCloud Director displays a number followed by "GHz" for each vApp. The numbers in this column actually represent the total number of virtual processors in the vApp, and not the total GHz used by those processors.

Deleting an organization vDC from the API versus from the UI
When you delete an organization vDC using the API, vCloud Director deletes any vApps, vApp templates, and media in the organization vDC. Make sure to move any objects you want to keep before you delete the organization vDC. When you delete an organization vDC using the UI, Cloud Director deletes any vApp templates in the organization vDC. Make sure to move any vApp templates you want to keep before you delete the organization vDC.

Cannot start a vApp in a Reservation Pool organization vDC
Users can set memory and CPU reservations for their virtual machines in a Reservation Pool organization vDC. As a result, it is possible for users to reserve all the available memory and CPU in the organization vDC for their virtual machines. In this case, they would not be able to start a vApp that requires a vShield Edge virtual machine to provide network services, since there would be no memory or CPU available.

Upload and Download Issues

Upload fails to transfer files
If you previously installed the beta version of vCloud Director may see a Java security warning or a "java.lang.ExceptionInInitializationError" in the Java plug-in console when attempting to upload a vApp template or media file. In this case, clear the Java applet / application cache.

  1. Navigate to Control Panel > Java.
  2. On the General tab, click Settings in the Temporary Internet Files section.
  3. Click Delete Files.
  4. Make sure that Applications and Applets is selected and click OK.

Java plug-in issues
In order to upload vApp templates and media to a catalog, the computer from which you are uploading must have Java Plug-in 1.6.0_10 or later installed. In some cases, even after you install the plug-in you will not be able to upload files until you restart your Web browser.

Paused or canceled upload times out
When you pause or cancel an upload media or upload vApp template task, that task is subject to an upload timeout (one hour, by default). If you do not resume the task before the timeout, the task fails. An upload task that is in progress is not affected by the timeout.

Paused downloads display as "Canceled"
When you pause a vApp template download, the Download Progess Window incorrectly displays "Canceled". You can click the Resume button to continue the download.

Cannot upload files without using the Browse button
If you type or paste the path to the source file when uploading a vApp template or media file, the upload may fail with no error message. In this case, click the Browse button to locate the source file instead.

Virtual Machine Issues

Virtual machine console page shows an empty box in Mozilla Firefox 3.6 on Linux
Some versions in Firefox 3.6 series strip executable permissions on files that are extracted from the XPI plug-in binary. The console plug-in does not load correctly and the console page appears blank. To resolve the issue, browse to the console plug-in installation folder at /<Firefox_profile_folder>/extensions/VMwareMKSNPRTPlugin@vmware.com/plugins/ and run the command chmod 755 * to manually enable permissions on the files of that folder.

Unable to hot add memory or CPU
Under certain circumstances, you may not be able to hot add memory or CPU to virtual machines running in Allocation Pool or Reservation Pool organization vDCs. In this case, you can power off the virtual machine, add the memory or CPU, and then power on the virtual machine.

Networking Issues

Unable to delete an organization network
Before you can delete an organization network, you must make sure that no virtual machines are connected to it. If a vApp template in a catalog requires the organization network, you can delete the vApp template (if you don't need it anymore) or take the following steps to create a new vApp template that does not use the network you want to delete:

  1. From the catalog, add the vApp template to My Cloud.
  2. Delete the vApp template from the catalog.
  3. In My Cloud, open the vApp and make sure that none of its virtual machines connect to the organization network you want to delete.
  4. Remove the organization network from the vApp.
  5. Add the vApp to the catalog.
  6. Delete the vApp.

You can now delete the organization network.

vCloud API Issues

  • A vApp that displays as "Fenced" in the UI may have its vApp network Configuration FenceMode displayed as "natRouted" when retrieved in the vCloud API. If the IP subnet on the vApp network overlaps the IP subnet on the external network, then the vApp is actually deployed fenced. If the IP subnets on the two do not overlap, it is natRouted.

  • When a cloneVapp or cloneVappTemplate request is made with the vCloud REST API, the value of the name attribute in the request body is ignored, and the cloned object retains the name of the Source object.

  • GET vmext:ResourcePoolList requests might fail with an XML validation error (Invalid content).

  • When a cloneVapp request is made with the vCloud REST API, the deploy and powerOn attributes in the request body are ignored.

  • Until a ProviderVdc has been created, a GET request for networkPoolReferences or externalNetworkReferences will return an empty list even though network pools and external networks exist.

  • The response to a registervimserver request might include an invalid content message of the form "Invalid content was found starting with element vmext:AssociatedVimServer." This response does not indicate that the request failed.

  • Attempts to use the vCloud API to specify a memory reservation or limit when editing the VirtualHardwareSection of a Vm are silently ignored when the Vm is in a vDC whose AllocationModel has the value AllocationPool or AllocationVapp.

  • If you encounter errors (for example, "OperationDeniedException - Operations not in users context") when using the vCloud API to import LDAP users into an organization, log out and log in, then try to import the users again.

  • When a system administrator uses the REST API to instantiate a vApp template from a shared Catalog in a vDC owned by an organization other than the one that owns the shared catalog, the vApp owner is set to a member of the organization that owns the catalog, not the organization that owns the vDC. When any other use performs this operation, the vApp owner is set correctly.

  • When you instantiate a vApp template and specify a FenceMode value of isolated, the vApp network is created with a FenceMode of natRouted.

  • A Vdc response body can contain one or more Link elements with a rel attribute value of move. These links are inoperative, and will be removed in a future release.

Resolved Issues

Networking issues on virtual machines running certain guest operating systems
This release fixes an issue that affected some vCloud Director-created virtual machines running on ESX/ESXi 4.1 hosts. For virtual machines created with the following guest operating systems, vCloud Director set the incorrect network adapter type:

  • Microsoft Windows 7 (32 bit)
  • Microsoft Windows Vista (32 bit)
  • Microsoft Windows Server 2003 Enterprise Edition (32 bit)
  • Microsoft Windows Server 2003 Datacenter Edition (32 bit)
  • Microsoft Windows Server 2003 Standard Edition (32 bit)
  • Microsoft Windows Server 2008 (32 bit)
  • Suse Linux Enterprise 11 (32 bit)
  • Debian GNU/Linux 5 (32 bit)
  • Debian GNU/Linux 4 (32 bit)
  • Novell Netware 6.x
  • Novell Netware 5.1
  • Sun Solaris 10 (32 bit)
  • Sun Solaris 9 (experimental)
  • FreeBSD (32 bit)

vCloud Director 1.0.1 resolves this issue.