Calabi Documentation

Calabi

Single-host disconnected OpenShift on nested KVM, with intent-first docs for architecture, orchestration, auth, and recovery.

PREREQUISITESAUTOMATION FLOWMANUAL PROCESSPORTABILITY / GAPSHOST SIZINGAWS DOCS MAP
Experimental On-Prem Path. Use these pages only for the divergent early host and bastion-staging steps, then return to the main Calabi docs once the normal flow resumes.

On-Prem Documentation

Warning

This on-prem target is experimental. Treat the docs and playbooks in this subtree as an emerging alternate installation path, not yet the same confidence level as the validated AWS-target flow.

Use these pages when you are building Calabi on an on-prem virt-01-like host.

What you provide:

  • you provide a RHEL hypervisor host
  • you provide an LVM2 volume group for guest storage
  • the on-prem subtree creates the guest logical volumes and publishes the same /dev/ebs/* compatibility paths the stock guest and cluster roles already expect
  • you define both:
    • how the operator workstation reaches the hypervisor
    • how bastion reaches that same hypervisor on the lab network
  • once that host contract is satisfied, the stock support-service, cluster, and day-2 orchestration is reused

These pages only cover the on-prem differences. After host bootstrap and bastion staging, return to AWS DOCS MAP.

Start Here

  1. PREREQUISITES
  2. AUTOMATION FLOW
  3. MANUAL PROCESS
  4. HOST SIZING
  5. PORTABILITY / GAPS

What Is Different On-Prem

  • there is no AWS tenant or host stack
  • there is no live AWS volume discovery
  • the guest storage contract comes from the LVM volume group you provide
  • you must validate CPU, RAM, NUMA, and storage headroom against the current guest footprint before bootstrap

Where The Normal Docs Take Over Again

For the manual path, the on-prem-specific work ends once the host is prepared, guest storage exists, and bastion staging is complete. Then continue in the stock runbook at:

For automation, the on-prem entrypoints are:

Continue