VirtEngine

Module reference · Marketplace & workloads

x/hpc — HPC

The HPC job marketplace for scheduler-backed supercomputing clusters.

What it does

Inside x/hpc

The hpc module extends the marketplace to batch supercomputing. Instead of leasing long-running services, tenants submit HPC jobs — batch workloads with resource, walltime, and partition requirements — that execute on providers' existing cluster schedulers: SLURM, MOAB, or Open OnDemand.

On the provider side, the daemon's HPC integration polls on-chain jobs, dispatches them through native scheduler adapters (munge or JWT auth for SLURM, per-partition configuration), tracks lifecycle with configurable concurrency limits and timeouts, and recovers state crash-safely. Job events, security events, and usage feed a dedicated audit log, and usage batches flow into the same settlement pipeline as cloud workloads.

Why it exists

The design rationale

University and national-lab clusters run some of the world's most valuable capacity at partial utilization, but their operating model — batch schedulers, allocations, walltime — doesn't map onto container leases. A dedicated HPC module lets that capacity join the marketplace without re-platforming the cluster.

Interactions

How it connects to the rest of the chain

No module stands alone — these are the protocol surfaces this module depends on or serves.

Key concepts

Terms that matter here

HPC job
A batch workload with resource, walltime, and partition requirements, executed via a cluster scheduler.
Scheduler adapter
The daemon component that speaks natively to SLURM, MOAB, or Open OnDemand.
Partition
A scheduler-level subdivision of a cluster that can be exposed to the marketplace with its own configuration.

Keep exploring

More from marketplace & workloads