This package for the vCenter Orchestrator plug-in for vCloud Director 5.1 or 5.5 allows to trigger custom workflows on vCloud Director blocking tasks and notifications with including:
These are the instructions to have the sample workflows working
The implementation of the workflows is documented in the vCAT 3.0 Workflow Examples Document
UPDATE Sep 9th, 2014: Updated package to include a couple minor fixes, updated description text --> Added notes on additional workflows in package (see BOLD entries in bullet list above), updated instructions to reflect that notification policy should be used and opt for listener workflow if there is trouble with policy)
UPDATE March 11th, 2014: Updated "Create a vCloud Director Notification subscription" workflow to work with vCloud Director 5.5. The change IS backward compatible with vCloud Director 5.1.
Disclaimer: These samples workflows are provided AS IS and are not considered production quality and are not officially Supported. Use at your own risk. Feel free to modify and expand and share your contributions.
"Click on the approve link, login, approve."
The approver link is to the vCloud API - this article doesn't mention setting that up does it?
There were some issues at the time of release for this package that prevented us from including a web based approval for this. One way to implement this is to use the code examples provided here: http://communities.vmware.com/docs/DOC-21144 to have Weboperator provide an approval interface. The other option is to have a custom webview in vCO handle the approval - this is my preferred method and I have the approval webview already created, I just need to find the time to update the package to include this - I was on PTO for the last several days but will see if I can squeeze this in sometime in the near future.
That would be cool, I will keep an eye on this post.
Facing issue while extending Notification package by adding new workflow.
I am trying to extend Notification package by adding new workflow for handling Import OVF as vApp or vApp template in catalog, my new workflow takes following input parameters
Input Type
I created a notification subscription and associate newly developed workflow to it also started subscription listener by executing respective workflows, when I upload OVF for creating vApp from OVF or upload OVF to create vApp template in catalog from VCD. Respective blocking task "vApp Template - Upload vApp Template" initiated and my newly developed workflow get called. Everything seems working except input parameter user vCloud:User object not found, I compare my workflow with other notification workflows but I could not able to figure it out what is wrong or missing.
-- AVR