VCF Demystified, Part 4: VCF Automation - From Requests to Governed Services
How VCF Automation turns infrastructure capability into repeatable, governed self-service: catalogs, templates, projects, policies, and the operational guardrails behind them.
VCF Automation is the consumption layer of VCF 9. It takes the capabilities provided by compute, storage, networking, and identity teams and exposes them as repeatable services with policy around them.
Automation is not a faster request form
The weak version of automation creates VMs more quickly. The useful version defines what a valid VM, application, or environment looks like, who may request it, where it may be placed, what it costs, and how it is retired.
Catalog item -> template or blueprint -> policy and placement -> provisioned service
^ |
+--------------- approvals, ownership, cost --------+The concepts that matter
| Concept | What it means |
|---|---|
| Catalog | The approved services users can request |
| Template or blueprint | The desired shape of a service |
| Project | A boundary for users, quotas, placement, and ownership |
| Policy | The rules for lease, approval, naming, size, or governance |
| Integration | The connection to vCenter, NSX, IPAM, identity, or other systems |
The component does not replace good platform design. It makes that design visible and repeatable. If the network, storage policy, images, and ownership model are undefined, an automation catalog simply produces inconsistent infrastructure faster.
A healthy automation mindset
Start with a small number of well-governed services: perhaps a standard Linux VM, a standard Windows VM, and a three-tier application pattern. Each should use known images, known networks, storage classes, lifecycle rules, and an owning project. Expand only after the support model is clear.
The success measure is not the number of catalog items. It is the percentage of common requests delivered without manual exception work.
How it fits VCF
VCF Automation consumes the controlled platform that VCF Operations manages. Operations supplies the context around capacity, cost, health, and lifecycle; automation supplies the governed path by which users consume that capacity. Together, they turn infrastructure components into a private-cloud service.