Content Library Support
for OVF and OVA PackagesLast Updated December 16, 2024
You can use the
objects and methods provided by the Content Library API to manage OVF and OVA
packages.
Open Virtualization Format (OVF)
is an industry standard that describes metadata about a virtual machine image
in an XML format. An OVF package includes an XML descriptor file and optionally
disk images, resource files (such as ISO files), manifest files, and
certificate files.
An OVA package is a single file that contains all OVF
package files in an archived form. After you upload an OVA package to a content library,
the OVA file is converted to the standard OVF package.
When you try to upload signed content to a content
library, you might receive preview warnings. Signed content can be either OVF or OVA
packages that contain manifest and certificate files. If you do not respond to the
preview warnings, the upload fails. To complete an upload operation successfully, you
must ignore any preview warnings by using the .
LibraryItemUpdatesessionWarningBehavior
data structureWith the
vSphere
Automation
API, you can use the OVF package in a content library to deploy virtual machines and
vApps on hosts, resource pools, and clusters. You can also use the API to create OVF
packages in content libraries from vApps and virtual machines on hosts, resource pools,
and clusters. When you create library items to store OVF packages,
you must set the item type to .
ovf
. To comply with the specific standards of the OVF packages, the
vSphere
Automation
API provides the Item
service