vcfa-upgrade · 5 articles
Moving Automation with TOP: Aria to VCF 9.1.1
Five steps with TOP: architecture and IPs, three source versions to 9.1.1, acceptance, identity retirement and gradual All Apps adoption.
Start the series
Every article
Aria to VCF Automation 9.1.1: TOP redraws the address book
Dedicated service runtimes, reused VIPs, new node IPs and internal CIDRs: understand the architecture before upgrading.
Upgrading to VCF Automation 9.1.1: TOP chooses the route
Sources 8.18.1, 9.0.x or 9.1.0: three routes to the same VCF Automation 9.1.1 target, with prechecks and a go/no-go decision.
VCF Automation 9.1.1 cutover: TOP asks for proof
Follow the migration, prove network and functional recovery, and keep an actionable recovery plan until acceptance.
Leaving vIDM with TOP: VM Apps identity and legacy retirement
Separate Provider SSO from VM Apps authentication, prepare vIDB OIDC, migrate access and prove vIDM and Lifecycle can retire.
VM Apps to All Apps with TOP: keep serving while rebuilding
Keep existing VM Apps services running while rebuilding and accepting All Apps services, one capability and one consumer wave at a time.




