If you want to provide this function in a customer portal, with WaveMaker for example, you need to check the chain length and when the user decides the consolidate method has to be called.
I build a workflow:
The workflow has three steps: determination of the chain length, user decision to consolidate or not and the consolidate call itself. The first part (getChain script) looks like this:
myVm.updateInternalState();
System.log("VM name: "+myVm.name);
var doc = new XML(myVm.toXml());
default xml namespace = doc.namespace();
var n8 = new Namespace("http://www.vmware.com/vcloud/extension/v1.5");
System.log("ChainLength: "+doc.VCloudExtension.*::VmVimInfo.*::VirtualDisksMaxChainLength);
var chainLength = doc.VCloudExtension.*::VmVimInfo.*::VirtualDisksMaxChainLength;
if(myVm.vmStatus.value != 8){
throw("VM is not powered off!");
}
As you can see I update the state of "myVM" (vCloud:VM) and setting the variable "chainLength" (number). The chain length is used as external input for the user interaction, so it´s possible to decide based on the count.
After the submission the myVm.consolidate() method is called and the workflows waits for it.
With my host.login() workflow you can combine the Org based login with the consolidation of vCloud:VM´s :)
It gives exhaustive learning of the subject. Everything written in this blog is near acceptable level. I am certain nobody can raise any issue about all the data conveyed here. Veeam Availability Suite for HyperV
ReplyDelete