Managing Depot Overrides
In case, you have a smaller Remote Office/ Branch Office (ROBO) cluster environment,
or Edge computing environment, your clusters have no, or limited access to the Internet and
limited connection to a
vCenter
Server
instance.
In such an environment, you can use Depot Manager to fetch the metadata and payloads of a
desired software state from a local to the cluster depot. To remediate a ROBO cluster, you must have access to a local software depot that hosts
the components of the desired state. You can use Depot Manager to either export the
whole
vSphere Lifecycle Manager
depot to an offline bundle, or export only the content of the desired state required for
remediating the ROBO cluster. To export the desired state image from the
vSphere Lifecycle Manager
depot, use the
. To move the
content of the offline bundle to the ROBO location, you must physically copy the ZIP
file, unarchive, and mount its content to an HTTP server inside the ROBO environment. POST
https://
request and submit the cluster ID as path parameter and an
<vcenter_ip_address_or_fqdn>
/api/esx/settings/clusters/<cluster_ID>
/software?action=exportSoftware.ExportSpec
JSON object. You receive the URI of the
offline bundle that is hosted on the vSphere Lifecycle Manager
Jetty Web serverTo redirect a ROBO cluster to download software updates from a local repository and not
from the . During the ROBO cluster remediation, Depot Manager instructs the
hosts in the ROBO cluster to download the software updates from the configured local
depots within the ROBO cluster.
vSphere Lifecycle Manager
depot on the vCenter
Server
instance, the vSphere
Automation
REST
API offer the cluster
DepotOverrides
service. To add a depot override location to a
ROBO cluster, use the
. Specify the URI location of the local depot with the POST
https://
request<vcenter_ip_address_or_fqdn>
/api/esx/settings/clusters/<cluster_ID>
/depot-overrides?action=addlocation
property of
the DepotOverrides.Depot
data structure which you submit to the
request body