VMware

VMware vCenter Orchestrator Plug-In for vCloud Director 1.0.2 Release Notes

VMware vCenter Orchestrator Plug-In for vCloud Director 1.0.2 | 13 Sep 2011 | Build 643

VMware vCenter Orchestrator 4.1 | 13 Jul 2010 | Build 581

VMware vCloud Director 1.0 | 30 Aug 2010 | Build 285979

VMware vCloud Director 1.0.1 | 10 Feb 2011 | Build 356485

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Introduction to the VMware vCenter Orchestrator Plug-In for vCloud Director

The VMware vCenter Orchestrator plug-in for vCloud Director allows cloud administrators to simplify the management of their cloud infrastructure by extending the robust workflow automation platform of VMware to the vCloud environment. These workflows are built using the drag-and-drop capability of the workflow editor in the Orchestrator client. vCenter Orchestrator uses the plug-in to access the functionality of vCloud Director and the vCloud API. The included, pre-built workflows simplify the process to get you started with custom workflow creation.

The VMware vCenter Orchestrator plug-in for vCloud Director 1.0.2 release runs on VMware vCenter Orchestrator 4.1. The plug-in is compatible with VMware vCloud Director 1.0 and 1.0.1. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCloud Director 1.0.x.

Top of Page

What's New in VMware vCenter Orchestrator Plug-In for vCloud Director 1.0.2

Version 1.0.2 of the vCloud Director plug-in improves the performance, addresses a number of issues, and includes the sample workflow package. To upgrade the plug-in, you must install version 1.0.2 on top of your existing installation. You can download version 1.0.2 from the VMware vCenter Orchestrator Plug-In for vCloud Director download page.

Top of Page

Resolved Issues

The following issues have been resolved in the VMware vCenter Orchestrator Plug-In for vCloud Director 1.0.2 release:

  • Long running workflows might cause Orchestrator to stop responding

    If several users are running workflows simultaneously for an extended period of time, Orchestrator might stop responding and the state of all active workflows remains unchanged.

  • Error message displayed when trying to set the CPU value of a virtual machine

    When you try to set the CPU value of a virtual machine, you receive an error message for incompatible types.

  • Incorrect vCPU speed

    When you try to create or update an organization vDC with allocation mode type Allocation vApp (Pay-As-You-Go), the value of the vCPU is not applied correctly.

  • The vCloud Director plug-in configuration file might cause problems with handles

    The vCloud Director plug-in configuration file opens handles without closing them, which might cause the Orchestrator server to run out of handles and stop working properly.

Top of Page

Known Issues

The following issues are known to occur in the VMware vCenter Orchestrator Plug-In for vCloud Director 1.0.2 release:

  • Slow UI response when displaying large lists of vCloud Director objects

    If you expand a vCloud Director infrastructure object that contains many child objects, for example, more than 200 vApps in a vDC, loading all objects might take a considerable amount of time. The reason for the delay is that the underlying plug-in inventory object must call the REST API element by element in order to fetch additional element properties such as name, description, size, and networks.

    Workaround: Try to balance the number of elements in the infrastructure. For example, you can split the number of vApps between many organizations in order to prevent huge number of vApps to appear under the same organization and vDC.

  • The VclAdminOrgNetwork.networkPool attribute is not populated in a newly created organization network

    The VclAdminOrgNetwork.networkPool attribute always returns null in a newly created organization network.

    Note: When the network type is NAT-routed, the VclAdminOrgNetwork.allowedExternalIpAddresses attribute is also not populated.

  • Calling the VclAdminOrganization.getTasksList() method results in an error

    When the script calls the VclAdminOrganization.getTasksList() method, the following error message appears: InternalError: com.vmware.vcloud.sdk.admin.AdminOrganization cannot be cast to com.vmware.vcloud.sdk.Organization.

  • Incorrect VclAccessSetting.subject attribute behavior

    The VclAccessSetting.subject attribute always returns a VclReference element with a null name.

  • The VclFilesList.files attribute is valid only during upload

    The VclFilesList.files attribute is valid only during the upload process. If you try to access this attribute at any other time, the following error message appears: Property named 'files' not found on object : VclFilesList.

  • Incorrect VclResourceReference.status attribute behavior

    The VclResourceReference.status attribute always returns null.

  • The Add Org Network and Add VMW Provider Network workflows cannot run successfully when more than one IP range is entered

    If you specify more than one IP range when trying to run the Add Org Network or Add VMW Provider Network workflow, the following error message appears: Could not execute JDBC batch update - ORA-04091: table VCLOUD.IP_RANGE is mutating, trigger/function may not see it ORA-06512: at "VCLOUD.TR_LIMIT_IP_RANGE_INSERT", line 7 ORA-04088: error during execution of trigger 'VCLOUD.TR_LIMIT_IP_RANGE_INSERT'.

  • The Get Thumbnail workflow does not capture the current virtual machine screen

    When you run the Get Thumbnail workflow on a newly created virtual machine, a .png file is created, but the file has no content. If you have manually accessed the virtual machine's console through the vCloud Director UI, the .png file is not empty. However, the downloaded thumbnail might be outdated.

  • vShield Manager properties cannot be changed when updating vCenter Server

    If you run the Update VIM Server workflow to change a vCenter Server configuration, the new properties for the associated vShield Manager cannot be applied.

    Workaround: Unregister the vCenter Server from the vCloud Director instance, and then register it again with the new properties for the associated vShield Manager.

  • The Add Connection workflow might not run successfully when using a non-secure connection

    If you configure the Add Connection workflow to use session-per-user mode and not to use secure channel, the workflow might not run successfully.

    Workaround: Configure the workflow to use a secure channel connection.

Top of Page