Introduction
Migrating from a standalone VMware stack to a fully integrated cloud platform has always been more evolution than revolution. With the transition from vSphere 8.0 U3 and the traditional VMware Aria Suite Lifecycle Manager, VMware Aria Operations, and VMware Aria Automation stack toward VMware Cloud Foundation 9.0.2, that evolution becomes very tangible. What used to be a collection of loosely coupled management components is now converging into a single, opinionated platform with a unified lifecycle, control plane, and operational model.
At the heart of this convergence lies the introduction of VCF Operations, along with the VCF Operations Fleet Manager. These components fundamentally change how lifecycle, monitoring, and orchestration are delivered. Instead of managing individual appliances through Aria Suite Lifecycle Manager, organizations now adopt a Fleet-driven model, where deployment, configuration, and ongoing operations are tightly controlled and centrally orchestrated.
This shift is not just a rebranding exercise. It represents a deeper architectural realignment where VCF Automation replaces Aria Automation, and the platform aligns with the capabilities of vSphere 9, bringing infrastructure and management closer together under a single operational contract. The result is a more deterministic deployment model, but also one that requires a solid understanding of dependencies, sequencing, and especially the bootstrap process of new control plane components.
In this blog series, we will walk through the convergence journey from a working vSphere 8.0 U3 environment with Aria components toward a fully realized VCF 9.0.2 platform. We will highlight the critical transition points, common pitfalls, and the practical considerations that arise when introducing Fleet Manager and shifting away from Lifecycle Manager-based operations.
For reference, the official upgrade workflow is documented here:
View official documentation
Jonathan McDonald has written a nice blog about this process as well.
Whether you are approaching this from a design perspective or executing the upgrade in a live environment, understanding this convergence is key to avoiding subtle failure scenarios that only surface once the new control plane takes over.
Step 1 – Prerequisites
Before initiating the convergence toward VMware Cloud Foundation 9.0.2, it is essential to bring the existing Aria stack into a fully supported and upgrade-ready state. In practice, most issues during the transition to VCF Operations and the introduction of the VCF Operations Fleet Manager can be traced back to gaps in this preparation phase.
The first key requirement is ensuring that VMware Identity Manager (vIDM) 3.3.7, if available, is patched to a supported level. Broadcom explicitly mandates this as part of the upgrade path, and skipping this step will block or destabilize the migration workflow. The required patching guidance is documented here.
In parallel, VMware Aria Suite Lifecycle Manager must be upgraded to a version that supports the transition to VCF Operations. At the time of writing, this means applying VMware Aria Suite Lifecycle 8.18 Patch 7.
This step is not just a formality. Lifecycle Manager is still responsible for orchestrating the transition phase, even though it will ultimately be removed from the architecture. Ensuring it is fully up to date guarantees compatibility with newer VCF-based workflows.
The deployment of the Fleet Manager as part of the transition
This introduces a new dependency chain during the upgrade:
- Deployment of the Fleet Manager appliance
- Bootstrap and configuration injection
- Registration into the VCF Operations control plane
Unlike previous upgrades, this step introduces stricter requirements around:
- Network reachability
- DNS consistency (forward and reverse)
- Timing during first boot and bootstrap
Skipping or underestimating this step often leads to partially deployed environments that are difficult to recover.
Step 2 – Upgrading Aria Operations through Aria Suite Lifecycle Manager
Preparing the binaries
Before triggering the upgrade, ensure that all required binaries are available and correctly mapped. Two components are mandatory:
- Fleet Manager OVA
VCF-OPS-Lifecycle-Manager-Appliance-9.0.0.X.XXXXXXX.ova - Operations Upgrade PAK
Operations-Upgrade-9.0.0.X.XXXXXXXX.pak
A practical approach is:
- Upload both files to
/data - Trigger a binary mapping refresh
Executing the upgrade workflow
The steps below have been outlined before in my previous blog.
- Trigger Inventory Sync
Ensures Lifecycle Manager has an up-to-date view - Select VCF License Type
Transitions toward a VCF-aligned model - Run Assessment
Validates readiness - Snapshot Phase
Critical rollback point - Infrastructure Properties Input
- IP / subnet
- DNS / hostname
- gateway
- integration endpoints
- Precheck Execution
- Submit Upgrade
What actually happens under the hood
- Aria Operations detaches from Lifecycle Manager
- Upgrades to VCF Operations
- Fleet Manager is deployed
- Registration into Fleet Manager
- Cloud Proxies are upgraded
Why this step is different
A controlled migration from a Lifecycle Manager-centric model to a Fleet-driven control plane
- Successful OVA deployment
- Correct configuration injection
- Bidirectional connectivity
Key takeaway
This is not just an upgrade – it is a pivot point in the architecture.
- Binaries correctly staged
- Accurate infrastructure inputs
- Validated connectivity