Hi All,
I've successfully gotten the com.vmware.coe.vcd51.notifications.package update package working with vCO 5.5 and vCD 5.5. After setting up the "Create a vCloud Director notification subscription" to trigger on "instantiate vApp from template" i can now run a specified workflow in vCO.
I need to use a custom IPAM using a REST API which i've found plenty of documentation/examples on how to do, however what's not so crystal clear is the rest.
I've been studying the examples that come with the notifications package, and also the com.vmware.coe.vcd51.vapp.customdeploy.package workflow which would have suited perfectly if only it where meant to be triggered by AMQP blocking tasks.
1. i get a blocking task in a queue through the AMQP which is cought by a listener workflow. It seems however whats actually getting executed is the statically configured workflow "Workflow runner" that does some magic and then triggers the workflow i specified. When looking into "Customize VMs name and IPs" workflow it seems that the first thing it does is resume the blocking task, i assume this should trigger vCloud to continue to create the vApp, and then the workflow should receive a new blocking task once this is done to do the modification?
Is this how it's designed to work, that customization is done post-deployment instead of pre-deployment? I've tried to set the Customize VMs name and IPs as the destination workflow from the notification subscription but it generates 6 failed workflows in a row each time with various errors. ( 2014-03-11 14:31:55.125] [I] TypeError: Cannot call method "getTask" of null (Workflow:Customize VMs name and IPs / Resume Blocking Task (item8)#2) ) Is this workflow supposed to be called from another workflow or directly from the notification subscription?
2. What are good resources to study to be able to create such a workflow?
3. Does anyone have a workflow they can share that one could build on, or that might be clear and simple on how to work with blocking tasks?
//Kim