VMware

VMware vCenter Orchestrator AMQP Plug-In 1.0 Release Notes

VMware vCenter Orchestrator AMQP Plug-In 1.0 | 12 Aug 2011 | Build 157

VMware vCenter Orchestrator 4.1 | 13 Jul 2010 | Build 581

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 AMQP Plug-In

The VMware vCenter Orchestrator AMQP plug-in allows organizations to automatically trigger workflows based on AMQP messages. Advanced Message Queuing Protocol (AMQP) is a highly-scalable publish and subscribe message protocol that is increasingly used in cloud architectures. It is the default messaging protocol for vCloud Director 1.5. With the AMQP plug-in, organizations can define policies that automatically trigger specific workflows based on certain AMQP messages. For example, as part of a vApp pre-provisioning activity in vCloud Director, Orchestrator can detect the provisioning request and automatically fetch the IP address from an external system before allowing vCloud Director to proceed with the provisioning activity. When Orchestrator detects that the vApp provisioning is completed, Orchestrator can update configuration management databases and other management systems with information about the new vApp instance.

The AMQP plug-in provides the ability to monitor and publish AMQP messages, as well as to conduct administrative tasks such as configuring AMQP brokers and managing queues. The AMQP plug-in supports VMware RabbitMQ as well as other implementations of AMQP.

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

Top of Page

Known Issues

The following issue is a known limitation in the VMware vCenter Orchestrator AMQP Plug-In 1.0 release:

  • Policies always start normally even though they might not be working

    If you have a subscription to one or more undefined queues and you start the policy, the policy starts normally. Even if you create the queue later, and messages are sent, they do not trigger the policy.

    If you have a subscription to several defined queues and one undefined, and you start the policy, the policy starts normally. Even if you create the undefined queue afterwards, and messages are sent, they do not trigger the policy on either of the queues.

    • Top of Page