VMware vCenter Orchestrator Plug-In for vCloud Director 1.5 Release Notes
VMware vCenter Orchestrator Plug-In for vCloud Director 1.5 | 17 Nov 2011 | Build 506a
VMware vCenter Orchestrator 4.1 | 13 Jul 2010 | Build 581
VMware vCenter Orchestrator 4.2 | 24 Aug 2011 | Build 5277
VMware vCloud Director 1.5 | 01 Sep 2011 | Build 464915
Last Document Update: 16 Dec 2011
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.5 release runs on VMware vCenter Orchestrator 4.1 and the subsequent update releases, as well as VMware vCenter Orchestrator 4.2. The plug-in is compatible with VMware vCloud Director 1.5. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCloud Director 1.5.
Top of Page
What's New in the vCenter Orchestrator Plug-In for vCloud Director 1.5
Version 1.5 of the vCloud Director plug-in improves the performance and addresses a number of issues. This version includes full support for all new API features of the VMware vCloud API 1.5, including VPN, 5-tuple firewall, linked clones in vDCs, and full feature parity with the API.
Additionally, version 1.5 of the plug-in includes support for triggering workflows based on receiving vCloud messages from events in vCloud Director, as well as workflows that support vCloud Director's blocking tasks mechanism. These mechanisms allow your Orchestrator workflows to dynamically respond to events in your cloud, and allow you to implement task-based integrations with third-party systems.
To upgrade the plug-in, you must install version 1.5 on top of your existing installation. You can download version 1.5 from the VMware vCenter Orchestrator Plug-In for vCloud Director download page.
Top of Page
Earlier Releases of the Center Orchestrator Plug-In for vCloud Director
Features and issues from earlier releases of the vCenter Orchestrator Plug-In for vCloud Director are described in the release notes for each release. To review release notes for earlier releases of the vCenter Orchestrator Plug-In for vCloud Director, click one of the following links:
Top of Page
The following issues have been resolved in the VMware vCenter Orchestrator Plug-In for vCloud Director 1.5 release:
- The VclAdminOrgNetwork.networkPool attribute is not populated in a newly created organization network
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.
This issue is fixed in this release.
- 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.
The issue is fixed in this release and calling the
VclAdminOrganization.getTasksList() method does not result in an error.
- 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 issue is fixed in this release and the workflows run successfully.
- vShield Manager properties cannot be changed when updating vCenter Server configuration
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.
The issue is fixed in this release.
- Full REST API is now exposed in a consistent manner
- Data object serialization works, so you can pass objects for which you do not have a finder, between workflows and actions
- Triggers can now work even if the vCloud Director instance is not in the inventory
- Concurrent logging in and logging out no longer cause issues
- Improvements have been made to the inventory update and trigger mechanism
- Speed of searches for objects by type is improved
Top of Page
The following issues are known to occur in the VMware vCenter Orchestrator Plug-In for vCloud Director 1.5 release:
- New: Incorrect VclOrganization.enabled attribute behavior
VclOrganization.enabled attribute always returns
Workaround: Use the
VclAdminOrganization.enabled attribute instead of the
- Incorrect VclAccessSetting.subject attribute behavior
VclAccessSetting.subject attribute always returns a
VclReference element with a
- The VclFilesList.files attribute is valid only during upload
VclFilesList.files attribute is valid only during the upload process. If you try to access this attribute at any other time, you receive the following error message:
Property named 'files' not found on object : VclFilesList.
- Incorrect VclResourceReference.status attribute behavior
VclResourceReference.status attribute always returns
- The Get a thumbnail workflow does not capture the current virtual machine screen
When you run the Get a 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.
- 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.
- Unable to deploy or power on a vApp while importing it from a vCenter Server instance
If you run the Import a virtual machine as a vApp workflow and try to deploy or power on the vApp, the vApp is neither deployed nor powered on.
Workaround: Run the Deploy a vApp workflow after you import the vApp.
- URL mismatch might cause problematic communication with a vCloud Director cell
If a vCloud Director cell is configured with a URL that does not match the URL of the load balancer, the plug-in cannot resolve objects that come from the vCloud Director cell.
Workaround: Configure the vCloud Director cell to use a matching URL.
- vCloud:VimResourcePool objects are not valid input parameters
You cannot use objects of type
vCloud:VimResourcePool as input parameters of a workflow.
Workaround: Use container objects as workflow parameters and use their methods to get the list of resource pools.
- Invalid option is selectable in the Add a static route workflow for a vApp network
When you run the Add a static route network workflow from the vApp network configuration workflow category, you can select the Internal option as a value for the interface. However, static routing on an internal interface is not supported for vApp networks. Internal is not a valid option and it causes an error when you try to run the workflow.
- Invalid option is selectable in the Wire a virtual machine network workflow
When you run the Wire a virtual machine network workflow, you can select the None option as a value for the IP address allocation mode. None is not a valid option and it causes a validation error when you try to run the workflow.
- Invalid options are selectable in the Add a NAT rule workflow
When you run the Add a NAT rule workflow on an organization network, you can select One To One VM Rule or VM Rule as the rule type. These are not valid options and if selected, cause an error when you try to run the workflow.
- Possible protocol values are not listed in the Add a NAT rule workflow
When you run the Add a NAT rule workflow and select Port Forwarding Rule as the rule type, you must specify the type of protocol to be used. However, the possible values are not listed in the UI. The valid protocol values that you can type are
- Obsolete workflow remains when you upgrade from an earlier version of the plug-in
If you upgrade an earlier version of the plug-in to the vCloud Director 1.5 plug-in, the old Compose vApp workflow remains in the workflow library and the library contains two workflows with the same name. The version of the obsolete Compose vApp workflow is 0.0.15. You cannot use this workflow with version 1.5 of the plug-in. The version of the new Compose vApp workflow is 0.0.7.
- Unable to share vApps and catalogs when using vCenter Orchestrator 4.1
If you install the vCloud Director 1.5 plug-in by using vCenter Orchestrator 4.1 and try to run the Share a vApp or Share a catalog workflows, you receive a validation error.
Note: This issue does not occur with vCenter Orchestrator 4.2.
Workaround: Edit the workflow and remove the custom validation for users and groups from the presentation of the workflow.
Top of Page