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

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

VMware vRealize Orchestrator Plug-In for vCloud Director 9.5 | 4 October 2018 | Build 10198325

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 9.5

The VMware vRealize Orchestrator plug-in for vCloud Director 9.5 release runs on VMware vRealize Orchestrator 7.x. For information about installing and configuring the vRealize Orchestrator plug-in for vCloud Director 9.5, see Using the vRealize Orchestrator Plug-in for vCloud Director 9.5.

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

After you upgrade the vCloud API schemas to the latest version and bind the new workflow action parameters, the latest vCloud Director features will be available.

If you enable the multi-site connection, version 9.5 allows you to manage and monitor vCloud Director sites and their organizations as single entities. The listing of entities was integrated with the existing workflows and you can retrieve parent and child entities.

Note: To list a child entity, you must select its parent entity.

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.

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
31.00 9.5

 

Host Agent is no longer available and the following actions of VMWHost were deprecated:

          prepareVMWHost
          unprepareVMWHost
          enableVMWHost
          disableVMWHost
          repairVMWHost
          upgradeVMWHost

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 Create disk workflow takes the disk size in megabytes but creates an independent disk in bytes

    The Create disk workflow takes the disk size in megabytes but creates an independent disk in bytes. The input field text is changed from Size (MB) to Size (Bytes).

  • vRealize Orchestrator 9.1 plug-in fails to apply the getAdminVMsByName action

    The getAdminVMsByName action fails with the following error message: Error in (Dynamic Script Module name : getAdminVMsByName#9) TypeError: Cannot find function queryRecords in object DynamicWrapper (Instance) : [VclQueryService]-[classcom.vmware.vmo.plugin.vcloud.model.query.QueryService].

  • For All Certificates workflow, the Submit button becomes active only after you press the Tab button from the Certificate text box

    For all Certificates workflow, after selecting an advanced gateway, the Submit button is inactive. It becomes active only after pressing the Tab button from the Certificate text box.

  • The Add a VPN Tunnel workflow fails after upgrading the vCloud API schema

    The Add a VPN Tunnel workflow fails after upgrading the vCloud API schema, because Peer ID and Local ID values could not be generated due to changes in VPN tunnel implementation.

  • The Add a network pool workflow fails after upgrading the vCloud API schema

    The Add a network pool workflow fails after upgrading the vCloud API schema, because the createFencePoolParams action is deprecated and was replaced with createVxlanPoolParams in vRealize Orchestrator for vCloud Director 9.5 plug-in.

Known Issues

  • Existing workflow actions fail after upgrading the vRealize Orchestrator plugin-in to version 9.5

    Existing workflow actions fail after upgrading the vRealize Orchestrator plugin-in to version 9.5, because of the integration with the latest API schema.

    Workaround: Perform one of the following procedures.