27 articles in this category
Sizing for VCF Operations Orchestrator is a short answer, one fixed appliance spec and exactly three nodes. The longer part is building the cluster, which is a load balancer, three OVA deployments and five commands over SSH.
Every published VCF Automation configuration maximum from 9.0.0 to 9.1.1 on one page, Medium and Large profiles side by side. Those numbers are the All Apps figures, so the vRealize Automation limits that a VM Apps organization keeps are here too.
Two dropdowns in the planning workbook decide the VCF Automation footprint. Small deploys a single node, Medium and Large deploy a three node cluster, and the numbers follow from that. Figures taken from the VCF planning and preparation workbooks.
If the Migration Service Engine was patched before VCF Automation, both components end up stuck with a PackageDeploymentsCompleteWaitTimeout error. Broadcom KB 455559 has the recovery, and this is what it involves.
Patching the VCF Services Runtime component to 9.1.1.0, from prechecks through a five hour rolling replacement of every node, with the kubectl commands to follow it from the control plane.
How role-based access control works in VCF Automation. The Provider, Organization and Project scopes, the built-in roles at each level, and a permission matrix comparing the four project roles.
A patching order gotcha in VCF 9.1.1.0. If you patch the migration service engine before VCF Automation, the VCD_MIGRATOR upgrade runs for six hours and then fails on vmsp_upgrade.
The order in which to patch the VCF management components when going from 9.1.0.x to 9.1.1.0. Two components go in sequence, then the rest follow in no fixed order, with two that must run on their own.
A deep dive into what actually happens when VCF Automation is upgraded to 9.1.0.0, covering the inputs you need, the import, configure and precheck phases, and the new cluster that gets built during the upgrade.
How IP addresses move during an upgrade from Aria Automation 8.18.x to VCF Automation 9.1.x. Why you need a new runtime IP range, how your old node IPs come back as cluster VIPs, and why the load balancer never has to change.
Walking through the SDDC Lifecycle patch to 9.1.1.0, from setting the target version and running prechecks through to the component showing the new version.
Patching the VCF Operations component to 9.1.1.0, including the prechecks, the UI downtime to expect during the patch, and monitoring progress from the VCF Operations Admin UI.
A walkthrough of patching the VCF management services fleet lifecycle component from 9.1.0.0 to 9.1.1.0, with screenshots of the UI steps and what happens on the control plane node.
VCF 9.1.1.0 has been released as a maintenance release with an updated BoM. Here are the release notes links plus my notes on the known and resolved issues in VCF Automation and VCF Operations.
Upgrade Paths vSphere to VCF 9.0.x | How do we get there from here? |
VCF Operations for Networks 9.0.x | Install Guide |
Handling Postgres Startup and Cert Regeneration After a VCF 9.0.1 Fleet Management Reboot
VCF 9.0 to VCF 9.0.1 Management Components Upgrade & Patching Runbook
Retrieving password using locker API in VCF 9.0 for Management Components
Depot & Binary Management in VCF Operations fleet management appliance or OPS LCM 9.0
VCF Automation 9.0 Installation | Deep-Dive |
VMware Cloud Foundation 5.2.1 | What's New & Product Support Packs
VMware Aria Suite 8.18.0 Release | VCF 5.2 | Upgrade Repo and Product Support Pack Links |
Difference between System Upgrade, System Patch , PSPACK and Product Upgrades in Suite Lifecycle
Upgrading VMware Aria Suite Lifecycle | 8.12 to 8.14 | Deepdive |
Deploying VMware Aria Automation Orchestrator with vSphere Authentication using Suite Lifecycle 8.12
Deploying a vIDM clustered environment using NSX-T Loadbalancer