Introduction to the VMware vCenter Orchestrator Multi-Node Plug-In

As organizations increase their level of automation, they often find the need to deploy multiple Orchestrator instances. With the VMware vCenter Orchestrator Multi-Node Plug-In, administrators have a more efficient way to manage multiple Orchestrator instances from a central point. The plug-in allows administrators to log in to a master Orchestrator server to view the inventories and workflows of remote Orchestrator servers, and to trigger workflows remotely.

The Multi-Node plug-in also makes it easier for administrators to manage workflow packages. From a single Orchestrator server, administrators can push packages to one or more remote Orchestrator servers and ensure that all instances are in sync with the same workflow versions.

What's New in the vCenter Orchestrator Multi-Node Plug-In 5.5.1

Version 5.5.1 of the Multi-Node plug-in adds support for vCenter Orchestrator 5.5.1. It uses the new plug-in configuration API and is not compatible with vCenter Orchestrator versions earlier than 5.5.1
Due to the common SSL trusted store support, all SSL certificates of vCenter Orchestrator hosts are now managed by the Import a certificate from URL workflow, which is shipped with the platform as part of the vCenter Orchestrator Configuration plug-in.

Earlier Releases of the vCenter Orchestrator Multi-Node Plug-In

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

Known Issues

The following issues are known limitations in the VMware vCenter Orchestrator Multi-Node Plug-In 5.5.1 release:

When you run a Proxy workflow its status might be incorrectly displayed as successfully completed

If you run a proxy workflow of an invalid remote workflow, the proxy workflow is incorrectly shown as successfully completed even though the remote workflow is invalid and should not start. This behavior is applicable for both synchronous and asynchronous workflows.

The Multi-Node plug-in does not support answers when user interaction is needed for the remote workflow run

If you run a proxy workflow that requires a user interaction, the proxy workflow cannot send the required information to the remote workflow.