Last updated: September 14, 2026tiCrypt

Provisioning

AdministratorRequires: Admin or Super-Admin

Provisioning enables you to define what researchers can compute on. It covers the infrastructure that virtual machines run on, the catalogue of images and hardware setups researchers choose from, and the Slurm clusters that run batch work.

Provisioning supplies capacity; it does not grant access to what runs on it. An administrator assembles an image and a hardware profile into a hardware setup, and a researcher then builds a VM configuration from it. From that point the running machine belongs to whoever started it, and the administrator who supplied the catalogue cannot reach inside.

◆Why the catalogue is centrally controlled

Researchers choose from hardware setups rather than specifying arbitrary hardware because a hardware setup is where policy is encoded: which image (and therefore which patch level and which pre-installed software) a machine boots from, how much of the team quota it consumes, and whether device passthrough or debug access is permitted. Letting users assemble machines freely would move those decisions outside the audit trail.

Provisioning contains the following functionality

• Images & Hardware: register VM images and ISO images, define hardware profiles, and bundle them into the hardware setups researchers select.
• Infrastructure: register realms, libvirt hosts, storage pools, volumes, and passthrough devices.
• Building VM Images: build and prepare the Linux and Windows images that hardware setups reference.
• Slurm: configure and operate the Slurm clusters, nodes, worker VMs, and accounts that run batch jobs.

The provisioning chain

Each layer depends on the one before it, and a researcher only ever sees the last.

Layer	What it defines	Managed in
Realm	Binds compute, storage, and networking into one logical zone	Realms
Libvirt host	A physical or virtual server that runs VMs	Libvirt Hosts
Storage pool	The backend that encrypted drives are allocated from	Storage Pools
VM image	The operating system and pre-installed software a machine boots from	VM Images
Hardware profile	CPU, memory, and device allocation	Hardware Profiles
Hardware setup	An image paired with a profile — the unit researchers choose	Hardware Setups

Infrastructure

Realms

Logical groupings that bind hosts, storage, and networking.

Libvirt Hosts

Physical or virtual servers that run VMs.

Storage Pools

Storage backends that VM drives are allocated from.

Libvirt Volumes

Individual storage volumes within pools.

Devices

GPU and device passthrough configuration.

Images and hardware

VM Images

Operating system images that VMs boot from.

Hardware Profiles

Templates defining CPU, memory, and device allocation.

Hardware Setups

Bundled configurations pairing an image with a hardware profile.

ISO Images

ISO files available to mount inside VMs.

VM Configurations

Review the saved configurations researchers have built.

Building Images

Create and prepare Linux and Windows images from scratch.

Batch computing

Slurm Configuration

Configure the Slurm controller and partitions.

Nodes

Register and manage Slurm compute nodes.

Worker VMs

Manage the VMs that execute Slurm jobs.

Slurm Accounts

Map tiCrypt users and VMs to Slurm accounts.

Related

• VM Configurations: what researchers build from the hardware setups you publish.
• VM Roles and Permissions: why supplying the infrastructure does not grant access to the machines running on it.
• Governance: the teams and quotas that bound what researchers can provision.
• Monitoring & Audit: observe the instances actually running on this infrastructure.
• Secure HPC with Slurm: how tiCrypt's dual-Slurm architecture works.