VMware

VMware vCenter Orchestrator Elastic Service Plug-In 1.0 Release Notes

VMware vCenter Orchestrator Elastic Service Plug-In 1.0 | 06 Dec 2012 | Build 47

VMware vCenter Orchestrator 5.1 | 10 Sep 2012 | Build 2725

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 Elastic Service Plug-In

The VMware vCenter Orchestrator Elastic Service plug-in provides a self-scaling virtual datacenter, by automatically balancing the physical resource between virtual datacenters in VMware vCloud environment. The Elastic Service plug-in helps administrators to monitor virtual datacenter resource usage. The plug-in also automates tasks such as adding physical resource to a virtual datacenter, and removing the spared physical resource from the virtual datacenter.

The Elastic Service plug-in introduces a rule engine to analyze resource usage metrics and make decisions. Administrators can use the predefined workflows to modify the rules in the rule engine. The Elastic Service plug-in can communicate with the AMQP plug-in to forward the resource outage information to a message broker, and other third-party software.

The VMware vCenter Orchestrator Elastic Service Plug-In 1.0 release runs on VMware vCenter Orchestrator 5.1. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Elastic Service Plug-In 1.0.

For information about vCenter Orchestrator and vCenter Orchestrator plug-ins, see:

Top of Page

Known Issues

The following issues are known to occur in the VMware vCenter Orchestrator Elastic Service Plug-In 1.0 release:

  • Unable to update the organization virtual datacenter compute resource

    You cannot update the organization virtual datacenter compute resource by running the predefined workflow.

  • The Data Protection Manager threshold setting fails the host preparation for vCloud Director

    If the cluster's Data Protection Manager (DPM) threshold is set to aggressive, the DPM sets the host into a standby mode when the new host is added to this cluster, and the host preparation task fails.

Top of Page