VMware Cloud Foundation guides for architecture, deployment, upgrades, operations, NSX, vSAN, automation, security, migration, and recovery.
From Platform Capability to Operational Reality VCF 9.1 gives VMware teams a stronger private AI story. But having the platform capability is not the same thing as having an operating model. That distinction matters. A production AI platform needs more than GPU hosts and a few model endpoints. It needs clear consumption boundaries, network isolation, … Explore: Designing a Practical Private AI Operating Model with…
Traditional virtualization design habits do not automatically translate to inference-heavy AI platforms. That is not because virtualization suddenly stopped being useful. It is because the constraint model changed. For years, many virtualization clusters were designed around CPU consolidation, memory overcommit, shared storage resilience, and generalized mobility. That model worked well for mixed enterprise workloads where … Explore: The AI-Ready Cluster Is Different: GPU Placement, Memory…
How VCF 9.1 Reframes the Private Cloud Conversation For years, the VMware conversation was mostly about virtualization, consolidation, lifecycle management, and private cloud standardization. Those topics still matter. They are not going away. But AI has changed the center of gravity. The question is no longer just, “Can the platform run VMs reliably?” The better … Explore: AI Is Pushing VMware Beyond Virtualization
AI placement is becoming a real architecture decision. For the first wave of generative AI adoption, many organizations could experiment with hosted models, isolated copilots, and proof-of-concept retrieval systems without making hard infrastructure choices. That window is closing. AI is moving from isolated experiments into business workflows, operational systems, and agentic patterns that can retrieve … Explore: When to Keep AI On-Prem: Data Gravity, Latency,…
Scenario The VCF 9.1 upgrade path has been selected. The planning tool has been reviewed. The target version is understood. The team has a maintenance window on the calendar. That does not mean the environment is ready. A VCF 9.1 upgrade runbook needs to prove more than task order. It needs to prove that the … Explore: Building a VCF 9.1 Upgrade Runbook: Testing, Fallback,…
Enterprise AI is moving from experimentation into production design. That shift changes the conversation. The question is no longer, “Can we run a model on-prem?” The better question is, “Can we operate private AI as a secure, governed, scalable platform inside the enterprise?” That distinction matters because private AI is not just about GPU access. … Explore: Private AI Is Not a GPU Purchase: Comparing…
Build numbers are easy to treat as trivia until they become the deciding factor in a support case, security review, failed upgrade, or lifecycle audit. Most teams know whether they are running “vSphere 8” or “vSphere 9.” Fewer teams can quickly answer the more useful operational question: Which exact vCenter and ESX/ESXi builds are running … Explore: VMware vSphere Build Numbers in 2026: An Operational…
TL;DR A VCF 9.1 upgrade should not be treated like a normal maintenance window where each team updates its component, checks a dashboard, and leaves. The sequence matters. The ownership model matters. The readiness evidence matters. For VCF 9.1, VCF Operations is not a side task after the platform upgrade. Existing Aria Operations instances must … Explore: The VCF 9.1 Upgrade Is an Operating Model…
Private AI is not just a question of where to place GPUs. That is where the conversation often begins, but it is not where the real architecture work lives. The harder problem is deciding how private AI will be operated, governed, secured, monitored, scaled, and recovered once it moves beyond the proof of concept stage. … Explore: VCF 9.1 for Private AI: When the Private…
TL;DR VCF 9.1 changes the upgrade conversation because the management layer is no longer just a collection of adjacent appliances. VCF Operations, VCF Automation, VCF Management Services, license services, software depot, identity, logging, and lifecycle workflows become part of a more unified private cloud operating model. That means the VCF 5.2.x to 9.1 upgrade should … Explore: VCF 9.1 Management Services and Aria: Turning the…
TL;DR The VCF 5.2.x to 9.1 upgrade is not just a component upgrade. It changes how teams should think about ownership. In VCF 5.2.x, many operational responsibilities were still organized around product lanes and appliances: SDDC Manager, Aria Operations, Aria Suite Lifecycle, Aria Automation, Log Insight, Identity Manager, vCenter, NSX, and ESXi. VCF 9.1 pushes … Explore: VCF 5.2.x to 9.1: The Fleet vs Instance…
The first step in modernizing VCF Operations dashboards is changing the entry point from tools to services. The next step is harder. You have to decide what “healthy” actually means. That is where private cloud SLOs become useful. Not because infrastructure teams need to copy every SRE practice from application engineering, but because VCF operations … Explore: Designing Private Cloud SLOs in VCF Operations: Fleet…
Quick answer: prove readiness before generating the path An upgrade path becomes actionable only when the inputs, owners, recovery boundaries, and acceptance checks are agreed. Use this review to expose unresolved decisions before the planner session. Jump to ownership, DNS readiness, recovery boundaries, scoped inventory export, or the validation checklist. Broadcom’s VCF Upgrade Planner is … Explore: The VCF Upgrade Readiness Review: Decisions Before You…
Amazon Elastic VMware Service is not automatically a cloud strategy. Sometimes it is a landing zone. Sometimes it is a disaster recovery target. Sometimes it is a practical way to avoid a data center deadline. Sometimes it is a temporary bridge while application teams decide what to modernize. And sometimes it is just a cloud … Explore: Amazon EVS vs Private VCF: Cloud Escape Hatch…
Amazon Elastic VMware Service is easy to describe incorrectly. The shallow description is “VMware on AWS.” That is directionally true, but it misses the operational point. Amazon EVS is not just a place to run virtual machines. It is a way to place a VMware Cloud Foundation environment inside an AWS operating boundary, with Amazon … Explore: Amazon EVS as a VMware Cloud Landing Zone:…
VCF Private AI Services networking looks like an installer choice until you follow the consequences downstream. At first glance, the decision appears simple: deploy the vSphere Supervisor with traditional VDS networking and Foundation Load Balancer, or deploy it with VCF Networking using VPCs. Both can support Private AI Services. Both can get a Supervisor online. … Explore: VCF Private AI Services Networking: VDS + Foundation…
Introduction The first article in this series focused on multicloud control-plane sprawl. Azure, AWS, Google Cloud, and VMware Cloud Foundation each bring their own identity model, policy engine, network architecture, observability stack, automation surface, and lifecycle model. That is already enough to create governance fragmentation. AI agents add another layer. An agent is not just … Explore: AI Agents Are the New Control Plane: Governing…
TL;DR Compare Azure AI, Azure Local, and VCF Private AI against the workload’s data boundaries, latency, connectivity, governance, and operating model. Use the criteria and comparison tables to choose placement for each workload. Get new guides by email · Related reading: Private AI Is Not Model Hosting: A Reference Architecture for Sovereignty, Identity, GPUs, and … Explore: Azure AI, Azure Local, and vCF Private AI:…
TL;DR Multicloud is no longer just a workload placement problem. The harder problem is control-plane sprawl. Azure, AWS, Google Cloud, and VMware Cloud Foundation each bring their own identity model, policy engine, hierarchy, observability stack, network control plane, automation surface, and operational lifecycle. Those native control planes are useful. They become dangerous when each platform … Explore: Multi-Cloud Is Becoming Multi-Control-Plane: How to Avoid Governance…
Quick answer: On ESXi, identify the locked file, datastore type and lock owner before changing a VMware .lck file or stopping a process. VMFS uses metadata locks rather than .lck files; NFS requires a different workflow. A lock can belong to a running VM or a backup proxy. Use the VMFS vmfsfilelockinfo workflow or the … Explore: VMware .lck Files and ESXi VM Locks: Find…
Find an architecture guide, platform, or operational problem.
Suggested searches
