Exclusive Access · Invitation Only

Compute (Early Access)

Stratum Compute runs KVM virtual machines on your Stratum nodes, and connects each one to the node's networking before it starts: the machine's port is locked to its own address, separated from other tenants, and covered by the firewall, address translation and bandwidth rules you already use.

Early access. Compute is in development and is not sold online. It runs on pre-release builds, with a licence we issue after we have talked with you. What these pages describe works in those builds; details can change before release. The limits page lists what is not there yet. To take part, get in touch.

How it fits together

PieceWhat it is
ImageA 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).
Disc imageAn installation disc a machine is installed from, kept in the node's disc library (Installation discs).
Virtual machineCPUs, 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).
InterfaceEither an endpoint on one of your networks, or a public address your provider routes to the server (Networks and public addresses).
TenantThe 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).

Everything is managed on the node itself, with cenvero-str-ctl or the local API — the same tools as the rest of Stratum. The machine's first boot is configured for you (hostname, SSH keys, addresses), so a standard cloud image comes up reachable with nothing typed inside it. A machine installed from a disc is set up by its installer instead.

What a node needs

Requirement
Processor64-bit Intel or AMD (x86_64) with hardware virtualization (Intel VT-x or AMD-V), switched on in the firmware
MemoryAt least 4 GiB
DiskAt least 10 GiB free where the machines' disks will live (50 GiB or more is sensible)
Operating systemDebian 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
LicenceAn early-access licence that includes Compute

Proxmox VE hosts are not supported: another platform already manages virtual machines there.

Installing with Compute

Install with the compute profile (networking and virtual machines) or suite (everything your licence includes). Your account's licence page offers the matching command; the profile can also be added to the URL or set in the environment:

curl -fsSL "https://stratum.cenvero.com/install?key=YOUR_LICENSE_KEY&profile=compute" -o /tmp/cenvero-install.sh
sudo bash /tmp/cenvero-install.sh

Before it changes anything, the installer checks that the server can run virtual machines — processor, memory, free space, operating system — and stops with the reason if it cannot. (When your licence does not include Compute, those checks only warn, and the server is set up for networking only.) It then sets up the virtualization software and a disk pool for the machines, and finishes by checking that the node reports Compute as ready.

SettingEffect
CENVERO_PROFILE=compute or suiteThe same as &profile= in the URL
CENVERO_VM_POOL=/srv/vmKeep 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
CENVERO_ALLOW_EMULATION=1Go ahead on a server without usable hardware virtualization. Machines then run in software emulation, many times slower — for trying things out, not for customers
CENVERO_API_TOKEN=offLeave the local API — and the 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

A server that already runs another panel's virtual machines is supported. Stratum only ever touches machines it created; it never starts, stops, changes or deletes anything else. The installer notices the other machines, installs no virtualization software on its own if some is missing (it tells you what to install), and leaves the settings those machines share — whether guests start and stop with the server, and the built-in NAT network — exactly as they are. It prints the setting to use if you want them applied anyway.

To add Compute to a node that already runs Stratum, run the installer again with CENVERO_REINSTALL=1 and the profile.

Storage pools at install

The compute and suite profiles can also check or set up block pools on a new server. A block pool is described on Storage pools, which also says what the host needs first. Each setting is optional:

SettingEffect
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)
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
CENVERO_STORAGE_DEVICE=/dev/...The device a missing volume group or ZFS pool is created on. Nothing else is put on it
CENVERO_STORAGE_CREATE=yesLets 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
CENVERO_STORAGE_WIPE=yesLets 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
  • Verify only, by default: without the create setting, the installer checks each pool you name and reports what it finds. It creates nothing.
  • Creating needs both CENVERO_STORAGE_DEVICE and CENVERO_STORAGE_CREATE=yes. One run creates one kind: naming both a thin-provisioned pool and a ZFS pool with a device and the create setting is refused, and nothing is changed.
  • Wiping: a device that carries a signature is not used unless CENVERO_STORAGE_WIPE=yes is set as well. A signature is a filesystem or a partition table; with the wipe setting, those are removed before the device is used. WIPE covers ordinary signatures only. A device that a ZFS pool, a RAID array, an encrypted volume or a volume manager's physical volume claims is refused even with the setting. So is a disk with a partition that one of them claims.
  • A device is used only when nothing mounts or uses it, it belongs to no volume group, and it is not the disk the system starts from. Otherwise the installer leaves it alone and says why.
  • On a server that already runs another panel's virtual machines, the installer installs no packages for these pools unless CENVERO_LIBVIRT_TAKEOVER=1 is set. It says which packages to install instead.
  • Packages: a thin-provisioned pool needs the lvm2 package, and a ZFS pool needs zfsutils-linux, with zfs-dkms on Debian, which builds the ZFS module. On Debian the module comes from the contrib component, which must be enabled first. If the ZFS module does not load, the ZFS pool is left out and the install carries on.
  • A setting the installer cannot use is reported as a warning, that pool is skipped, and the install carries on.
  • The default fabric profile does not set up storage. These settings also need a licence that includes Compute or Storage.

Checking that it is ready

cenvero-str-ctl compute status
FieldMeaning
stateactive — 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
reasonWhy Compute is not active, in plain words, with what to do
hypervisor.virtkvm (hardware virtualization) or emulated (software emulation)
poolWhere the disks live, and its free and total space
countsMachines, running machines, images
warningsFor example software emulation, or a pool over 85 % or 95 % full

The licence and your machines

  • What a Compute licence includes. Virtual machines, with volumes, snapshots and backups, and the networking they need: private networks, anti-spoofing, the firewall, address translation, DHCP, DNS and bandwidth shaping. BGP, load balancing and overlays come with Fabric or the Suite (Licensing).
  • Speed. Each plan has a speed ceiling per node, the same as Fabric's tiers: Core 10 Gbps, Cloud 25 Gbps, Enterprise 100 Gbps.
  • An early-access licence issued before volumes, snapshots and backups came with Compute may not include them; the web console then says Storage is not in the plan. Ask us to reissue it.
  • Creating, starting, stopping and deleting machines and images need a licence that includes Compute and is not frozen.
  • Looking — compute status, vm list, vm show, image list — and opening a machine's console always work, whatever the licence says.
  • Running machines keep running when a licence expires or is frozen, like the rest of Stratum: changes are frozen, workloads are not.

Next

↓ This page as JSON ↓ All documentation as JSON