Academy/VCP-VCF 9.0 Administrator (2V0-17.25)/Cloud Builder Bring-up (VCF 5.2) vs VCF Installer Bring-up (VCF 9.0): Workflow, Console and API Comparison
This lab targets VCF 9.0

Cloud Builder Bring-up (VCF 5.2) vs VCF Installer Bring-up (VCF 9.0): Workflow, Console and API Comparison

VCF 9.0Intermediateadminarchitectvcdx⏱ 120 min

VCF 9.0 replaces the Cloud Builder appliance with the VCF Installer, which becomes SDDC Manager after bring-up, and adds VCF Operations with the fleet management appliance as the fleet-level console. SDDC Manager remains in every VCF Instance (UI deprecated, appliance and API retained). The 5.2 side of this lab is a documented walkthrough; the 9.0 side is observed live in Holodeck 9.0.x.

Objectives

  • Describe the VCF 5.2 management-domain bring-up: Planning and Preparation Workbook, Cloud Builder appliance, deployment parameter workbook, validation, bring-up, SDDC Manager hand-off
  • Observe and explain the VCF 9.0 bring-up: VCF Installer appliance, binaries download, deployment wizard (new fleet or instance in an existing fleet), validation, deploy, Installer switched to SDDC Manager mode
  • Compare the post-deployment operational surfaces: SDDC Manager UI (5.2) versus VCF Operations Fleet Management plus the retained SDDC Manager appliance (9.0)
  • Map SDDC Manager API operations used in 5.2 to their 9.0 equivalents (SDDC Manager API retained; VCF Operations APIs for fleet functions) and test them against the Holodeck instance
  • Articulate the design decisions behind the fleet/instance model (single management point, fault isolation, licensing and lifecycle) and record them as a VCDX-style decision set

Prerequisites

One deployed Holodeck 9.0.x single-site pod (VCF Installer bring-up complete; vCenter, NSX Manager, SDDC Manager, VCF Operations and the fleet management appliance reachable from the Holodeck jump host). No VCF 5.2 environment is required: the 5.2 workflow is reviewed from the VCF 5.2 documentation and deployment parameter workbook.

Prior labs: holodeck-02 (Holodeck 9.0.x site deployment), vcp-admin-01 (VCF 9.0 architecture and construct hierarchy)

Required skills:

  • VCF architecture fundamentals (management domain vs workload domain; fleet vs instance)
  • Reading a VCF deployment parameter workbook and the VCF 9.0 Planning and Preparation Workbook
  • REST API navigation with curl or PowerShell (token-based authentication)
  • vSphere Client, SDDC Manager UI and VCF Operations console navigation

Lab Environment

Single Holodeck 9.0.x site: nested ESX hosts forming the management domain default cluster (vSAN ESA), the VCF Installer appliance now running in SDDC Manager mode, vCenter, a NSX Manager cluster, VCF Operations with the VCF Operations fleet management appliance and collector, and (if deployed) VCF Automation. Access is from the Holodeck jump host; the HoloRouter Post Deployment table lists FQDNs and credentials.

Mermaid source
graph TB
  JH["Holodeck jump host"] --> INST["VCF Installer appliance (now SDDC Manager mode)"]
  JH --> OPS["VCF Operations + fleet management appliance"]
  INST --> VC["vCenter (management domain)"]
  INST --> NSX["NSX Manager cluster"]
  OPS --> VC
  OPS --> INST
  VC --> ESX["Nested ESX hosts, vSAN ESA default cluster"]

IP Addressing

NetworkPurposeVLAN
10.1.1.0/24Holodeck management network (Installer/SDDC Manager, vCenter, NSX Manager, VCF Operations, fleet management appliance)VLAN 10 (Holodeck default)
10.1.2.0/24Holodeck vMotion network (Installer-assigned IP inclusion range)VLAN 11 (Holodeck default)
10.1.3.0/24Holodeck vSAN network (Installer-assigned IP inclusion range)VLAN 12 (Holodeck default)

Credentials

SystemUsernamePassword
VCF Installer / SDDC Manager UIadmin@localHolodeck documented default (Post Deployment table)
SDDC Manager API (token)administrator@vsphere.localHolodeck documented default (Post Deployment table)
VCF Operations consoleadminHolodeck documented default (Post Deployment table)
vCenter (vSphere Client)administrator@vsphere.localHolodeck documented default (Post Deployment table)

Tasks

Task 1 Walk through the VCF 5.2 management-domain bring-up (documented workflow)

Manageability

Build an accurate mental model of the 5.2 flow — Planning and Preparation Workbook, Cloud Builder appliance, deployment parameter workbook, validation, bring-up, SDDC Manager hand-off — so that every 9.0 difference observed later is a real difference and not a gap in 5.2 knowledge.

Step 1

Open the VCF 5.2 documentation section 'Deploying the Management Domain'. Record the documented sequence: (0) plan with the Planning and Preparation Workbook, (1) deploy the Cloud Builder appliance on an ESXi host or on Workstation/Fusion, (2) prepare at least four ESXi hosts, (3) fill in the deployment parameter workbook, upload it to Cloud Builder, validate, then bring up the management domain; after bring-up the management domain contains vCenter, vSAN and SDDC Manager.

Four-step 5.2 sequence written in the lab notebook with the component list that exists after bring-up (vCenter, vSAN, NSX, SDDC Manager).
Step 2

Open 'About the Deployment Parameter Workbook' (5.2). List the worksheets and the inputs each carries (Credentials with per-account password rules; Hosts and Networks; Deploy Parameters including licences in key-based mode). Note the documented limits: the workbook cannot validate everything in Excel, some failures surface only after upload to Cloud Builder, and cut-and-paste between cells is discouraged.

Worksheet list with the inputs per sheet and the three documented validation caveats.
Step 3

Record the 5.2 post-bring-up steps from the same chapter: download the deployment report, Finish, Launch SDDC Manager, then power off the Cloud Builder appliance; afterwards configure the SDDC Manager repository (depot) credentials.

Note states that Cloud Builder is a disposable bootstrap appliance in 5.2 and that SDDC Manager is the Day-2 console from this point.
Step 4

Write the 5.2 operator surface as a table: console (SDDC Manager UI), lifecycle (SDDC Manager bundles via the online depot or offline bundle transfer), passwords (SDDC Manager password management with scheduled rotation at 30/60/90 days, ESXi root excluded), certificates (SDDC Manager certificate management), host commissioning (SDDC Manager UI), workload domains (SDDC Manager UI), API (SDDC Manager public API /v1/*).

Seven-row table completed for 5.2; this is the left-hand column for Task 4.

Validation Gate

Check: Notebook holds the 5.2 four-step sequence, the workbook worksheet list with caveats, the post-bring-up hand-off steps and the seven-row 5.2 operator surface table.

Expected: All four artefacts present; every row cites the 5.2 chapter it came from.

Common Errors

The table lists Cloud Builder as a Day-2 console
Cause: Cloud Builder is powered off after bring-up in 5.2
Fix: Move Day-2 operations to SDDC Manager in the table
Password rotation recorded as manual-only in 5.2
Cause: Confusion with the 9.0.x known issue
Fix: 5.2 SDDC Manager offered scheduled rotation (30/60/90 days); ESXi root was never auto-rotated

Task 2 Observe the VCF 9.0 bring-up artefacts in Holodeck (VCF Installer, deployment wizard, SDDC Manager mode)

Manageability

See the 9.0 flow as it actually ran: the VCF Installer appliance, its binaries depot, the deployment wizard choices, the validation stage and the fact that the Installer appliance is now SDDC Manager. This replaces the 5.2 Cloud Builder picture with the documented 9.0 one.

Step 1

From the Holodeck jump host, open https://<installer-fqdn> (the appliance the Holodeck deployment used as the VCF Installer) and log in as admin@local. Confirm the appliance now presents the SDDC Manager UI (the Installer is switched to SDDC Manager mode after management-domain storage is configured; its local disk is not part of management storage).

SDDC Manager UI loads on the former Installer FQDN; Inventory shows the management domain, its cluster and hosts.
Step 2

Compare the appliance specification with the documentation: VCF Installer resource requirements are 4 vCPU, 16 GB RAM and 914 GB storage (VCF 9.0.1, Deploy the VCF Installer Appliance). In the vSphere Client, select the appliance VM and record vCPU, memory and provisioned disk; note whether the VM now lives on the vSAN datastore (Storage vMotion during bring-up).

VM summary recorded; VM resides on the management vSAN datastore.
Do not change the appliance's hardware or storage; this is an observation step.
Step 3

Review the deployment wizard inputs that Holodeck supplied, using the VCF 9.0.1 wizard steps as the checklist: deployment type (new VCF fleet vs instance in an existing fleet), existing components (VCF Operations reuse), general configuration (VCF Instance name, management domain name, deployment model Simple vs High Availability three-node, password creation — auto-generated passwords are 20 characters), VCF Operations and VCF Automation details, vCenter, NSX Manager, storage (principal storage type is fixed per cluster once created), ESX hosts (common root password unless a JSON spec is used), networks (VM management port group, vSAN and vMotion IP inclusion ranges), vSphere Distributed Switch profile (Default, Storage Traffic Separation, NSX Traffic Separation, both, or Custom), SDDC Manager details, review, validation, deploy. In SDDC Manager > Inventory and vCenter, find the values Holodeck used for the deployment model, the vDS profile and the IP inclusion ranges.

Wizard checklist annotated with the Holodeck values for deployment model, vDS profile, vSAN/vMotion ranges and storage type.
Step 4

In the vSphere Client, inspect the management cluster: number of hosts, vSAN ESA storage pool per host (no disk groups), vSphere HA and DRS enabled, the vDS and its port groups (management, vMotion, vSAN, NSX overlay) matching the chosen profile. Record how these map to the wizard inputs from step 3.

Cluster facts recorded: host count, ESA storage pool, HA/DRS on, port groups matching the vDS profile.
Step 5

Open the VCF Operations console (https://<vcf-ops-fqdn>) and navigate to Fleet Management > Lifecycle. Confirm the VCF Instance appears with its components and versions, and that the VCF Operations components (fleet management appliance, collector, and VCF Automation if deployed) are listed. This is the fleet-level view that does not exist in 5.2.

Fleet Management > Lifecycle lists the Holodeck VCF Instance and the VCF Operations components at their deployed versions.
Step 6

Write the 9.0 bring-up sequence in the notebook: deploy VCF Installer OVA → download binaries to the Installer depot (online or VCF Download Tool offline) → deployment wizard (new fleet or instance in existing fleet; VCF Automation can be skipped for Day-N) → validate → deploy → Installer becomes SDDC Manager → VCF Operations (and fleet management appliance) available for Day-2. Mark each item OBSERVED (seen in Holodeck) or DOCUMENTED (from the 9.0.1 docs).

Sequence written with every item tagged OBSERVED or DOCUMENTED.

Validation Gate

Check: SDDC Manager UI reached on the former Installer FQDN; appliance resources and datastore recorded; wizard checklist annotated; cluster facts recorded; Fleet Management > Lifecycle shows the instance; 9.0 sequence written with evidence tags.

Expected: All six items present; no step relies on an unobserved claim without a DOCUMENTED tag.

Common Errors

Installer FQDN shows a deployment wizard instead of SDDC Manager
Cause: Bring-up did not complete or the appliance was not switched to SDDC Manager mode
Fix: Check the Holodeck deployment status (Get-HoloDeckStatus) and the Installer Tasks panel; complete or retry the deployment before continuing
VCF Operations shows no VCF Instance under Lifecycle
Cause: Collector or fleet management appliance still initialising, or the instance integration not yet collected
Fix: Wait for the first collection cycle; verify the VCF Operations collector appliance is powered on and registered
Looking for disk groups on the ESA cluster
Cause: ESA uses a single-tier storage pool
Fix: Read Cluster > Configure > vSAN > Disk Management as a storage pool; disk groups exist only in OSA

Task 3 Compare the operational surfaces: SDDC Manager UI (5.2) vs VCF Operations Fleet Management + SDDC Manager (9.0)

Manageability

Produce the console map an administrator needs in 9.0: which Day-2 operations moved to VCF Operations, which remain in the (deprecated but present) SDDC Manager UI, and where the 9.0.x known issues force a path.

Step 1

In VCF Operations, open each Fleet Management menu and record what it offers: Lifecycle (component inventory and updates per instance, cluster image updates through vSphere Lifecycle Manager), Certificates (inventory and replacement per instance), Passwords (view, update, remediate), Identity & Access (VCF SSO, Active Directory, identity provider).

Four Fleet Management menus documented with their visible actions.
Step 2

In the SDDC Manager UI on the same instance, record the surfaces that still exist: Inventory (domains, hosts), Lifecycle Management (bundle management), Security > Password Management (rotate, rotate all, schedule rotation), Security > Certificate Authority, Administration (repository/depot settings, backup). Note the deprecation banner: the SDDC Manager UI is deprecated and will be removed in a future major release; the appliance and API remain.

SDDC Manager UI surfaces documented with the deprecation note.
Step 3

Complete the comparison table started in Task 1 with a 9.0 column: console (VCF Operations; SDDC Manager UI deprecated), lifecycle (Fleet Management > Lifecycle driving SDDC Manager per instance), passwords (Fleet Management > Passwords for view/update/remediate; rotate and schedule rotation only in SDDC Manager UI/API in 9.0.x — documented known issue), certificates (Fleet Management > Certificates), host commissioning (vSphere Client > Global Inventory Lists > Hosts > Unassigned Hosts > Commission Hosts, or SDDC Manager UI), workload domains (created in VCF Operations), API (SDDC Manager API retained; VCF Operations APIs for fleet functions).

Seven-row, two-column table complete; the password row cites the 9.0.1 release-notes known issue.
Step 4

Exercise one non-destructive path per column: in VCF Operations open Fleet Management > Passwords and view the managed accounts for the instance (do not change anything); in the SDDC Manager UI open Security > Password Management and confirm the rotate options exist there. Record how long after deployment the accounts became visible in VCF Operations (the 9.0.1 notes allow up to a day).

Both views reached; account visibility delay recorded (or 'visible immediately').
Step 5

Record the host-commissioning entry points without commissioning anything: vSphere Client > Global Inventory Lists > Hosts > Unassigned Hosts > Commission Hosts, and SDDC Manager UI > Hosts > Commission Hosts. Note the documented rules: hosts commissioned for vSAN ESA can only join ESA clusters, OSA to OSA, NFS/FC/vVols to matching clusters; SSH is enabled briefly to collect the host key.

Both entry points screenshotted; storage-type binding rules written down.
Step 6

Summarise in five lines what an administrator moving from 5.2 to 9.0 must relearn: one console for the fleet, the Installer-becomes-SDDC-Manager pattern, the retained SDDC Manager API, the 9.0.x password-rotation path, and host commissioning from the vSphere Client.

Five-line summary written; each line maps to a row of the comparison table.

Validation Gate

Check: Comparison table has seven rows and both version columns filled with console paths; the password and commissioning rows carry their documentation references; the five-line summary exists.

Expected: Table complete and consistent with what was observed in VCF Operations and SDDC Manager.

Common Errors

Password rotation attempted from VCF Operations
Cause: Rotate/schedule options are not present in VCF Operations 9.0.x
Fix: Use SDDC Manager UI or API for rotation; VCF Operations for view/update/remediate
Host commissioning searched for under VCF Operations
Cause: Commissioning lives in the vSphere Client (or SDDC Manager UI) in 9.0
Fix: Use Global Inventory Lists > Hosts > Unassigned Hosts > Commission Hosts
Table claims SDDC Manager was removed in 9.0
Cause: Conflating UI deprecation with appliance removal
Fix: SDDC Manager appliance and API remain in every VCF Instance; only the UI is deprecated

Task 4 Map and test the APIs: SDDC Manager API (retained) and VCF Operations

Manageability

Show that automation written against the SDDC Manager public API in 5.2 still has a target in 9.0, and identify which fleet-level functions are reached through VCF Operations instead.

Step 1

From the jump host, obtain an SDDC Manager API token from the former Installer appliance (now SDDC Manager): POST https://<sddc-manager-fqdn>/v1/tokens with the admin@local credentials in the JSON body (the account the VCF documentation uses to obtain an SDDC Manager API token). Record the access token.

curl -k -s -X POST https://<sddc-manager-fqdn>/v1/tokens -H 'Content-Type: application/json' -d '{"username":"admin@local","password":"<admin@local password>"}'
HTTP 200 with accessToken and refreshToken in the response.
Step 2

List the domains and hosts with the token: GET /v1/domains and GET /v1/hosts. Record the management domain id and the host status values (ASSIGNED for cluster members; UNASSIGNED_USEABLE for free-pool hosts).

curl -k -s https://<sddc-manager-fqdn>/v1/domains -H 'Authorization: Bearer <token>'
curl -k -s https://<sddc-manager-fqdn>/v1/hosts -H 'Authorization: Bearer <token>'
Domain list shows the management domain; hosts list shows the nested ESX hosts with their status.
Step 3

Record the SDDC Manager API operations the 9.0 documentation still routes through this API: stretching a vSAN cluster (Stretch a vSAN ESA or OSA Cluster Using the SDDC Manager API), JSON-specification deployments through the Installer (LAG uplinks, per-host ESX passwords), and password rotation for core components (9.0.x known issue workaround). Note that the Installer's deployment wizard can also download and re-upload the JSON specification.

Three documented API-only or API-first operations listed with their 9.0 chapter names.
Step 4

In VCF Operations, open the API documentation link from the console (Administration > Integrations area or the product API docs on developer.broadcom.com) and record which fleet functions are API-exposed there: VCF Operations integrations (adding a VCF endpoint), lifecycle operations and inventory for the fleet. Do not create or modify any integration.

VCF Operations API entry points recorded for integrations, lifecycle and inventory.
Step 5

Write the API mapping: 5.2 SDDC Manager API /v1/* → 9.0 SDDC Manager API /v1/* (same endpoint family, per instance); 5.2 Aria Suite Lifecycle API → 9.0 VCF Operations fleet management (Lifecycle); 5.2 SDDC Manager password API → 9.0 SDDC Manager password API for rotation, VCF Operations for view/update/remediate. Mark each mapping OBSERVED (tested here) or DOCUMENTED.

Mapping table complete with evidence tags; the token and domain calls are OBSERVED.

Validation Gate

Check: Token obtained; /v1/domains and /v1/hosts responses recorded; three API-first operations listed; VCF Operations API entry points recorded; mapping table with evidence tags.

Expected: All API calls returned HTTP 200 against the Holodeck SDDC Manager; nothing was created or changed.

Common Errors

401 from /v1/tokens
Cause: Wrong account or password — the documented token request uses admin@local and the password set for it at deployment
Fix: Retry with admin@local and the Holodeck documented default password
Certificate error from curl
Cause: VMCA-signed certificate on the lab appliance
Fix: Use -k in the lab only; in production import the CA chain
Expecting a separate 'fleet' API host
Cause: There is no Fleet Manager API endpoint
Fix: Fleet functions are VCF Operations APIs; instance operations are the SDDC Manager API

Task 5 Record the design decisions behind the fleet/instance model and a 5.2 → 9.0 transition path

Availability

Turn the observations into VCDX-style decisions: what the fleet model changes for availability, lifecycle, licensing and operations, and how an existing 5.2 estate reaches 9.0.

Step 1

Decision 1 — management single point: the first instance's management domain hosts VCF Operations, the fleet management appliance and VCF Automation. Record the implication (its loss stops fleet-level Day-2 operations for every instance, while workloads keep running) and the mitigation (vSphere HA for the management VMs, file-based backups of SDDC Manager, vCenter, NSX and VCF Operations, tested restore).

Decision record with justification, implication and mitigation.
Step 2

Decision 2 — fault isolation per instance: each VCF Instance keeps its own SDDC Manager, vCenter and NSX; workload domains never share the management domain's NSX Manager cluster. Record when to add a second instance rather than another workload domain (site boundary, independent lifecycle, blast radius).

Decision record with the instance-vs-domain criteria.
Step 3

Decision 3 — licensing and lifecycle: VCF Operations is licensed in connected licensing mode (VCF-OPS-RECD-LIC-001) or offline; the VCF or vSphere Foundation licence is added in VCF Operations and vCenter instances are licensed from there (90-day evaluation until licensed); lifecycle runs from Fleet Management > Lifecycle with SDDC Manager executing per instance. Record the implication for air-gapped sites (offline binaries via the VCF Download Tool).

Decision record covering licensing mode and the offline path.
Step 4

Transition path for a 5.2 estate (documented order): management planes first — VCF Operations and the fleet management appliance on version 9 (Aria Suite Lifecycle has no upgrade path to 9), then per instance SDDC Manager (to 9.0.1 or later before NSX, vCenter or ESX per the 9.0.1 release notes), NSX Manager, vCenter, ESX hosts, then the vSAN on-disk format. Alternative for non-VCF vSphere estates: converge with the VCF Installer, or import an existing vCenter as a workload domain from VCF Operations (in VCF 9.0 these replace the 5.x VCF Import Tool). Record which path fits a greenfield lab (Holodeck: fresh Installer deployment) and which fits a brownfield production estate.

Transition path written with the documented order and the greenfield/brownfield choice.
Step 5

Close the lab: take the Holodeck instance snapshot 'vcp-admin-03-complete' with the instance stopped, and file the comparison table, API mapping and the three decision records in the lab notebook for reuse in the VCDX design.

Snapshot exists; notebook artefacts filed.

Validation Gate

Check: Three decision records (single point, fault isolation, licensing/lifecycle) with justification and implication; transition path in the documented order; closing snapshot taken.

Expected: Decisions trace to observations in Tasks 2-4 and to the cited 9.0.1 chapters; the upgrade order matches KB 390634 and the 9.0.1 release notes.

Common Errors

Transition path starts with SDDC Manager
Cause: 5.2 habit
Fix: In 9.0 the management planes (VCF Operations, fleet management appliance) go first; SDDC Manager follows, then NSX, vCenter, ESX
Decision text calls the fleet a stretched infrastructure
Cause: Over-reading the fleet construct
Fix: The fleet is a management scope; DR between instances is a replication/recovery design

Final Validation

The candidate can describe the 5.2 Cloud Builder flow and the 9.0 VCF Installer flow from the documentation and from Holodeck observation, hold a complete console and API map between the two releases (including the 9.0.x password-rotation known issue and the retained SDDC Manager API), and defend three design decisions about the fleet/instance model plus a documented 5.2 → 9.0 transition order.

✓ 5.2 bring-up sequence, workbook structure and operator surface documented from the 5.2 chapters → Notebook entries cite the chapter names

✓ 9.0 bring-up artefacts observed in Holodeck: SDDC Manager mode on the Installer FQDN, wizard inputs mapped, Fleet Management > Lifecycle showing the instance → All items tagged OBSERVED

✓ Seven-row console comparison table (5.2 vs 9.0) complete → Password row cites the 9.0.1 known issue; commissioning row names the vSphere Client path

✓ SDDC Manager API token, /v1/domains and /v1/hosts calls succeeded; API mapping written → HTTP 200 responses recorded; no configuration changed

✓ Three decision records and the transition path written → Upgrade order: management planes → SDDC Manager → NSX → vCenter → ESX → vSAN on-disk format

Cleanup / Restore

Snapshot: vcp-admin-03-complete

• Stop the Holodeck instance before taking the closing snapshot (nested vSAN and SDDC Manager state must not be captured mid-flight)

• Revoke nothing: the API token expires on its own; no integrations, passwords or hosts were changed in this lab

• File the comparison table, API mapping and decision records in the lab notebook for the VCDX design

Design Reflection (VCDX)

The 9.0 change is not a renamed Cloud Builder. The Installer becomes SDDC Manager, so every instance still carries an instance-level control plane and API, while VCF Operations with the fleet management appliance becomes the fleet-level console. A VCDX design must therefore (1) protect the first instance's management domain as the fleet's management single point of failure, (2) decide instance boundaries on fault-isolation and lifecycle grounds rather than on console convenience, (3) place licensing and lifecycle in VCF Operations with an explicit offline path for air-gapped sites, and (4) state the 5.2 → 9.0 order (management planes first) in the transition plan. Be ready to say what is OBSERVED in a lab and what is DOCUMENTED when a panel asks.

Requirements

  • Describe the VCF 5.2 Cloud Builder bring-up and hand-off to SDDC Manager from the documentation
  • Observe the VCF 9.0 Installer bring-up outcome in Holodeck and map it to the documented wizard
  • Produce a console and API map between 5.2 and 9.0 including the 9.0.x known issues
  • Record three design decisions for the fleet/instance model and a documented transition order

Constraints

  • Holodeck provides a VCF 9.0.x instance only; the 5.2 side is a documentation walkthrough, not a live deployment
  • The Installer appliance has already become SDDC Manager in a deployed Holodeck site, so the wizard is reconstructed from inventory and the 9.0.1 wizard documentation rather than clicked through
  • 9.0.x: password rotate/schedule options are absent from VCF Operations (release-notes known issue); account and certificate inventories can take hours to appear after onboarding

Assumptions

  • The Holodeck 9.0.x deployment completed and the Post Deployment table credentials are valid
  • The jump host can reach the SDDC Manager, VCF Operations and vCenter FQDNs over HTTPS
  • Evaluation licensing is acceptable for the lab (VCF Operations runs 90 days unlicensed)

Risks

  • Running API calls that create or change objects — IMPACT: lab drift and broken later labs, MITIGATION: this lab is read-only; only GET and the token POST are used
  • Taking the closing snapshot with the instance running — IMPACT: inconsistent nested vSAN state on revert, MITIGATION: Stop-HoloDeckInstance first
  • Relying on 5.2 habits (SDDC Manager first) in the transition plan — IMPACT: unsupported upgrade order, MITIGATION: cite the 9.0.1 release notes and KB 390634 in the decision record

Self-Assessment Discussion Prompts

  1. Which 5.2 automation would break in 9.0 even though the SDDC Manager API is retained, and why (hint: fleet-level functions and identity)?
  2. When would you deploy a second VCF Instance into the existing fleet instead of adding a workload domain to the first instance?
  3. What is the recovery order if the first instance's management domain is lost, and which other instances are affected during the outage?

Extensions

Deploy a workload domain from VCF Operations and compare with the 5.2 SDDC Manager workflow

Commission two free-pool hosts from the vSphere Client, create a workload domain in VCF Operations, and document where the 5.2 SDDC Manager workflow differed (entry point, NSX Manager choice: share an existing workload NSX Manager cluster or deploy a new one).

harder

Download and edit the Installer JSON specification

From the VCF Installer wizard documentation, reconstruct the JSON specification for the Holodeck deployment (download it from a fresh Installer in a second Holodeck site if available) and identify the fields that have no wizard equivalent (LAG uplinks, per-host ESX passwords).

harder

Walk the 5.2 → 9.0 upgrade order against a 5.2 topology diagram

Using the VCF 5.2 documentation topology (Cloud Builder, SDDC Manager, Aria Suite Lifecycle, vCenter, NSX, ESXi), annotate the diagram with the 9.0 documented order and the components that are new installations rather than upgrades (VCF Operations for logs, VCF Identity Broker).

same

PowerCLI/PowerShell version of Task 4

Repeat the token, domains and hosts calls with Invoke-RestMethod and store the results as JSON for the lab notebook.

same

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.