{
    "product": "Cenvero Stratum",
    "generated_at": "2026-11-16T13:19:22+00:00",
    "format": "cenvero-docs-v1",
    "document_count": 1,
    "documents": [
        {
            "slug": "compute/overview",
            "title": "Compute (Early Access)",
            "category": "Compute",
            "url": "https://stratum.cenvero.com/docs/compute/overview",
            "headings": [
                {
                    "level": 1,
                    "text": "Compute (Early Access)"
                },
                {
                    "level": 2,
                    "text": "How it fits together"
                },
                {
                    "level": 2,
                    "text": "What a node needs"
                },
                {
                    "level": 2,
                    "text": "Installing with Compute"
                },
                {
                    "level": 3,
                    "text": "Storage pools at install"
                },
                {
                    "level": 2,
                    "text": "Checking that it is ready"
                },
                {
                    "level": 2,
                    "text": "The licence and your machines"
                },
                {
                    "level": 2,
                    "text": "Next"
                }
            ],
            "word_count": 1753,
            "markdown": "# Compute (Early Access)\n\nStratum Compute runs KVM virtual machines on your Stratum nodes, and connects\neach one to the node's networking before it starts: the machine's port is\nlocked to its own address, separated from other tenants, and covered by the\nfirewall, address translation and bandwidth rules you already use.\n\n> **Early access.** Compute is in development and is not sold online. It runs on\n> pre-release builds, with a licence we issue after we have talked with you.\n> What these pages describe works in those builds; details can change before\n> release. The [limits](/docs/compute/limits) page lists what is not there yet.\n> To take part, [get in touch](/compute).\n\n## How it fits together\n\n| Piece | What it is |\n|---|---|\n| **Image** | A base disk a machine starts from — a Linux cloud image you register once on a node, or once in a cluster's image library ([Images](/docs/compute/images)). |\n| **Disc image** | An installation disc a machine is installed from, kept in the node's disc library ([Installation discs](/docs/compute/images#installation-discs)). |\n| **Virtual machine** | CPUs, memory and a disk made from an image, or a blank disk installed from a disc, plus one to four network interfaces ([Creating virtual machines](/docs/compute/virtual-machines)). |\n| **Interface** | Either an endpoint on one of your [networks](/docs/networking/overview), or a [public address](/docs/networking/public-addresses) your provider routes to the server ([Networks and public addresses](/docs/compute/networking)). |\n| **Tenant** | The customer a machine belongs to. A tenant's machines attach only to that tenant's networks, and are kept apart from every other tenant's ([Tenants](/docs/tenants)). |\n\nEverything is managed on the node itself, with `cenvero-str-ctl` or the\n[local API](/docs/api) — the same tools as the rest of Stratum. The machine's\nfirst boot is configured for you (hostname, SSH keys, addresses), so a standard\ncloud image comes up reachable with nothing typed inside it. A machine installed\nfrom a disc is set up by its installer instead.\n\n## What a node needs\n\n| | Requirement |\n|---|---|\n| **Processor** | 64-bit Intel or AMD (x86_64) with hardware virtualization (Intel VT-x or AMD-V), switched on in the firmware |\n| **Memory** | At least 4 GiB |\n| **Disk** | At least 10 GiB free where the machines' disks will live (50 GiB or more is sensible) |\n| **Operating system** | Debian 12 or newer, or Ubuntu 22.04 or newer (early access is tested on Debian 13). RHEL-family hosts are not validated for Compute yet |\n| **Licence** | An early-access licence that includes Compute |\n\nProxmox VE hosts are not supported: another platform already manages virtual\nmachines there.\n\n## Installing with Compute\n\nInstall with the `compute` profile (networking and virtual machines) or `suite`\n(everything your licence includes). Your account's licence page offers the\nmatching command; the profile can also be added to the URL or set in the\nenvironment:\n\n```bash\ncurl -fsSL \"https://stratum.cenvero.com/install?key=YOUR_LICENSE_KEY&profile=compute\" -o /tmp/cenvero-install.sh\nsudo bash /tmp/cenvero-install.sh\n```\n\nBefore it changes anything, the installer checks that the server can run\nvirtual machines — processor, memory, free space, operating system — and stops\nwith the reason if it cannot. (When your licence does not include Compute, those\nchecks only warn, and the server is set up for networking only.) It then sets up\nthe virtualization software and a disk pool for the machines, and finishes by\nchecking that the node reports Compute as ready.\n\n| Setting | Effect |\n|---|---|\n| `CENVERO_PROFILE=compute` or `suite` | The same as `&profile=` in the URL |\n| `CENVERO_VM_POOL=/srv/vm` | Keep the machines' disks on another disk. The directory must exist (mount the disk there first); the disks go in a `cenvero-str-vm` folder inside it |\n| `CENVERO_ALLOW_EMULATION=1` | Go ahead on a server without usable hardware virtualization. Machines then run in software emulation, many times slower — for trying things out, not for customers |\n| `CENVERO_API_TOKEN=off` | Leave the local API — and the [web console](/docs/compute/web-console) — off. By default the `compute` and `suite` profiles turn it on with a generated token, stored root-only in `/etc/cenvero-str/api-token`, and the installer prints the console's address at the end |\n\n**A server that already runs another panel's virtual machines** is supported.\nStratum only ever touches machines it created; it never starts, stops, changes\nor deletes anything else. The installer notices the other machines, installs no\nvirtualization software on its own if some is missing (it tells you what to\ninstall), and leaves the settings those machines share — whether guests start\nand stop with the server, and the built-in NAT network — exactly as they are. It\nprints the setting to use if you want them applied anyway.\n\nTo add Compute to a node that already runs Stratum, run the installer again with\n`CENVERO_REINSTALL=1` and the profile.\n\n### Storage pools at install\n\nThe `compute` and `suite` profiles can also check or set up block pools on a new server.\nA block pool is described on [Storage pools](/docs/compute/storage-pools), which also says\nwhat the host needs first. Each setting is optional:\n\n| Setting | Effect |\n|---|---|\n| `CENVERO_STORAGE_THIN=<group>/<pool>` | A thin-provisioned pool that already exists in a volume group. The installer checks it and, once the node is running, registers it as a pool called `thin-pool` (when a pool of that name already exists at another location, the name is made from the group and pool, such as `thin-vg1-pool`) |\n| `CENVERO_STORAGE_ZFS=<pool>` or `<pool>/<dataset>` | A ZFS pool, or a dataset in one, that already exists. The installer checks it and, once the node is running, registers it as a pool called `zfs-pool` (or a name made from the pool and dataset, such as `zfs-tank2-vm`, when that name is taken). To keep the host's volume manager off ZFS volumes, the installer writes a filter into that manager's local settings file. If the file carries the installer's marker, each run rewrites it, so a line you add to it is lost; a file the installer did not write is left alone |\n| `CENVERO_STORAGE_DEVICE=/dev/...` | The device a missing volume group or ZFS pool is created on. Nothing else is put on it |\n| `CENVERO_STORAGE_CREATE=yes` | Lets the installer create the missing group or pool on `CENVERO_STORAGE_DEVICE`. It never adds a pool to a group that exists, and never adds a dataset to a pool that exists |\n| `CENVERO_STORAGE_WIPE=yes` | Lets the installer remove the ordinary signatures on `CENVERO_STORAGE_DEVICE` (a filesystem or a partition table) before it uses the device. It never removes a ZFS pool member, a RAID array member, an encrypted volume or a volume manager's physical volume: the installer refuses such a device whether or not this setting is given |\n\n- **Verify only, by default:** without the create setting, the installer checks each pool you\n  name and reports what it finds. It creates nothing.\n- Creating needs both `CENVERO_STORAGE_DEVICE` and `CENVERO_STORAGE_CREATE=yes`. One run creates\n  one kind: naming both a thin-provisioned pool and a ZFS pool with a device and the create\n  setting is refused, and nothing is changed.\n- Wiping: a device that carries a signature is not used unless `CENVERO_STORAGE_WIPE=yes` is set\n  as well. A signature is a filesystem or a partition table; with the wipe setting, those are\n  removed before the device is used. WIPE covers ordinary signatures only. A device that a ZFS\n  pool, a RAID array, an encrypted volume or a volume manager's physical volume claims is refused even with\n  the setting. So is a disk with a partition that one of them claims.\n- A device is used only when nothing mounts or uses it, it belongs to no volume group, and it is\n  not the disk the system starts from. Otherwise the installer leaves it alone and says why.\n- On a server that already runs another panel's virtual machines, the installer installs no\n  packages for these pools unless `CENVERO_LIBVIRT_TAKEOVER=1` is set. It says which packages to\n  install instead.\n- Packages: a thin-provisioned pool needs the `lvm2` package, and a ZFS pool needs\n  `zfsutils-linux`, with `zfs-dkms` on Debian, which builds the ZFS module. On Debian the module\n  comes from the contrib component, which must be enabled first. If the ZFS module does not load,\n  the ZFS pool is left out and the install carries on.\n- A setting the installer cannot use is reported as a warning, that pool is skipped, and the\n  install carries on.\n- The default `fabric` profile does not set up storage. These settings also need a licence that\n  includes Compute or Storage.\n\n## Checking that it is ready\n\n```bash\ncenvero-str-ctl compute status\n```\n\n| Field | Meaning |\n|---|---|\n| `state` | `active` — ready; `not_licensed` — this node's licence has no Compute yet (it switches on by itself when the licence does); `connecting` — starting up; `unavailable` — see `reason` |\n| `reason` | Why Compute is not active, in plain words, with what to do |\n| `hypervisor.virt` | `kvm` (hardware virtualization) or `emulated` (software emulation) |\n| `pool` | Where the disks live, and its free and total space |\n| `counts` | Machines, running machines, images |\n| `warnings` | For example software emulation, or a pool over 85 % or 95 % full |\n\n## The licence and your machines\n\n- **What a Compute licence includes.** Virtual machines, with **volumes,\n  snapshots and backups**, and the networking they need: private networks,\n  anti-spoofing, the firewall, address translation, DHCP, DNS and bandwidth\n  shaping. BGP, load balancing and overlays come with Fabric or the Suite\n  ([Licensing](/docs/licensing)).\n- **Speed.** Each plan has a speed ceiling per node, the same as Fabric's\n  tiers: Core 10 Gbps, Cloud 25 Gbps, Enterprise 100 Gbps.\n- **An early-access licence issued before volumes, snapshots and backups came\n  with Compute** may not include them; the web console then says Storage is not\n  in the plan. Ask us to reissue it.\n- **Creating, starting, stopping and deleting** machines and images need a\n  licence that includes Compute and is not frozen.\n- **Looking** — `compute status`, `vm list`, `vm show`, `image list` — and\n  opening a machine's **console** always work, whatever the licence says.\n- **Running machines keep running** when a licence expires or is frozen, like\n  the rest of Stratum: changes are frozen, workloads are not.\n\n## Next\n\n- [Images](/docs/compute/images) — register the image machines start from.\n- [Creating virtual machines](/docs/compute/virtual-machines) — sizes, first boot, tenants.\n- [Firmware, resizing, interfaces and the guest agent](/docs/compute/machine-settings) — UEFI and TPM, changing a machine, the guest agent.\n- [Networks and public addresses](/docs/compute/networking) — how a machine is connected.\n- [Consoles](/docs/compute/consoles) — the serial and graphical console.\n- [Lifecycle and restarts](/docs/compute/lifecycle) — what happens on stop, crash, reboot and update.\n- [Current limits](/docs/compute/limits) — what early access does not do yet.\n"
        }
    ]
}