Working with Offline Depots
An offline depot is a ZIP file that contains the metadata and payloads of software
updates and follows the same structure as the online depot. Use the
vSphere
Automation
APIs to import the content of an offline
depot to the vCenter
Server
database. To add an offline depot to the depots managed by the Depot Manager, you must create an
offline depot specification by using the . When you define the offline depot parameters, .
Offline.CreateSpec
data structureuse the
.
Depending on the location of the offline depot, when you create the offline depot
specification, you must provide either the URI location or the file ID returned by the
Jetty Web server embedded in the POST
https://
request and submit the <vcenter_ip_address_or_fqdn>
/api/esx/settings/depots/offline?vmw-task=trueOffline.CreateSpec
JSON objectvSphere Lifecycle Manager
. You set the type of the source from which the
offline depot is downloaded by using the source_type
property of the
Offline.CreateSpec
data structurePull Depot Content from a URI
To indicate that the offline depot resides on a URI location,
set the depot
location as a value to the
. If you provide an HTTPS location to the
offline depot, make sure you also provide a certificate trusted by the VMware
Certificate Authority (VMCA) or a custom certificate from the VMware Endpoint
Certificate Store (VECS). For detailed information about how to manage certificates,
see the location
property of the
Offline.CreateSpec
data structure. You can use one of the
following URI schemes: http
, https
, or
file
vSphere Authentication
documentation.Push Depot Content to the Depot Manager
To push the content of an offline depot to the Depot Manager, you must first upload
the ZIP file to the Jetty Web server at the
https://
URL. The server returns a file identifier that you can<vcenter_FQDN>
:9087/vum-fileuploadset as a value to the
. file_id
property of the Offline.CreateSpec
data structure