Holodeck Instance Lifecycle Management

Before destroying, document the instance configuration. Run: Get-HoloDeckInstance | ConvertTo-Json | Out-File C:\Holodeck\holodeck-runtime\instance-backup-before-destroy.json

Power off all Holodeck VMs to prepare for destruction. Run: Get-VM -Name 'Holo-*' | Stop-VM -Kill -Confirm:$false

Record pre-destruction datastore state: $datastorePre = Get-Datastore | Where-Object {$_.Name -like 'holodeck'}; $datastorePre | Format-Table -Property Name, FreeSpaceGB, CapacityGB

Execute instance removal. Get your instance ID first: $instanceId = (Get-HoloDeckInstance).InstanceId; Write-Host 'Destroying instance: '$instanceId; Remove-HoloDeckInstance -InstanceID $instanceId -Verbose

Verify cleanup: (a) No VMs named Holo- should exist: Get-VM -Name 'Holo-' -ErrorAction SilentlyContinue | Measure-Object

Verify (b) Port groups cleaned: Get-VirtualPortGroup | Where-Object {$_.Name -match '10\.0\.'} | Measure-Object

Verify (c) Datastore space reclaimed: $datastorePost = Get-Datastore | Where-Object {$_.Name -like 'holodeck'}; $spaceReclaimed = $datastorePost.FreeSpaceGB - $datastorePre.FreeSpaceGB; Write-Host 'Space reclaimed: '$spaceReclaimed' GB'

Now redeploy from scratch using the same config.json. First, prepare: $stopwatch = [System.Diagnostics.Stopwatch]::StartNew(); New-HoloDeckInstance -ConfigFile .\templates\config.json -Verbose

Start the full deployment: Start-HoloDeckInstance -InstanceID ((Get-HoloDeckInstance).InstanceId) -Verbose

Compare redeploy time vs snapshot revert time. Redeploy typically takes 90-150 minutes. Snapshot revert (if you had reverted instead of destroying) would take ~5-10 minutes. Document this in your lab notebook.

Create a config directory structure for version control: mkdir -p C:\Holodeck\holodeck-runtime\configs\{base,overlays,deployed}

Copy your current config.json as the base template: Copy-Item .\templates\config.json .\configs\base\config-base-9.0.2.json

Create overlay configs for different scenarios. First, create an overlay for management-only deployment: @{ managementOnly = $true; vcfAutomationRequired = $false } | ConvertTo-Json | Out-File .\configs\overlays\overlay-mgmt-only.json

Create an overlay for different resource tiers (e.g., 3-host compact vs 4-host standard). Read the base config: $baseConfig = Get-Content .\configs\base\config-base-9.0.2.json | ConvertFrom-Json

Modify the config for a 3-host scenario (compact): $baseConfig.holodeck_sddc.'Site-A'.management.esxi.NumofNode = 3; $baseConfig.holodeck_sddc.'Site-A'.management.esxi.memory = 128; $baseConfig | ConvertTo-Json -Depth 20 | Out-File .\configs\deployed\config-vcf902-mgmt-3host.json

Verify the 3-host config: Get-Content .\configs\deployed\config-vcf902-mgmt-3host.json | ConvertFrom-Json | Select-Object -ExpandProperty holodeck_sddc | Select-Object -ExpandProperty 'Site-A' | Select-Object -ExpandProperty management | Select-Object -ExpandProperty esxi | Format-Table -Property NumofNode, memory

Create naming convention documentation: @'EOM
Holodeck Config Naming Convention:
---
(1) base configs: config-base-<vcf-version>.json
Example: config-base-9.0.2.json

(2) deployed configs: config-vcf<version>-<scenario>.json
Example: config-vcf902-mgmt-only.json
Example: config-vcf902-mgmt-3host.json
Example: config-vcf921-full-wld.json

(3) overlays: overlay-<feature>.json (for composition patterns)
Example: overlay-mgmt-only.json
Example: overlay-vsan-compact.json

(4) dated archives: config-<scenario>-<date>.json.bak
Example: config-vcf902-mgmt-only-2026-04-17.json.bak
EOM
' | Out-File .\configs\CONFIG_NAMING.md

Create a version history file: Add-Content C:\Holodeck\holodeck-runtime\configs\VERSION_HISTORY.txt -Value @"
2026-04-17: config-vcf902-mgmt-only.json deployed successfully (90min)
2026-04-17: config-vcf902-mgmt-3host.json validated (85min)
2026-04-16: config-base-9.0.2.json created as baseline
"@

Demonstrate config validation before deployment. Create a validation function in PowerShell: function Validate-HoloDeckConfig { param([string]$ConfigFile); $config = Get-Content $ConfigFile | ConvertFrom-Json; if (-not $config.vcf.version) { Write-Host 'ERROR: vcf.version not set' } else { Write-Host 'VCF version: '$config.vcf.version }; if (-not $config.network.management_cidr) { Write-Host 'ERROR: management_cidr not set' } else { Write-Host 'Management CIDR: '$config.network.management_cidr } }; Validate-HoloDeckConfig -ConfigFile .\configs\deployed\config-vcf902-mgmt-only.json

Create a config snapshot feature: function Export-ConfigSnapshot { param([string]$ConfigId); $timestamp = Get-Date -Format 'yyyyMMdd-HHmmss'; Copy-Item .\configs\deployed\$ConfigId .\configs\base\archive\$ConfigId'.snapshot-'$timestamp'.json }; Export-ConfigSnapshot -ConfigId 'config-vcf902-mgmt-only.json'

Verify your VCF 5.2.x content manifest is available. List content manifests: Get-ChildItem .\content\manifests\ | Where-Object {$_.Name -like '5.2*'} | Format-Table Name

Create a VCF 5.2.x config by copying the base config and modifying version: $config521 = Get-Content .\configs\base\config-base-9.0.2.json | ConvertFrom-Json; $config521.vcfVersion = '5.2.1'; $config521.contentManifest = '.\content\manifests\vcf-5.2.1-manifest.json'; $config521 | ConvertTo-Json -Depth 20 | Out-File .\configs\deployed\config-vcf521-mgmt-only.json

Update the Site-A naming in the config to avoid conflicts with the 9.0.2 instance. Modify the site identifier: $config521.holodeck_sddc | Add-Member -MemberType NoteProperty -Name 'Site-B' -Value $config521.holodeck_sddc.'Site-A' -Force; $config521.holodeck_sddc.PSObject.Properties.Remove('Site-A'); $config521 | ConvertTo-Json -Depth 20 | Out-File .\configs\deployed\config-vcf521-mgmt-only.json

Prepare the VCF 5.2.1 instance: New-HoloDeckInstance -ConfigFile .\configs\deployed\config-vcf521-mgmt-only.json -Verbose

Start the VCF 5.2.1 deployment in parallel (or sequentially if resources are limited): Start-HoloDeckInstance -InstanceID ((Get-HoloDeckInstance | Where-Object {$_.VcfVersion -eq '5.2.1'}).InstanceId) -Verbose

Once 5.2.1 deployment completes, validate both instances. Get the VCF 5.2.1 SDDC Manager IP (different Site-B network) and compare: Write-Host 'VCF 9.0.2 instances:'; Get-HoloDeckInstance | Where-Object {$_.VcfVersion -eq '9.0.2'} | Format-Table -Property InstanceId, State, VcfVersion; Write-Host 'VCF 5.2.1 instances:'; Get-HoloDeckInstance | Where-Object {$_.VcfVersion -eq '5.2.1'} | Format-Table -Property InstanceId, State, VcfVersion

Access both SDDC Managers and document differences. For 5.2.x, navigate to https://10.10.0.4 (Site-B network). For 9.0.2, navigate to https://10.1.1.4 (Site-A network). Compare: (a) SDDC Manager UI layout and menu structure, (b) Component versions listed in System > About, (c) Workload Domain configuration workflow

Compare component versions. Access vCenter on both instances and check: Administration > System Configuration > Servers. Document the vCenter version for each instance (typically vCenter 7.x for 5.2.x, vCenter 8.x for 9.0.x).

Document 5+ specific architectural or operational differences. Create a comparison document: @'EOM
VCF 5.2.1 vs VCF 9.0.2 Differences:
---

1. SDDC Manager UI:

5.2.x: Simplified dashboard, fewer Day 2 operations visible
9.0.x: Enhanced UI with VCF Automation integration, expanded Day 2 menu

2. vCenter Version:

5.2.x: vCenter 7.0.x
9.0.x: vCenter 8.0.x

3. NSX Version:

5.2.x: NSX 4.x
9.0.x: NSX 9.0.x

4. Cloud Builder Role:

5.2.x: Cloud Builder required for bring-up, then can be removed
9.0.x: Cloud Builder retained for SDDC lifecycle operations

5. Licensing Model:

5.2.x: Older licensing mechanism, limited evaluation trial
9.0.x: New licensing portal integration, extended evaluation trial
EOM
' | Out-File C:\Holodeck\holodeck-runtime\COMPARISON_5.2-vs-9.0.md

Create a summary discussing VCDX-relevant insights: 'From a design perspective, VCF 9.0.x introduces tighter integration between SDDC Manager and lifecycle operations. This affects how you plan upgrade windows, capacity planning, and automation. A VCDX candidate should understand these version-specific constraints when designing infrastructure.'

Create a PowerShell module for common Holodeck operations. Create file: C:\Holodeck\holodeck-runtime\HoloDeckOps.psm1

Add a function to deploy an instance with logging: @'
function New-HoloDeckDeployment {
param(
[string]$ConfigFile,
[string]$LogPath = 'C:\Holodeck\holodeck-runtime\logs'
)
$timestamp = Get-Date -Format 'yyyyMMdd-HHmmss'
$logFile = Join-Path $LogPath "deployment-$timestamp.log"

Write-Host "[$(Get-Date)] Starting deployment with config: $ConfigFile" | Tee-Object -FilePath $logFile -Append

try {
New-HoloDeckInstance -ConfigFile $ConfigFile -Verbose 2>&1 | Tee-Object -FilePath $logFile -Append
$instanceId = (Get-HoloDeckInstance | Where-Object {$_.State -eq 'Prepared'}).InstanceId
Write-Host "[$(Get-Date)] Prepared instance: $instanceId" | Tee-Object -FilePath $logFile -Append

Start-HoloDeckInstance -InstanceID $instanceId -Verbose 2>&1 | Tee-Object -FilePath $logFile -Append
Write-Host "[$(Get-Date)] Deployment completed successfully" | Tee-Object -FilePath $logFile -Append
return $instanceId
}
catch {
Write-Host "[$(Get-Date)] ERROR: $_" | Tee-Object -FilePath $logFile -Append
throw
}
}
export-modulemember -function New-HoloDeckDeployment
' | Out-File C:\Holodeck\holodeck-runtime\HoloDeckOps.psm1 -Encoding UTF8

Add a snapshot management function: @'
function New-HoloDeckCheckpoint {
param(
[string]$CheckpointName,
[string]$Description
)
Write-Host "Creating checkpoint: $CheckpointName"
Get-VM -Name 'Holo-*' | New-Snapshot -Name $CheckpointName -Description $Description -Memory:$false -Quiesce:$false | Out-Null
Write-Host "Checkpoint created: $CheckpointName"
}

function Revert-HoloDeckCheckpoint {
param(
[string]$CheckpointName
)
Write-Host "Reverting to checkpoint: $CheckpointName"
Get-VM -Name 'Holo-*' | Get-Snapshot -Name $CheckpointName | Foreach-Object { Set-VM -VM $_.VM -Snapshot $_ -Confirm:$false } 2>&1
Write-Host "Checkpoint reverted: $CheckpointName"
}
export-modulemember -function New-HoloDeckCheckpoint, Revert-HoloDeckCheckpoint
' | Add-Content C:\Holodeck\holodeck-runtime\HoloDeckOps.psm1 -Encoding UTF8

Create a lab reset script: @'

HoloDeck Lab Reset Script

Usage: .\Reset-Lab.ps1 -TargetSnapshot 'holodeck-02-complete'

param(
[string]$TargetSnapshot = 'holodeck-02-complete',
[switch]$Confirm = $true
)

Import-Module C:\Holodeck\holodeck-runtime\HoloDeckOps.psm1

Write-Host "Lab Reset: Reverting all VMs to snapshot: $TargetSnapshot"

if ($Confirm) {
$response = Read-Host "Confirm reset? (yes/no)"
if ($response -ne 'yes') { Write-Host 'Cancelled'; exit }
}

Get-VM -Name 'Holo-*' | Where-Object { Get-Snapshot -VM $_ -Name $TargetSnapshot -ErrorAction SilentlyContinue } | Foreach-Object {
Write-Host "[$(Get-Date)] Reverting: $($_.Name)"
Get-Snapshot -VM $_ -Name $TargetSnapshot | Set-VM -Snapshot -Confirm:$false | Out-Null
}

Write-Host "[$(Get-Date)] Lab reset complete. Starting VMs..."
Get-VM -Name 'Holo-*' | Start-VM -Confirm:$false | Out-Null
Write-Host "Lab ready"
' | Out-File C:\Holodeck\holodeck-runtime\Reset-Lab.ps1 -Encoding UTF8

Create a scheduled snapshot script. This script runs weekly to create a clean checkpoint: @'

Scheduled Weekly Snapshot

This runs every Friday at 18:00 via Windows Task Scheduler

$timestamp = Get-Date -Format 'yyyyMMdd'
$checkpointName = "auto-weekly-$timestamp"

Write-Host "[$(Get-Date)] Creating weekly checkpoint: $checkpointName"
Get-VM -Name 'Holo-*' | New-Snapshot -Name $checkpointName -Description "Auto-generated weekly snapshot" -Memory:$false -Quiesce:$false | Out-Null

Write-Host "[$(Get-Date)] Snapshot created"

Clean up snapshots older than 4 weeks

$cutoffDate = (Get-Date).AddDays(-28)
Get-VM -Name 'Holo-*' | Get-Snapshot | Where-Object { $_.Created -lt $cutoffDate } | Remove-Snapshot -Confirm:$false

Write-Host "[$(Get-Date)] Old snapshots cleaned up"
' | Out-File C:\Holodeck\holodeck-runtime\ScheduledSnapshot.ps1 -Encoding UTF8

Test the reset script (dry-run): Read the script to verify syntax, then test on a single VM: Get-VM -Name 'Holo-Console' | Get-Snapshot | Measure-Object

Create a CI/CD integration example. This script validates a config before deployment: @'
function Test-HoloDeckConfig {
param([string]$ConfigFile)

Write-Host "Validating config: $ConfigFile"
$config = Get-Content $ConfigFile | ConvertFrom-Json

Validation checks

$checks = @(
('vcfVersion defined', -not [string]::IsNullOrEmpty($config.vcfVersion)),
('contentManifest exists', (Test-Path $config.contentManifest)),
('ESXi count > 2', $config.holodeck_sddc."Site-A".management.esxi.NumofNode -ge 2)
)

$passed = 0
foreach ($check in $checks) {
$status = if ($check[1]) { 'PASS' } else { 'FAIL' }
Write-Host " [$status] $($check[0])"
if ($check[1]) { $passed++ }
}

return ($passed -eq $checks.Count)
}
export-modulemember -function Test-HoloDeckConfig
' | Out-File C:\Holodeck\holodeck-runtime\HoloDeckValidation.psm1 -Encoding UTF8

Create a deployment status dashboard script. This shows health of all instances: @'
Write-Host "Holodeck Deployment Status"
Write-Host "============================="
Get-HoloDeckInstance | Format-Table -Property @(
'InstanceId',
'State',
'VcfVersion',
@{Label='SDDC Manager';Expression={Get-VM -Name 'SDDC-Manager*' -ErrorAction SilentlyContinue | Measure-Object | Select-Object -ExpandProperty Count}}
) -AutoSize

Write-Host ""
Write-Host "Datastore Usage"
Write-Host "==============="
Get-Datastore | Where-Object {$_.Name -like 'holodeck'} | Format-Table -Property Name, @{Label='Free GB';Expression={[Math]::Round($_.FreeSpaceGB, 0)}}, @{Label='Total GB';Expression={[Math]::Round($_.CapacityGB, 0)}} -AutoSize

Write-Host ""
Write-Host "Snapshots"
Write-Host "========="
Get-VM -Name 'Holo-*' | Get-Snapshot | Group-Object -Property VM | Format-Table -Property Name, @{Label='Snapshot Count';Expression={$_.Count}} -AutoSize
' | Out-File C:\Holodeck\holodeck-runtime\Show-LabStatus.ps1 -Encoding UTF8

Test the modular functions: Import-Module C:\Holodeck\holodeck-runtime\HoloDeckOps.psm1; New-HoloDeckCheckpoint -CheckpointName 'test-automation' -Description 'Testing automation script'

Document the automation framework in a README: @'

Holodeck Automation Framework

Available Functions

Deployment

• New-HoloDeckDeployment -ConfigFile <path>: Deploy instance with logging

Checkpoints

• New-HoloDeckCheckpoint -CheckpointName <name>: Create snapshot
• Revert-HoloDeckCheckpoint -CheckpointName <name>: Revert to snapshot

Utilities

• .\Reset-Lab.ps1 -TargetSnapshot <name>: Full lab reset
• .\Show-LabStatus.ps1: Display current health
• Test-HoloDeckConfig -ConfigFile <path>: Validate config before deployment

Scheduling

Schedule weekly snapshots via Windows Task Scheduler:
Action: PowerShell -ExecutionPolicy Bypass -File C:\Holodeck\holodeck-runtime\ScheduledSnapshot.ps1
Trigger: Weekly on Friday at 18:00

Idempotency

All scripts are designed to be re-runnable. If a step fails, you can run again without side effects.
' | Out-File C:\Holodeck\holodeck-runtime\AUTOMATION_README.md -Encoding UTF8