check-circle-line exclamation-circle-line close-line

VMware vRealize Orchestrator Plug-In for vCloud Director 9.1 Release Notes

VMware vRealize Orchestrator Plug-In for vCloud Director 9.1 | 8 March 2018 | Build 7876914

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 vRealize Orchestrator Plug-In for vCloud Director

The VMware vRealize 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. vRealize 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 vRealize Orchestrator plug-in for vCloud Director 9.1 release runs on VMware vRealize Orchestrator 7.x. The plug-in is compatible with VMware vCloud Director 9.1. For instructions about installing and configuring the vRealize Orchestrator plug-in for vCloud Director 9.1, see Using the vCenter Orchestrator Plug-In for vCloud Director 5.5.

What's New in the vRealize Orchestrator Plug-In for vCloud Director 9.1

VMware vRealize Orchestrator plug-in for vCloud Director 9.1 introduces various new workflows designed to cover the NSX-based networking components that are available in vCloud Director. With these workflows, you can manage first-entity networking configuration objects, such as Firewall, NAT, DHCP pools, DHCP bindings, and Certificates. You can create, edit, or delete instances of these objects. The plug-in also includes workflows for managing advanced gateways and legacy gateways.

By only switching the host connection, version 9.1 of the plug-in makes it possible for multiple users to initiate workflows against vCloud Director instances on version 8.10, 8.20, 9.0, and 9.1 simultaneously from a single instance of the vRealize Orchestrator plug-in for vCloud Director 9.1 plug-in.

Note: When managing multiple vCloud Director instances running on different versions, you must create a connection to each one of them separately and specify the API version that each version of vCloud Director supports.

Fig.1 API Version compatibility with vCloud Director

API version vCloud Director version
20.00  8.10
27.00  8.20
29.00  9.0
30.00  9.1

You can download version 9.1 from the VMware vRealize Orchestrator plug-in for vCloud Director download page.

Earlier Releases of the vRealize Orchestrator Plug-In for vCloud Director

Features and issues from earlier releases of the vRealize Orchestrator plug-in for vCloud Director are described in the release notes for each release. To review release notes for earlier releases of the vRealize Orchestrator plug-in for vCloud Director, click one of the following links:

Resolved Issues

  • The Add a gateway workflow fails.

    The Add a gateway workflow fails with an error message “Cannot convert compact to com.vmware.vmo.plugin.vcloud.model.schema.objects.GatewayInterfaces”.

  • The Add a storage profile workflow fails.

    The Add a storage profile workflow fails with an error message “"TypeError: Cannot find function getReference in object 100. (Dynamic Script Module name: createVdcStorageProfileParams#8)'".

  • The Update a storage profile workflow fails.

    The Update a storage profile workflow fails with an error message “com.vmware.vmo.plugin.vcloud.model.admin.ProviderVdcStorageProfile@4ebc38a6 is not a valid unit. Please use MB; majorErrorCode=400; minorErrorCode=BAD_REQUEST; vendorSpecificErrorCode=null;”.

Known Issues

  • The Add a NAT rule workflow is deprecated. 

    The Add a NAT rule workflow is deprecated and will be removed in the next version.

    Workaround: Use Add a NAT rule [9.1]. This workflow supports both Legacy and Advanced Gateway.

  • When running the Add a firewall rule workflow for a legacy gateway, the firewall rule name remains empty if you do not enter text in the description field.

    When you run the Add a firewall rule workflow, if you do not enter text in the description field, the firewall rule name is not saved.

    Workaround: Enter text in the description field of the workflow

  • When you run a workflow for creating a certificate, the Submit button does not appear as enabled.

    When you run a workflow for creating a certificate, the Submit button does not appear as enabled if you keep the cursor in a text field for certificate details.

    Workaround: Tab out from the text field for certificate details.

  • You can run the Self-Sign a CSR Certificate workflow without selecting CSR certificate and specifying Number of Days

    You can run the Self Sign a CSR Certificate workflow without selecting CSR certificate and specifying Number of Days. This leads to an invalid certificate.

    Workaround: Select CSR certificate and Number of Days before you submit the Self Sign a CSR certificate workflow.