VMWARE BY BROADCOM · ARCHITECTURE · OPERATIONS
Make your next VMware decision with confidence.
A practical starting point for VMware Cloud Foundation, vSphere, NSX, vSAN, and Private AI. Follow a curated path from platform choice to design, upgrades, troubleshooting, and recovery.
Start with the decision in front of you
Choose a pathway, read the starting guide, then follow the supporting references. Version labels describe the scope of the guides; confirm your exact build and supported path in the current vendor documentation.
01 · PLATFORM CHOICE
Choose the right VMware platform
VVF 9.0 · VCF 9.1
Compare workload needs, platform capabilities, operational effort, and entitlement questions before committing to a design.
Start here: VVF and VCF compared
02 · UPGRADES & LIFECYCLE
Plan a controlled upgrade
VCF 5.2.x to 9.1 · source-build dependent
Connect source eligibility, component dependencies, maintenance impact, validation, and recovery ownership.
Start here: VCF 5.2.x to 9.1 upgrade runbook
03 · NSX NETWORKING
Design and troubleshoot connectivity
NSX · consult each guide’s release scope
Work from network intent to packet paths, MTU, segmentation, and the boundary between physical and virtual networking.
Start here: NSX overlay networking and MTU
04 · STORAGE & RECOVERY
Make failure and recovery explicit
vSphere storage · VCF 9.1 recovery design
Understand storage failure behavior and the dependencies needed to recover workloads across vSAN, VMFS, and NFS.
Start here: Understand PDL and APD storage failures
05 · OPERATIONS & AUTOMATION
Operate the fleet with clear ownership
VCF 9.x · version-specific workflows
Connect fleet services, health, certificates, licensing administration, and API-driven operations to named owners.
Start here: VCF Operations Fleet Management
06 · PRIVATE AI & KUBERNETES
Design governed AI services
VCF 9.1 architecture · 9.1.1 release analysis
Plan identity, data boundaries, GPU capacity, networking, and service ownership before introducing shared AI services.
Start here: Private AI reference architecture
What changed, who is affected, what to do
Selected updates for platform planning. Sources checked September 20, 2026. This is a dated selection, not a complete release or security advisory feed.
September 18, 2026
Check automation runtimes before updating tools
What changed: Broadcom’s hardening update describes dependency and runtime changes across VCF SDK 9.1.1, PowerCLI 9.1.1, and the vSphere Terraform provider.
Who is affected: Teams maintaining scripts, SDK integrations, and infrastructure as code.
What to do: Inventory automation runtimes and dependencies, then check the applicable release notes before upgrading.
September 3, 2026
VCF 9.1.1 changes several platform boundaries
What changed: The general availability announcement covers multi-tenant AI model sharing, an AI assistant, and EVPN networking enhancements.
Who is affected: VCF platform, network, Kubernetes, and AI service owners.
What to do: Map each capability to your topology, dependencies, and service ownership. Start with the VCF 9.1.1 architecture analysis.
September 3, 2026
Keep the GitOps preview boundary visible
What changed: The VCF Automation organization self-service GitOps integration is a technology preview. Broadcom distinguishes it from the production-supported Argo CD Supervisor service accessed through vCenter.
Who is affected: Platform engineers planning tenant self-service and application delivery.
What to do: Record which integration your design uses and its release status before making production commitments.
Keep the source beside the decision
Use these references alongside the guides when validating a platform change.
- VCF 9.1.1 release notes for the release’s documented changes and known issues.
- VCF Upgrade Planner guide for building a plan around your installed components.
- vSphere build-number validation runbook for checking inventory against vendor release records.
- Broadcom’s resource center for vendor guides, reference architectures, and learning resources.
Digital Thought Disruption provides architecture analysis and documentation-based operational guidance. Product requirements and support boundaries remain governed by the applicable vendor documentation. Validate procedures against your own environment before making a production change.
Curated by Paul Bryant. View qualifications and public references.
Working across VMware, Azure, and other platforms?
Continue in Hybrid Platforms for cross-vendor architecture, shared-service dependencies, migration choices, and operating models.