You can create and deploy a vApp directly from an OVF package without creating a vApp template and a corresponding catalog item.
Verify that you have an OVF package to upload and that you have permission to upload OVF packages and deploy vApps.
- On the Virtual Datacenters dashboard screen, click the card of the virtual data center you want to explore, and select vApps from the left panel.
- Click Add vApp from OVF.
- Click the Upload () button to browse to a location accessible from your computer, and select the OVF/OVA template file.
The location might be your local hard drive, a network share, or a CD/DVD drive. The supported file extensions include .ova, .ovf, .vmdk, .mf, .cert, and .strings. If you select to upload an OVF file, which references more files than you are trying to upload, for example, a VMDK file, you must browse and select all files.
- Click Next.
- Verify the details of the OVF/OVA template you are about to deploy and click Next.
- Enter a name and, optionally a description for the vApp, and click Next.
- (Optional) Change the computer name of the vApp so that it contains only alphanumeric characters.
This step is required only if the name of the vApp contains spaces or special characters. By default, the computer name is prepopulated with the name of the virtual machine. However, computer names must contain only alphanumeric characters.
- From the Storage Policy drop-down menu, select a storage policy for each of the virtual machines in the vApp, and click Next.
- Select the networks to which you want each virtual machine to connect. You can configure additional properties for virtual machines after you complete the wizard.
You can optionally switch to the advanced networking workflow, and enter the network settings such as primary NIC, network adapter type, network, IP assignment and IP address manually.
- Click Next.
- Customize the hardware of the virtual machines in the vApp, and click Next.
Option Description Number of virtual CPUs Enter the number of virtual CPUs for each virtual machine in the vApp.
The maximum number of virtual CPUs that you can assign to a virtual machine depends on the number of logical CPUs on the host and the type of guest operating system that is installed on the virtual machine.
Cores per socket Enter the number of cores per socket for each virtual machine in the vApp.
You can configure how the virtual CPUs are assigned in terms of cores and cores per socket. Determine how many CPU cores you want in the virtual machine, then select the number of cores you want in each socket, depending on whether you want a single core CPU, dual-core CPU, tri-core CPU, and so on.
Number of cores View the number of cores for each virtual machine in the vApp.
The number changes when you update the number of virtual CPUs.
Total memory (MB) Enter the memory in MB for each virtual machine in the vApp.
This setting determines how much of the ESXi host memory is allocated to the virtual machine. The virtual hardware memory size determines how much memory is available to applications that run in the virtual machine. A virtual machine cannot benefit from more memory resources than its configured virtual hardware memory size.
- Review the settings on the Ready to Complete page, and click Finish.