7.7.2 vApp Deployment
Standardized vApp templates for common guest operating systems are usually provided by the service provider in a global share catalog. The tenants have an option to create their own vApps or import them through vCloud Connector or OVF import.
The following are vApp deployment design considerations:
• When creating a VM within a vApp, select the correct operating system in the VM properties. An incorrectly specified operating system impacts the presented virtual hardware.
• Install VMware Tools™ to take advantage of guest operating system shutdown action and guest customization scripts (IP assignment, and so on).
• VM configuration limits can be enforced upon deployment via blocking task (see the VMware Knowledge Base article
CPU and Memory Limit enforcement for vCloud Director at https://communities.vmware.com/docs/DOC-21694. (Third-party Web sites are not under the control of VMware, and the content available at those sites might change.)
• vApp state (memory) can be saved in the catalog. vApp with a state (in Suspended state) can be moved between Org VDCs. However, the state does not persist in the case where OVF import x export is leveraged. (This is also valid for Org VDC migrations between vSphere instances.) vCloud Director does not guarantee compute compatibility (for example, migration between an Org VDC running on an Intel platform and an AMD platform).
• Only SCSI disks can be resized. No guest partition extension is performed. Disks cannot be shrunk. Resizing a disk during deployment from the catalog in a fast provisioning-enabled Org VDC results in a full clone with much slower deployment time.