Three layers: Aria control plane, cloudbase-init first boot, file-share build engine

Windows Server 2025 via Aria Automation, part 1: the pipeline

One catalog request, one fully built, domain-joined Windows Server 2025 with its agents, a validation report, and no trace of the tooling that built it. The three-layer design, and why each seam is where it is.

17 September 2026 · Updated 1 October 2026 · Adam Stretton
Seven demo apps behind seven VIPs on one VCFA-deployed VKS cluster

Seven demo apps, one request: deploying a showcase stack via VCF Automation

Seven demo apps, Pac-Man and KubeDoom among them, on a VKS cluster that VCF Automation built in a tenant VPC, each with its own NSX virtual IP. The proper tenanted path, what you get for free, and the traps.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
One blueprint: namespace, trunk topology, two nested hosts, two VIPs — requested as a catalog item

A datacenter in a catalog tile: nested ESXi pods via VCF Automation All Apps

The whole isolated pod, nested ESXi hosts and all, as one VCF Automation blueprint in the catalog. How the blueprint is built, the order it enforces, and the three things it can’t express.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
ContentValid: False — and the seven reasons why

Blueprinting the supervisor: seven CCI blueprint gotchas

Seven ways the nested-ESXi pod blueprint failed validation before it worked, from ${input} inside flow mappings to an image-sync race. Short, specific, and each one cost me a cycle.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
Two provisioning paths side by side: IaaS engine to vCenter, vs blueprint to supervisor reconciliation

VM Apps vs All Apps: a field comparison of VCF Automation's two provisioning models

VCF Automation 9.1 has two provisioning models, as two kinds of organisation. I ran the same use cases through both, from Windows VMs to nested ESXi. The honest scorecard, and how each case is done.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
The same Cluster manifest applied by kubectl and requested through the catalog — and what the second path adds for free

One VKS cluster, two ways: kubectl vs VCF Automation All Apps

The same VKS cluster built twice: once with kubectl, once as a VCF Automation request. The Cluster object is identical. Everything around it isn’t, and the difference is what you get for free.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
The lab factory: stage 1 nested hosts, stage 2 bringup, day-N items, one wrapper form

One catalog item, one VCF instance: building a lab factory

How an interactive PowerShell script grew into a catalog item that builds complete nested VCF 9.1 instances from one request form. The design rules that made it survivable, and the traps behind them.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
One checkbox on every form: validateOnly. Tick everything, plan the whole stack, change nothing.

validateOnly everywhere: plan mode for infrastructure

Terraform has plan. Kubernetes has –dry-run. Your vRO workflows have nothing, unless you give them a validateOnly input and pass it down. The most valuable checkbox in the lab factory.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
Left: an interactive script's menu prompts. Right: where each one went — inputs, actions, template expressions, subscriptions.

Porting a PowerShell deploy script to a catalog item: the mapping table is the post

A 400-line menu-driven PowerShell script became a cloud template, two vRO actions and two subscriptions. Where each behaviour belongs, four non-obvious decisions, and the ‘yes’ that isn’t ’true’.

16 September 2026 · Updated 1 October 2026 · Adam Stretton
Spec derived from X, validated by the installer, bringup started, task id returned; a second run polls without the catalog's leash

Driving the VCF Installer API from vRO: generate, validate, start, walk away

Stage 2 of the lab factory: a vRO workflow turns an environment number into a VCF 9.1 deployment spec, validates it and starts bringup, because the request dies long before the eight-hour build does.

16 September 2026 · Updated 1 October 2026 · Adam Stretton