VMware by Broadcom · Software · YoctoIT tech page

VCF Automation

Self-service provisioning and lifecycle automation: the private cloud with the public cloud's experience.

FOCUS · INTERNAL SELF-SERVICEBlueprints, catalog and guardrails: the VM in ten minutes, inside the rules
Request the Free Assessment Learn more
YoctoIT material for clients and partners · VMware, vSphere, vSAN, NSX and the other products mentioned are trademarks of Broadcom Inc.
01 · What it is

VCF Automation, made clear.

VCF Automation (formerly Aria Automation) gives the private cloud the cloud experience: a self-service catalog where the teams request VMs, environments and services from approved blueprints — with naming, network, security and leases already right. IT stops doing provisioning by hand and starts designing the rails.

Catalogo
the user chooses, the platform executes: the provisioning ticket disappears
Blueprint
infrastructure as code: the environment defined once, delivered N times
Guardrail
quotas, leases and approvals: freedom inside the rails
VCF Automation
OFFICIAL VMWARE BRANDING · VCF AUTOMATION
CONSOLE REALE · VCF AUTOMATION · FONTE: VMWARE BLOG
REAL CONSOLE · VCF AUTOMATION · SOURCE: VMWARE BLOG
02 · How to use it well

The things that make the difference.

The flow

Devs & projectsthose who request the environment
Catalogo
Blueprints (IaC)
Policies & approvals
storefront · recipe · rules
Orchestration on VCFnetwork, storage and VMs together
Day-2: leases, resize, decommissionthe complete lifecycle
From the request to the environment, without emails

The blueprints that matter

You start from the 5 most requested environments: the value in weeks, the catalog grows later.

Naming and network as standard

Every VM is born with the right name, in the right network, with the right backup: order by design.

Leases and reclamation

The test environments expire and get reclaimed: the swamp of orphan VMs, drained.

Light approvals

The workflow where needed (production), the automatic where not (dev): speed with a head.

03 · In depth

Self-service and IaC for the private cloud

VCF Automation (formerly Aria Automation) delivers self-service: the blueprints (VCF Templates, YAML) describe complete stacks (VMs, NSX networks, storage policies, software), the catalog exposes them with approvals and leases, the projects isolate teams and quotas, the cloud zones abstract the clusters; the Orchestrator extends with workflows (IPAM, CMDB, ticketing); the Terraform support and the APIs make everything code: the test environment is born and dies on its own.

  • Blueprint YAML — the stack declared: VM+network+storage+software in one versioned file
  • Catalogo + approvazioni — governed self-service: the dev asks, the policy decides
  • Lease — the environments with an expiry: the test that switches itself off
  • Project & quote — teams isolated with limits: the cluster doesn't run out by surprise
  • Orchestrator — IPAM, CMDB and tickets hooked up: provisioning integrated with the processes
  • Terraform provider — the private cloud in the corporate IaC workflow
04 · Numbers and lifecycle

The numbers that matter.

min
from the ticket to the VM: self-service provisioning
-90%
the typical environment delivery time
100%
tracked: who asked for what, when, why
0
orphan VMs with leases: the graveyard empties
The private cloud is a service, not iron: catalog, quotas and integrations built by us — IT that delivers in minutes.
05 · Use cases

Where it really pays off.

Dev & test on demand

The environments in minutes, not weeks.

Projects and engagements

The infrastructure per project, tracked and time-boxed.

Standardization

The end of the artisanal VMs.

The private cloud is judged by its self-service: Automation delivers it — we design the rails.