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
Forty three prechecks run before a VCF Automation upgrade, and most of them are testing things you can check yourself a week earlier. Here is what they look for, what the exit codes mean, and the thresholds worth knowing before you book the window.
Deploying a VCF instance asks you two questions about management services: which components run here, and how is the cluster built. The documentation answers both in two tables and two diagrams. Here is the same thing as a story.
VCF 9.1 adds password policies, so you can set length, complexity, expiration and lockout once and apply them across the fleet. VCF Operations keeps no copy of your passwords, and CyberArk integration gives you somewhere to store them.
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.