VMware Cloud Foundation

VCF 9.0 GA Mental Model Part 6: Topology and Identity Boundaries for Single Site, Dual Site, and Multi-Region

by

TL;DR Architecture Diagram Table of Contents Scope and terminology guardrails You will move faster as an organization if you treat these as non-negotiable guardrails: For topology conversations, you also need consistent physical vocabulary: Assumptions Decision criteria Use these criteria to keep topology and identity debates grounded in operational outcomes: Challenge You need a topology and … Read more

VCF 9.0 GA Mental Model Part 5: Topology Patterns for Single Site, Two Sites, and Multi-Region

by

TL;DR If you want architects, operators, and leadership aligned, you need a topology mental model that starts with VCF objects and only then maps to your physical sites. Architecture Diagram Table of Contents Scenario You are about to deploy VCF 9.0 GA greenfield and you need a shared language for: Scope and version alignment This … Read more

VCF 9.0 GA Mental Model Part 4: Fleet Topologies and SSO Boundaries (Single Site, Dual Site, Multi-Region)

by

TL;DR Architecture Diagram Table of Contents Scope and Code Levels This article is written against VCF 9.0 GA terminology and design guidance. Version Compatibility Matrix Use this as your “shared truth” when people ask “what exactly are we talking about?” Component Version Build VMware Cloud Foundation 9.0 24755599 VCF Installer 9.0.1.0 24962180 ESX 9.0.0.0 24755229 … Read more

VCF 9.0 GA Mental Model Part 3: Day-0 to Day-2 Ownership Across Fleets, Instances, and Domains

by

TL;DR If you want clean accountability in VCF 9.0, anchor your operating model to the official hierarchy: VCF private cloud -> VCF fleet -> VCF instance -> VCF domain -> vSphere clusters. This post translates that hierarchy into an operating model: who owns what, where day-0/day-1/day-2 work happens, and how topology (single site vs two … Read more

VCF 9.0 GA Mental Model Part 2: Fleet Services vs Instance Management Planes (and Who Owns What)

by

TL;DR Standardize on the official hierarchy: VCF private cloud -> VCF fleet -> VCF instance -> VCF domain -> vSphere clusters. A VCF fleet is managed by one set of fleet-level management components (notably VCF Operations and VCF Automation), while each VCF instance keeps its own management domain and domain-level control planes. Your fastest path … Read more

VCF 9.0 GA Mental Model Part 1: Fleets, Instances, Domains, and the Fleet Management Layer

by

TL;DR If you want alignment fast, standardize on this hierarchy and ownership split: Architecture Diagram Table of Contents Scenario You need architects, operations, and leadership to answer the same questions the same way: If you do not standardize vocabulary, you end up with: Series map This topic is usually too big for one post, so … Read more