Instead of accessing the vSphere Lifecycle Manager depot in vCenter Server, clusters in Remote Office and Branch Office (ROBO) deployments can download data from a depot that is local for them. You can configure vSphere Lifecycle Manager to use local depots for any cluster that uses images.
A ROBO cluster is a cluster that has limited or no access to the Internet or limited connectivity to vCenter Server. As a result, clusters in ROBO deployments might have limited access to the vSphere Lifecycle Manager depot during the compliance check, remediation pre-check, and remediation operations.
With vSphere Lifecycle Manager images, you can use a local depot for ROBO clusters and configure vSphere Lifecycle Manager to use the local depot during the compliance check, remediation pre-check, and the remediation tasks. The local depot overrides the vSphere Lifecycle Manager depot. Using local depots with ROBO clusters saves time and network bandwidth.
For each cluster that you manage with a single image, you can add and use multiple local depots instead of the default vSphere Lifecycle Manager depot. You can also delete the depot overrides that you configure. If depot overrides are not active for a cluster, the cluster uses the general vSphere Lifecycle Manager depot in vCenter Server.
Prerequisites
- Set up an online depot to which the cluster can connect.
- Export an offline bundle with components from a vSphere Lifecycle Manager image and import the offline bundle to the target local depot.
- Verify that you have the proper privileges. See vSphere Lifecycle Manager Privileges For Using Images.