vSphere Foundation Overview
Objectives
- Describe vSphere Foundation (VVF) components and how they differ from full VCF
- Explain the three VVF use cases: HCI enhancement, modern workloads, data protection
- List VVF add-ons (vSAN capacity, Live Recovery, Avi Load Balancer) and their capabilities
- Describe the VVF to VCF upgrade path via VCF Installer converge process
- Compare VVF and VCF licensing under the Broadcom per-core model
- Position VVF vs VCF for different customer scenarios in VCDX design context
Prerequisites
Active Holodeck VCF 9.0 lab or access to VCF/VVF documentation
Required skills:
- Basic VMware terminology
- Understanding of hyperconverged infrastructure concepts
Tasks
Task 1 VVF Architecture & Component Mapping
Build a clear mental model of what VVF includes and excludes compared to full VCF, understanding VVF as a subset not a separate product.
Document the four components included in VVF: (1) vSphere 9.0 (compute hypervisor, same as VCF), (2) vSAN 9.0 (storage, both ESA and OSA supported), (3) VMware Kubernetes Service (VKS) for enterprise Kubernetes (CNCF-compliant), (4) VCF Operations (administrative console for health monitoring and license management). Verify: VVF does NOT include NSX, SDDC Manager, or VCF Automation. VVF uses VCF Operations as its primary management interface instead of SDDC Manager.
Create a side-by-side comparison table. VVF includes: vSphere, vSAN, VKS, VCF Operations. VCF adds: NSX (network virtualization and micro-segmentation), SDDC Manager (lifecycle management and orchestration), VCF Automation (self-service portal and infrastructure-as-code). Key implication: VVF has no overlay networking (no Geneve tunnels, no DFW micro-segmentation), no automated lifecycle management (manual vCenter-based updates), and no self-service provisioning.
Understand that VVF and VCF share the same deployment mechanism: the VCF Installer appliance. The same OVA deploys both products. During installation, the wizard branches based on whether you select VVF or VCF deployment. This shared foundation means VVF environments are architecturally compatible with VCF, enabling the converge upgrade path.
Compare management approaches: VVF uses VCF Operations Console as the primary admin interface (simplified launchpad, vCenter-based inventory, no fleet management). VCF uses SDDC Manager as the primary admin interface (full lifecycle management, multi-domain orchestration, API-driven operations). VVF administrators use vSphere Client for day-to-day operations; VCF administrators use SDDC Manager for most operations. Document: what operational tasks require SDDC Manager that cannot be done in VVF?
Validation Gate
Check: Complete VVF component inventory and comparison table
Expected: All VVF components listed, exclusions documented, management interface differences understood.
Common Errors
Task 2 VVF Use Cases & Licensing Model
Map the three official VVF use cases to customer scenarios and understand the per-core licensing model shared with VCF.
VVF as modern HCI platform: replaces traditional SAN/NAS with vSAN (ESA or OSA), provides integrated storage management, vSAN Insights for capacity planning, and storage health monitoring through VCF Operations. Target customers: organizations modernizing from legacy storage (NetApp, Pure, Dell EMC) to HCI. Key selling point: single platform for compute and storage without the complexity of full SDDC stack. Typical deployment: 4-16 hosts, single site.
VVF includes VMware Kubernetes Service (VKS) for running containerized workloads alongside traditional VMs. VKS provides: CNCF-compliant Kubernetes clusters, integrated container networking (without NSX, uses Antrea CNI), persistent storage via vSAN CSI driver, lifecycle management of K8s clusters through vSphere Client. Target customers: organizations starting cloud-native journey without needing full network virtualization.
VVF supports data protection scenarios: VM-level backup and recovery, vSAN native snapshots, and the optional Live Recovery add-on for ransomware recovery and disaster recovery from a single console. Live Recovery is a paid add-on that provides: orchestrated recovery workflows, ransomware detection and clean recovery, and multi-site DR capabilities without requiring SRM.
VCF 9.0 and VVF share the same Broadcom per-core licensing model. Key details: license is per physical CPU core (not per socket), minimum 16 cores per physical CPU socket regardless of actual core count, all hosts in the environment must be licensed. VVF licensing is typically lower cost than VCF because fewer components are included. Compare: VVF per-core cost vs VCF per-core cost (VCF includes NSX, SDDC Manager, Automation in the license). Document: for a customer with 4 hosts, 2 sockets each, 32 cores per socket = 256 total cores. Calculate licensing for both VVF and VCF.
Document when VVF is insufficient and VCF is required: (a) micro-segmentation needed (NSX DFW), (b) multi-tenant environment (VCF Automation projects), (c) multi-workload domain architecture (SDDC Manager), (d) automated lifecycle management at scale (SDDC Manager vLCM integration), (e) overlay networking for multi-site or cloud connectivity. Create a decision matrix: customer requirement vs VVF/VCF recommendation.
Validation Gate
Check: Document all three use cases with target customer profiles and licensing calculation
Expected: Three use cases mapped to customer scenarios. Licensing calculation completed for sample environment. VVF vs VCF decision matrix created.
Common Errors
Task 3 VVF Add-Ons & Extensibility
Understand the VVF add-on ecosystem that extends capabilities without requiring full VCF upgrade.
VVF base license includes vSAN, but additional vSAN capacity can be added through the vSAN add-on for environments needing more storage. This allows scaling storage independently of compute. Document: vSAN ESA storage pool expansion (add NVMe devices to existing hosts), vSAN host addition (add new hosts to cluster), and the capacity planning process using VCF Operations vSAN Insights.
Live Recovery provides a single console for ransomware recovery and disaster recovery. Features: (a) ransomware detection using behavioral analysis, (b) clean recovery to a known-good state, (c) orchestrated DR workflows for site failover, (d) recovery testing without production impact. Live Recovery replaces the need for separate backup and DR products. Compare with VCF approach: VCF uses SRM (Site Recovery Manager) for DR orchestration and can integrate with third-party backup solutions.
Avi Load Balancer (formerly NSX ALB) is available as a VVF add-on for application traffic management. In VVF context: Avi Controller cluster deploys on vSphere VMs, Service Engines (SEs) deploy on vSAN datastore, Avi connects to vCenter for SE lifecycle management (no NSX integration since NSX is not in VVF). Capabilities: L4/L7 load balancing, SSL offload, WAF, real-time analytics. Key difference from VCF: in VCF, Avi integrates with NSX for automated SE placement on overlay networks. In VVF, Avi uses VLAN-backed port groups.
Build a decision framework: when to add individual add-ons vs upgrading to full VCF. Factors: (a) cost comparison (VVF + all add-ons may approach VCF cost), (b) operational complexity (each add-on is separate management plane vs VCF unified SDDC Manager), (c) future roadmap (if customer will eventually need NSX, start with VCF), (d) scale (VVF add-ons work well for single-site, single-cluster; VCF scales to multi-domain multi-site). Calculate the breakpoint: at what combination of add-ons does VCF become more cost-effective?
Validation Gate
Check: Document all add-ons with use cases and create VVF+add-ons vs VCF decision framework
Expected: Three add-ons documented with capabilities. Decision framework with cost breakpoint analysis created.
Common Errors
Task 4 VVF to VCF Migration Path & VCDX Positioning
Master the VCF Installer converge process for upgrading VVF to VCF, and understand how to position VVF in VCDX design proposals.
The converge process upgrades a VVF environment to full VCF by adding the missing components: SDDC Manager, NSX Manager cluster, and VCF Automation. Process overview: (1) deploy VCF Installer appliance (same OVA used for initial VVF deployment), (2) run the converge wizard which detects existing VVF components, (3) wizard deploys and configures: SDDC Manager (connects to existing vCenter), NSX Manager cluster (3 nodes for HA), VCF Automation (optional), (4) existing VMs, vSAN, and VKS clusters are preserved — no data migration required. Document: the converge is additive (adds components), not destructive (does not rebuild existing infrastructure).
Document converge requirements: (a) VVF must be running vSphere 9.0 (same version as target VCF), (b) sufficient compute resources for new components (SDDC Manager: 4 vCPU/16 GB, NSX Manager x3: 6 vCPU/24 GB each, VCF Automation: 8 vCPU/32 GB), (c) network preparation (management VLAN, TEP VLAN for NSX overlay, uplink VLAN for NSX edges), (d) DNS/NTP configuration for new components, (e) IP address planning for SDDC Manager, NSX Managers, TEP pool. Total additional resource requirement: approximately 30 vCPU, 120 GB RAM for management components.
After converge: (a) verify SDDC Manager UI shows all hosts and VMs from existing vCenter, (b) verify NSX Manager cluster is stable (3 nodes, all STABLE), (c) verify NSX transport nodes are configured on all ESXi hosts, (d) test DFW with a basic allow/deny rule, (e) verify VCF Operations now shows NSX and SDDC Manager in inventory tree. Document: what changes for day-to-day operations (SDDC Manager becomes primary interface, NSX overlay networking available, VCF Automation self-service available).
Prepare design recommendations for VVF vs VCF. Start-with-VVF scenarios: (a) small environment under 16 hosts that does not need micro-segmentation, (b) organization with limited VMware expertise (simpler to operate), (c) phased adoption strategy (start simple, grow to VCF), (d) budget-constrained projects where per-core cost difference is significant. Start-with-VCF scenarios: (a) multi-tenant environments requiring isolation (NSX DFW), (b) multi-site DR requiring SRM integration, (c) environments requiring automated lifecycle management (SDDC Manager), (d) regulatory compliance requiring micro-segmentation (PCI-DSS, HIPAA). Document as VCDX design decision D-VVF-001 with RCAR format.
Design a phased adoption approach: Phase 1 (months 0-6) deploy VVF with vSAN ESA for HCI modernization. Phase 2 (months 6-12) add Live Recovery for DR capability. Phase 3 (months 12-18) converge to VCF when NSX micro-segmentation is required for compliance. Phase 4 (months 18-24) add workload domains for multi-tenant isolation. Document the architectural evolution at each phase, showing how VVF investment is preserved through the VCF converge path.
Validation Gate
Check: Document converge process, design positioning, and phased adoption architecture
Expected: Converge process documented with prerequisites. VVF vs VCF decision matrix with RCAR format. Phased adoption architecture showing 4-phase evolution.
Common Errors
Final Validation
Complete VVF overview with component mapping, use cases, add-ons, and VCF migration path
✓ VVF components documented → All 4 VVF components listed with VCF exclusions
✓ Use cases mapped → 3 use cases with target customer profiles
✓ Add-ons understood → 3 add-ons documented with VCF comparison
✓ Converge process known → VVF to VCF upgrade path documented with prerequisites
✓ VCDX positioning prepared → VVF vs VCF decision matrix with phased adoption architecture
Cleanup / Restore
• No lab environment changes to revert
• Save design decision documentation for future reference
• Update personal study notes with VVF vs VCF comparison
Design Reflection (VCDX)
VVF positioning demonstrates product portfolio understanding critical for VCDX. The design decision between VVF and VCF maps directly to customer requirements analysis (Objective 1.1). The converge path shows architectural planning for growth, a key VCDX competency.
Requirements
- R-001: Customer needs HCI modernization within 6-month timeline
- R-002: Budget constraint limits initial investment to essential components
- R-003: Future micro-segmentation requirement anticipated within 18 months
Constraints
- VVF does not include NSX — no micro-segmentation capability
- VVF management is vCenter-based — no SDDC Manager lifecycle automation
- Per-core licensing minimum 16 cores per socket applies to both VVF and VCF
Assumptions
- Customer will grow to need NSX within 18 months based on compliance roadmap
- Converge process will be non-disruptive to running workloads
- VVF per-core licensing cost is lower than VCF per-core cost
Risks
- Starting with VVF when VCF is needed delays compliance readiness — assess timeline carefully
- VVF + all add-ons may exceed VCF cost — calculate total cost of ownership before recommending
- Converge requires additional compute and network resources — plan capacity upfront
Self-Assessment Discussion Prompts
- At what scale does VCF become more cost-effective than VVF with add-ons?
- How would you handle a customer who wants micro-segmentation but has a VVF budget?
- What is the operational impact of transitioning from VVF management to SDDC Manager after converge?
- How does VVF fit into a multi-site architecture compared to VCF?
Extensions
VVF Deployment in Holodeck
Deploy a VVF environment using VCF Installer in Holodeck. Compare the wizard experience with VCF deployment. Document the differences in deployment time, configuration steps, and post-deployment management interface.
VVF Converge Lab Exercise
Starting from a deployed VVF environment, execute the VCF Installer converge process to upgrade to full VCF. Document each step, measure the time required, verify NSX and SDDC Manager deployment, and validate that existing VMs are unaffected.
VVF vs VCF TCO Analysis
Build a total cost of ownership comparison for a sample customer scenario (8 hosts, 2 sockets, 32 cores each). Compare: VVF base + all add-ons vs VCF base. Include licensing, support, and operational cost (additional staff training for VCF complexity).
⚠ Known Pitfalls (from Community KB)
References
- vSphere Foundation 9.0 Product Overview and Datasheet
- VMware VCF Installer 9.0 Guide — VVF Deployment and VCF Converge Process
- vSAN 9.0 ESA Architecture Guide — Storage for VVF and VCF
- Broadcom VCF 9.0 Licensing Guide — Per-Core Model for VVF and VCF
- VMware Live Recovery Administration Guide