Self-service platform in VCF for provisioning VM, Kubernetes and AI workloads. Providers manage regions and tenants in one portal, while tenants handle projects and consumption in theirs.
Also called formerly VMware Aria Automation, VMware Aria Automation.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains VCF Automation in context, with comparison tables and the common traps.
Terms in this definition
- VMware Cloud Foundation
Broadcom's platform for private cloud. It unifies management of NSX, vSAN, vSphere, VCF Automation and VCF Operations as one fleet; VVF, by contrast, lacks automation and cloud management.
- MANAGE
A Unity Catalog privilege allowing a principal to grant and revoke access on an object, hand over its ownership and drop it, all without being the owner. It gives no data access by itself and is not part of
ALL PRIVILEGES. - Consumption
Serverless, event-driven Azure Functions hosting plan charged per execution; runs are capped at 10 minutes and VNet integration isn't available.
Related terms
- Active Standby
An NSX gateway HA mode where one Edge node handles traffic while a second waits to take over. Stateful services such as NAT, VPN, load balancing and the stateful firewall depend on it, and VCF Automation 9.0 expects its Tier-0 to be set up this way.
- Approval policy
A VCF Automation policy under which nominated approvers must sign off catalog requests or day 2 actions before anything is provisioned. Approvers respond from their Inbox, and the policy defines what happens if a request expires.
- Classic Tenant Creation
Feature flag in VCF Automation that a provider has to switch on before creating VM Apps organizations, the classic tenancy model, rather than All Apps ones.
- Cloud account
An endpoint plus credentials, for example for vCenter, NSX, VCF, AWS, Azure or Google Cloud, that VCF Operations and VCF Automation (VM Apps) use to gather data or provision resources.
- Cloud zone
VM Apps construct in VCF Automation: a slice of a cloud account's compute, labelled with capability tags and governed by placement rules, that given projects may use as a deployment target.
- Cluster Node IP Pool
Block of no fewer than four IP addresses given to VCF Automation at deployment for its cluster nodes. The extra addresses are consumed during scale-out and rolling upgrades.
- Content library
Repository in vCenter holding items such as templates, ISOs and OVF/OVA packages; one vCenter publishes it and others subscribe. VCF Automation shares images this way as well.
- Day 2 action
Action taken on a resource already deployed from the catalog, such as powering off, resizing or taking a snapshot. VCF Automation Day 2 Action policies decide who may run which actions.