VMware vCenter Orchestrator Plug-In for vCloud Director 5.1 Release Notes
VMware vCenter Orchestrator Plug-In for vCloud Director 5.1 | 10 Sep 2012 | Build 538
VMware vCenter Orchestrator 5.1 | 10 Sep 2012 | Build 2725
VMware vCloud Director 5.1 | 10 Sep 2012 | Build 810718
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 5.1 release runs on VMware vCenter Orchestrator 5.1. The plug-in is compatible with VMware vCloud Director 5.1. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCloud Director 5.1.
Top of Page
What's New in the vCenter Orchestrator Plug-In for vCloud Director 5.1
Version 5.1 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 5.1, including new authentication scenarios, new entities, and operations.
Additionally, version 5.1 of the plug-in includes fully auto-generated object model and fully auto generated scripting actions.
You can download version 5.1 from the VMware vCenter Orchestrator plug-in for vCloud Director download page.
Top of Page
Earlier Releases of the vCenter 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 5.1 release:
- 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.
A warning message appears in the logs if this issue occurs.
Top of Page
The following issues are known to occur in the VMware vCenter Orchestrator Plug-In for vCloud Director 5.1 release:
- Clone operations leave an empty object in the parent virtual datacenter
When you clone an object and select the deleteSource option, the object is moved but the source is not deleted from the cache.
Workaround: Use updateInternalState() function to update the vCloud Director and remove the source from the cache.
- The Set up an AMQP broker workflow does not show all SSL options
When you run the Set up an AMQP broker workflow and select the Use SSL option, the certificates and SSL properties do not appear.
Workaround: Create a custom workflow that uploads the SSL certificate.
- The created hard disk does not attach to a specified virtual machine
When you create a new hard disk and add a virtual machine to attach, the disk is created but it is not attached to the virtual machine.
Workaround: Run Attach a hard disk workflow.
- Not all actions and workflows are removed after Orchestrator, and plug-in upgrade
If you have vCenter Orchestrator 4.1.x or 4.2.x and vCloud Director plug-in 1.x, and you upgrade to Orchestrator 5.1 and vCloud Director plug-in 5.1, some actions and workflows from the plug-in's previous version might remain in the library, but cannot work with version 5.1.
- 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.
Workaround: Power on the virtual machine to get the thumbnail.
- 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.
- 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.
Top of Page