Browse the complete collection of guides, runbooks, and troubleshooting articles.
274 articles
Fourteen resolved issues, five of them in the upgrade path. One of them lifts a datastore restriction, one formalises the Migration Service Engine ordering rule, and one was silently throwing away your proxy configuration while reporting success.
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.
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.
Product teams keep asking for applications that never go down. Here is why 100% uptime is not a real target, what people usually mean when they ask for it, and how to decide whether zero downtime upgrades are worth what they cost.
How the nervous system is put together, from the organisation chart down to a single neuron, with illustrations covering the CNS and PNS, action potentials, reflex arcs, and the sympathetic and parasympathetic branches.
New guides on VMware Cloud Foundation, Aria Suite, and infrastructure automation. Follow the blog in your feed reader and new posts show up as soon as they are published.
Using a different reader? Copy the feed URL and add it there.