Technical Blog
Upgrade guides, troubleshooting runbooks and architecture notes for VMware Cloud Foundation and Aria Suite. All original, all tested in my own lab. If it is here, I have run it.
The latest from the blog
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.
The two get used interchangeably and they solve completely different problems. What separates them, the two numbers that define both, and a worked example of three failures where only one of them saves you.