Appendix E: Integrating with Existing Enterprise System Management : vCloud Director Notifications and Blocking Tasks Messages : Extension : vCenter Orchestrator as an Extension Example
   
vCenter Orchestrator as an Extension Example
This section shows a simple example leveraging the blocked tasks as a trigger mechanism for starting extension workflows using different vCenter Orchestrator plug-ins.
As a prerequisite, a subscription to an AMQP queue, bound to the exchange used by vCloud director, was created using the workflows listed in the previous section. As part of this, the routing key is set to filter on vApp creation (#.blockingtask.create.vdcInstantiateVapp).
Next an Approve new vApp policy is created to listen on new messages. It is set to start the Approve a vApp workflow.
Figure 34. vCenter Orchestrator AMQP Subscription Policy
Screen shot 2011-07-12 at 4.22.26 PM.png
 
The Approve a vApp workflow is designed as shown in the following table.
Table 18. Approve a vApp Workflow
Workflow
Description
Plug-in in use
Important information is extracted from the subscription message such as the name of the vApp requester and the scaffold object of the vApp being requested.
AMQP
The detailed properties of the requested vApp are gathered.
vCloud Director
The vApp requester’s manager name and email is found in Active Directory, an email is sent to approve the vApp. It contains all the details gathered before.
Active Directory and mail
The workflow is stopped until the approver follows the link in his email, authenticates using his Active Directory credential, and approves or rejects the vApp.
 
Depending on if the vApp was approved or not, the aborted task is resumed or aborted. An email message is sent to the requester.
vCloud Director and mail