# Build the catalog

Offer your tenants what they can deploy, and at what size.

## One item, one template per site

A catalog **item** is what the tenant sees: "Debian 12", "Windows Server 2022". On each site, it relies on a template the platform already holds. The same item can therefore serve on several sites.

## The steps

1. Open **Cloud services › Offers**, **Templates and sizes** tab. Under **New catalog item**, fill in the name and description in English and French, the system family and name, the minimums and the guest customization. Click **Create as draft**.
2. On the item's page, attach a template on each site with **Place**. The screen says why a template is not eligible.
3. Click **Publish**.
4. Offer the item to the VDCs you want with **Offer**, from its page or from the VDC's.
5. On the same page, create the **Size templates**: vCPU, memory and disk. A disk left empty is chosen at deployment, from the template's minimum.

## A good template

- **On shared storage**: Proxmox VE only clones a template to another node if its disks are shared. A template on local storage only deploys on its own node.
- **With the guest agent**: without it, the machine's address is never read back.
- **With a graphical display**: the portal's console is graphical, and a serial-only template leaves it blank. The screen flags it.

## Storage classes

A class, such as "Gold" or "Silver", is the common vocabulary of your VDCs' tiers and of your billing. Create it in the **Storage classes** tab, next to **Templates and sizes**, with a code that will never change: it is the "disk per class" dimension of your rate plans. Then tick, site by site, the storages that carry it. The VDC wizard then copies the class into each tier.

## ISO images and cloud-init

- **ISO images** are placed on an ISO storage of the site, declared at bootstrap.
- **Cloud-init snippets** (packages, NTP, certificate authorities) are written in **Settings › Infrastructure actions › Deployment presets**. Attach one to an item so it always applies, or offer it in a VDC: the tenant picks from a closed list, and never writes cloud-init.

### A published item does not show for the tenant

It must be placed on the VDC's site **and** offered in that VDC. An item with no template on that site is flagged on the VDC's page.

### The tenant cannot choose their size

The **Catalog sizes only** box is ticked on their VDC: they go through your size templates. Untick it under **Edit limits** to allow a custom size.
