Configure capacity forecasting in VCF Operations to trigger procurement automation.
Step 1
Enable capacity projection for all workload clusters.
Step 2
Set buffer thresholds (e.g., 20% headroom, 90 days runway).
Step 3
Create alert on threshold breach that calls a webhook to procurement.
Step 4
Simulate consumption growth and validate webhook fires.
Step 5
Integrate into VCF Automation to auto-provision additional hosts from a pool.
Validation Gate
Check: Verify lab completion
Expected: Lab exercise completed successfully
Common Errors
Capacity forecast not accounting for planned projects
Fix: VCF Operations forecasts based on historical trends only. If a new project will onboard 200 VMs in 60 days, the forecast won't show this until the VMs are actually deployed. Manually add planned project resource requirements to the forecast model as what-if scenarios.
Procurement trigger set too close to capacity exhaustion
Fix: Hardware procurement: 4-12 weeks. If capacity trigger fires at 90% utilization and growth rate is 5%/month, you have approximately 2 months before 100%. If procurement takes 3 months, you are already too late. Set trigger at: 100% - (growth_rate × procurement_months) with buffer.
Not separating forecast by resource type (CPU vs memory vs storage)
Fix: A cluster may be capacity-constrained on memory while CPU has 50% headroom. Forecasting aggregate 'capacity' misses this imbalance. Run separate forecasts per resource dimension: CPU, memory, and storage. The most constrained resource determines the procurement trigger.
Final Validation
Lab completed successfully
✓ All steps completed → No errors observed
Cleanup / Restore
• Revert to snapshot if needed
Design Reflection (VCDX)
Capacity forecasting with procurement triggers demonstrates infrastructure planning maturity. VCDX designs should include growth projections tied to procurement timelines.
⚠ Known Pitfalls (from Community KB)
Forecasting only aggregate capacity instead of per-resource-dimension — memory exhaustion occurs while CPU shows 50% free.
Not manually adding planned projects to forecasts — 200 new VMs from a project won't appear in historical trend data.
Was this page useful?Thanks — noted.
Type to search. ↑↓ to move,
Enter to open, Esc to close.