Automation

Org Builder's Home page, four ways in, with the Install or upgrade tile highlighted and its note: Install, upgrade or uninstall an organization from packages

Install, upgrade, uninstall: a whole lab catalog with Org Builder

The nested-lab catalog as three Org Builder packages that install, upgrade and uninstall a VCF Automation organization. How made and found keep an uninstall honest, and what two live runs proved.

Org Builder's Home page, four ways in, with the Create a package tile highlighted and its note: Create a package from an organization

Bring your own image: a step done by hand in Org Builder

Org Builder’s second worked example, the bring-your-own-image case: a team catalog that boots from an image, packaged without the image file, edited to ask for each site’s own copy at the right moment, and installed in production. Plus what VCF Automation’s own OVA export does with the same blueprint.

Org Builder's Home page, four ways in, with the Move an organization tile highlighted and its note: Package one organization and install it into another

Same blueprints, different values: dev to prod with Org Builder

Org Builder’s first worked example: two blueprints and the property groups they read, exported from a development organization and imported into production with production’s own values.

Org Builder's Home page: four ways in, each a tile of its own - Make a site file, Create a package, Install or upgrade, and Move an organization - with links below for the offline site wizard, importing a bundle and editing a package, beside the Install and Package and move steps in the side menu

Introducing Org Builder

Why we built Org Builder, our tool for VCF Automation organizations: catalog services built in one organization have to reach others, and rebuilding them by hand or scripting every API call doesn’t scale. Packages, site files and versioned releases, in brief.

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.

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.