Ask for a VM. The rules answer.

Create a new virtual machine

Set the VM size within the caps configured for this template.

vCPU

2 c16 c

Memory

4 GB64 GB

Disk

60 GB250 GB

Checks on the request

memberadmin

try a name · windows-server-2025

Template allowed in this project: passed3 templates allowed · windows-server-2025
Size between the template minimum and the project's cap: passed2–16 vCPU · 4–64 GB · 60–250 GB
Fits the project quota: passed58/64 vCPU · 208/256 GB · 1770/2000 GB
Name follows web-prod-<2100–2199>: passedprefix and number match the template's rule
VMID 2104 from the name: passedfree on the cluster, not recently freed

Will be created as

VMID 2104

A simulation in your browser — nothing is created.

Teams pick what their project allows — every rule is checked before anything exists.

Try a name, or drag a size past the quota.

Open the portal

Admins decide once. The dialog follows.

Fix a size or a network on the template, and that step disappears from the dialog.

Template · Defaults

rocky-9Rocky Linux 9

Rules applied — the create-VM dialog auto-fills and locks these for non-admins.

Enable rules

Naming scheme (forced)

Name is prefix + number within the range. Forced for users; admins may override but stay within the range.

Prefix

Range from

Range to

e.g. ci-runner-500 … up to ci-runner-599

Forced VM storage (optional)

Leave on “project default” to use the project-wide VM storage.

Auto resources(skips the resources step)

vCPU (max 8)

Memory GB (max 32)

Disk GB (max 200)

Auto network / VLAN(skips the network step)

Network

VLAN

Domain join override(blank = use the project's Deployment defaults)

Domain (FQDN)

OU (DN)

Deployment workflow

What new VMs from this template go through (Deployments page). Built-in = clone, boot, backup job, hostname, domain join, local admins, verify, HA.

Backup job prefix

After clone, the VM is added to the backup job whose comment starts with this prefix and that targets the VM's node (one job per PVE). Leave blank to skip.

High availability(auto-joins the HA rule for its deployment node, after deploy finishes)

5steps in the dialogout of 7

Create a new virtual machine

This template enforces a naming scheme — the name is assigned automatically.

Name

Range: ci-runner-500 – ci-runner-599

One click. Eight steps. Three places.

Portal

pre-stepChecksTemplate, size, quota, name, VMID.

Proxmox

step 01Cloning templateFull clone as VMID 2104.

step 02Booting VMWaits for the agent.

step 03Assigning backup jobThe job for its node.

step 08Adding to HALast, so HA can't fight the reboots.

runningweb-prod-2104, owned, backed up, in HA.

Agent in the guest

step 04Setting hostnameweb-prod-2104

step 05Joining domaincorp.example, across the reboot.

step 06Configuring local adminsThe owner becomes local admin.

step 07FinalizingCleanup, final reboot.

Nobody picks a node. The cluster does.

The least-loaded enabled, online node wins — CPU counts 60 %, memory 40 %.

Hosts

Host	Type	Capacity	CPU	Memory	Version	In project
pve-01	pve	64c · 512 GB	62%	71%	9.0.6	enabled
pve-02	pve	64c · 512 GB	38%	55%	9.0.6	enabled
pve-03	pve	64c · 512 GB	24%	33%	9.0.6	enabled
pve-04	pve	32c · 256 GB	9%	18%	9.0.6	disabled

Simulate load · click a status for maintenance

pve-01

62%

71%

pve-02

38%

55%

pve-03

24%

33%

pve-04 is not enabled for this project.

web-prod-2104 lands onpve-02

Target node

pve-02

Least loaded of 2 eligible nodes — CPU 38% / RAM 55%.

Backup job

pve-01→nightly - pve-01

pve-02→nightly - pve-02

pve-03→nightly - pve-03

pve-04→nightly - pve-04

HA rule

pve-01→prefer-pve-01

pve-02→prefer-pve-02

pve-03→prefer-pve-03

pve-04→prefer-pve-04

A no, before anything exists.

Each refusal, word for word, where it appears.

01Over the quotaREST API
POST /api/v1/projects/web-platform/vms400 Bad Request
```
{ "error": "exceeds project vCPU quota (68 would be used of 64)" }
```

02Name off the ruleREST API

POST /api/v1/projects/web-platform/vms400 Bad Request

{ "error": "name must match the template's provisioning rule: \"web-prod-<n>\" with n between 2100 and 2199" }

03VMID takenNew VM dialog
Can’t use this nameVMID 2101 from the name "web-prod-2101" is already in use by "web-prod-2101" on the cluster
04VMID recently freedNew VM dialog
Can’t use this nameVMID 2103 from the name "web-prod-2103" was freed recently and is blocked from reuse (VMID blacklist)
05Template not allowedREST API
POST /api/v1/projects/web-platform/vms403 Forbidden
```
{ "error": "template 'pve-a:9003' is not allowed for this project" }
```
06Range used upNew VM dialog
Can’t use this nameVMID 2200 from the name "web-prod-2200" is outside the template's range 2100–2199
07VMID taken sinceat clone time
Failed: Cloning template1s
Infrastructure3 tasks(1 failed, 2 pending)1s
Proxmox3
Cloning template4 vCPU · 8 GB · 80 GB1s
Cloning templatePOST /nodes/{node}/qemu/{template}/cloneprovisioning: VMID 2104 from the name "web-prod-2104" is already in use by "restore-test" on the cluster — rename the VM or free that VMID1s
Booting VM
Assigning backup job

Bring one template, one range, one quota.

In a demo we set them up on your own templates and send the first request through.

See pricing