6.0.1

Deploying OVF Templates 3
You can export virtual machines, virtual appliances, and vApps in Open Virtual Machine Format (OVF).
You can then deploy the OVF template in the same environment or in a different environment.
This chapter includes the following topics:
n
“OVF File Format and OVF Templates,” on page 63
n
“Deploy an OVF Template in the vSphere Web Client,” on page 64
n
“Browse VMware Virtual Appliance Marketplace,” on page 67
n
“Export an OVF Template,” on page 68
OVF File Format and OVF Templates
OVF is a file format that supports exchange of virtual appliances across products and platforms.
The OVF format offers the following advantages:
n
OVF files are compressed, allowing for faster downloads.
n
The vSphere Web Client validates an OVF file before importing it, and ensures that it is compatible
with the intended destination server. If the appliance is incompatible with the selected host, it cannot be
imported and an error message appears.
n
OVF can encapsulate multi-tiered applications and more than one virtual machine.
Exporting OVF templates allows you to create virtual appliances that can be imported by other users. You
can use the export function to distribute pre-installed software as a virtual appliance, or to distributing
template virtual machines to users. You can make the OVF file available to users who cannot access your
vCenter Server inventory.
Deploying an OVF template allows you to add pre-configured virtual machines or vApps to your
vCenter Server or ESXi inventory. Deploying an OVF template is similar to deploying a virtual machine
from a template. However, you can deploy an OVF template from any local file system accessible from the
vSphere Web Client, or from a remote Web server. The local file systems can include local disks (such as C:),
removable media (such as CDs or USB keychain drives), and shared network drives.
VMware, Inc.
63