Here is my understanding ... Straight Suspend does not free the reservations .... Suspend needs to keep the reservations there so you can ensure a resume succeeds. this is just for CPU/MB reservations on the VMs/pools.
Stop will also undeploy, but powers off the VMs ... same as a 'stop' from the UI.
Either of these should be fine for you to perform, since the goal is to power off VMs to take a SAN snap, just that suspend takes that much longer.
plenty o documents here: http://communities.vmware.com/community/vmtn/developer/forums/vcloudapi
However, I do not recall a mass "suspend" or power off for vCloud Director.
Thanks for your response, but I was looking for something like Lab Manager 4.0 Internal APIs. LM used to have ManagedServerPerformAction, action 3 for Undeploy all VMs for a host.
I don't think that's an option in vCloud Director's website, nor API.
IN Lab Manager undeploy meant something special .. power off and remove from inventory.
vCloud Director doesn't do that, since all VMs should be resident in vCenter's inventory.
The nearest neighbor is the 'redeploy all VMs', but for vCloud, that just enters maintenance mode.
In vApp Workflows under "vApp Power Workflows", there is a Workflow named "Undeploy a vApp" : Stops or suspends a vApp and frees the resources reserved for the vApp. Do you know what resources are freed if I use it instead of "Suspend a vApp": Suspends a vApp. Does not free the resources reserved for the vApp? I'm planning to use vCO for the task of suspending all running vApps.
Thanks!
Here is my understanding ... Straight Suspend does not free the reservations .... Suspend needs to keep the reservations there so you can ensure a resume succeeds. this is just for CPU/MB reservations on the VMs/pools.
Stop will also undeploy, but powers off the VMs ... same as a 'stop' from the UI.
Either of these should be fine for you to perform, since the goal is to power off VMs to take a SAN snap, just that suspend takes that much longer.
Thank you.