Page 2 of 24.
279 articles
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.
A prion is a protein folded the wrong way that forces its healthy neighbours to misfold too. What that means, why it matters for the human brain, and why the normal version of the protein is already sitting in your head right now.
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.
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.