When you connect directly to a host with the vSphere Client, you can deploy an OVF template from a local file system accessible to the vSphere Client machine, or from a web URL.
- In the vSphere Client, select
The Deploy OVF Template wizard appears.
- Specify the source location and click Next.
Deploy from File
Browse your file system for an OVF or OVA template.
Deploy from URL
Specify a URL to an OVF template located on the internet. Example:
- View the OVF Template Details page and click Next.
- If license agreements are packaged with the OVF template, the End User License Agreement page appears. Agree to accept the terms of the licenses and click Next.
- Select the deployment configuration from the drop-down menu and click Next.
The option selected typically controls the memory settings, number of CPUs and reservations, and application-level configuration parameters.Note:
This page appears only if the OVF template contains deployment options.
- Select a datastore to store the deployed OVF template, and click Next.
Datastores are a unifying abstraction for storage locations such as Fibre Channel, iSCSI LUNs, or NAS volumes. On this page, you select from datastores already configured on the destination cluster or host. The virtual machine configuration file and virtual disk files are stored on the datastore. Select a datastore large enough to accommodate the virtual machine and all of its virtual disk files.
- Select the disk format to store the virtual machine virtual disks, and click Next.
Thick Provisioned Lazy Zeroed
Creates a virtual disk in a default thick format. Space required for the virtual disk is allocated when the virtual disk is created data remaining on the physical device is not erased during creation, but is zeroed out on demand at a later time on first write from the virtual machine.
Thick Provision Eager Zeroed
A type of thick virtual disk that supports clustering features such as Fault tolerance. Space required for the virtual disk is allocated at creation time. In contrast to the flat format the data remaining on the physical device is zeroed out when the virtual disk is created. it might take much longer to create disks in this format than to create other types o disks.
Use this format to save storage space. For the thin disk, you provision as much datastore space as the disk would require based on the value that you enter for the disk size. However, the thin disk starts small and at first, uses only as much datastore space as the disk needs for its initial operations. The disk space grows as the virtual machine needs more storage.
- If the appliance that you are deploying has one ore more vService dependencies, select a binding service provider.
- For each network specified in the OVF template, select a network by right-clicking the Destination Network column in your infrastructure to set up the network mapping and click Next.
- On the IP Allocation page, configure how IP addresses are allocated for the virtual appliance and click Next.
You will be prompted to enter the IP addresses in the Appliance Properties page.
IP addresses are allocated from a specified range when the appliance is powered on. The IP addresses are released when the appliance is powered off.
A DHCP server is used to allocate the IP addresses.
This page does not appear if the deployed OVF template does not contain information about the IP scheme it supports.
- Set the user-configurable properties and click Next.
The set of properties that you are prompted to enter depend on the selected IP allocation scheme. For example, you are prompted for IP related information for the deployed virtual machines only in the case of a fixed IP allocation scheme.
- Review your settings and click Finish.
The progress of the import task appears in the vSphere Client Status panel.