Lab: Create & Apply Cluster Image
Objectives
- Compose a vLCM cluster image from the depot: base image, vendor add-on, components (Obj 4.2)
- Run compliance check and remediation pre-check
- Remediate the cluster and confirm compliance
Prerequisites
Holodeck VVF 9.0 instance deployed and healthy
Lab Environment
Holodeck vSphere Foundation 9.0 instance (New-HoloDeckInstance -VVF; -vSANMode OSA by default, ESA where the physical layer supports it): vCenter managing one vSAN cluster of nested ESX hosts, plus VCF Operations. VVF has no SDDC Manager and no NSX. Firmware through a hardware support manager is physical-lab only.
Credentials
| System | Username | Password |
|---|---|---|
| vCenter | administrator@vsphere.local | Holodeck documented default (Post Deployment table) |
| Nested ESX hosts | root | Holodeck documented default (Post Deployment table) |
Tasks
Task 1 Create & Apply Cluster Image
Lifecycle Manager → Settings: sync the online depot (entitled download token) or import the ESX 9.0 offline bundle into the depot (VCF 9.0.1 docs p.246). Binaries come from the Broadcom support portal or depot, not vmware.com.
(Physical servers only) Register the vendor hardware support manager as a vCenter extension — for Dell that is OpenManage Integration for VMware vCenter (OMIVV), for HPE iLO Amplifier or OneView, for Lenovo XClarity Integrator (p.1811). In Holodeck skip firmware.
Cluster → Updates → Image → Edit: choose the ESX base image version, the vendor add-on (if any) and extra components → Save. vLCM composes the image from the depot; it is not built by importing an ISO.
Record the image composition (base image build, add-on version) in the lab log; vLCM images have no separate 'tag'.
Check Compliance for the cluster against the new image.
Run the remediation pre-check: it reports issues (for example a host that cannot enter maintenance mode, or a missing driver) before anything changes.
Remediate: vLCM puts hosts into maintenance mode one at a time, applies the image and reboots them (there is no 'preview mode').
Verify: the cluster shows Compliant; on a host, vmware -v shows the new build.
Validation Gate
Check: After creating and applying a cluster image: verify all hosts show 'Compliant' status, no hosts are in maintenance mode, and vSAN health is green
Expected: All hosts compliant with the cluster image. No hosts pending reboot. vSAN health shows all checks green after rolling update completes.
Common Errors
Final Validation
Gate: every check below passes with the evidence recorded in the lab log.
✓ Image → Cluster image saved with the chosen base image and add-on
✓ Compliance → All hosts Compliant after remediation
✓ Cluster state → No host left in maintenance mode; vSAN health green
Cleanup / Restore
• Leave the image in place; record its composition
Design Reflection (VCDX)
Lifecycle management is a Day-2 operational requirement in VCDX designs. Panelists test whether you planned for patching cadence, image composition, and the operational impact of rolling updates on cluster availability.
Requirements
- Create cluster images with base ESXi + vendor add-on + components
- Validate images before production deployment
- Schedule remediation during maintenance windows
Constraints
- vSphere 9.0 requires image-based management only (no baselines)
- Rolling updates require DRS capacity to evacuate each host
- Firmware updates may require additional reboot cycles
Assumptions
- Vendor add-on packages are available and compatible
- DRS has sufficient headroom to evacuate VMs during rolling update
Risks
- Boot failure from incompatible firmware in cluster image
- Stalled remediation from insufficient DRS evacuation capacity