No Shutdown option via GUI in 5.1.1?

[CSIEnvironments]

In vCloud Director 5.1.1 how do I shutdown the guest vm's without undeploying the entire CIvApp? If I right click on the CIvApp there are 2 options, stop and force stop. Both of which undeploy the CIvApp which means the vm's lose their external ip addresses if they obtained by an IP Pool.

I am trying to get the same result with the GUI as I achieve with PowerCLI with the command: (Get-CIvApp "Sandbox").ExtensionData.Shutdown()

The CIvApp should be left in a Partially Running State.With the VM's shutdown/powered off with the CIvApp still deployed.

So all I want to do is shutdown the guests vms, not undeploy the entire CIvApp.

Thanks!

[IamTHEvilONE]

Right clicking the vApp itself, gives power state options for the entire vApp.  Stop and force stop.

If you go into the vApp itself you can shut down the vApp

Otherwise, you have to perform actions on the individual VMs instead of the entire vApp.

"Both of which undeploy the CIvApp which means the vm's lose their external ip addresses if they obtained by an IP Pool."

if this matters, why not just enable the ability to keep the external IP consistent.

[CSIEnvironments]

Thanks for the response. We migrated from LabManager which had this feature. I understand vCD is CIvApp based, but I would have thought a simple feature such as a 1 click solution to "Shutdown only guest VM's" would be possible from the GUI?

"Otherwise, you have to perform actions on the individual VMs instead of the entire vApp."

This would be ok if vCloud Director displayed all 50 VM's on a page, but currently it only displays 22. So the process is not 1 click, its: select all, power off, next page, select all, power off, next page etc....

"if this matters, why not just enable the ability to keep the external IP consistent."

There are a few reason why we do not use statically assigned external IP's, but the main reason is our custom in-house software built around the functionality. Secondly we rip and replace far to often to cater for static external IP's without heavily investing time into VMWare Orchestrator or PowerCLI.

Is there a specific reason VMWare does not want us to keep the CIvApp running but with the Guest VM's shutdown?

[CSIEnvironments]

Also the option to undeploy or stop a specific VM in CIvApp does not exist from the gui. If I want to free up the networking resources of a few VM's in a CIvApp without deleting the actual machines, I can't without using PowerCLI or the API.

Seems in terms of the gui we have taken two steps forward and 1 step back.

[IamTHEvilONE]

yes ... Lab Manager had two terms ... Shut down vs Undeploy ... seeing as Undeploy meant removing the VMs from vCenter inventory.

vCloud Director always has the VMs listed in inventory.  That's why any stop on the entire vApp is also considered an Undeploy.

At this point, I think you have to power off each VM individually via an API to get the equivalent ... once all are off you would run the undeploy command from the API to actually stop the entire vApp.