Start Here
Orientation guide for the AORXI homelab documentation: what this site covers, how it is organized, and where to go next.
AORXI is a two-site private cloud built on Proxmox, OPNsense, WireGuard, 10 Gb switching, and planned Kubernetes. Site A is moving to an OPNsense-routed, three-switch UniFi L2 fabric; Site B keeps its Netgear L2 core. Approved target state is labeled separately from observed live state.
What This Site Covers
The docs cover every layer of the homelab: physical hardware and cabling, VLAN and IP design, OPNsense and WireGuard configuration, Proxmox cluster setup, Ceph storage at Site B, ZFS and Proxmox Backup Server (PBS) at Site A, DNS, and the Kubernetes/OpenShift plans. Reference pages collect all IP tables, port maps, and decisions in one place.
How to Navigate
| Page | What you will find |
|---|---|
| How It Fits Together | Bird's-eye view of both sites: topology, inter-site link, and how each layer connects |
| Design Principles | The hard architecture rules that cannot be violated and the reasoning behind them |
| Glossary | Every hostname pattern, product name, VLAN name, and acronym used on this site |
Main Documentation Sections
- Architecture covers the two-site model, site roles, and topology diagrams.
- Networking covers IP addressing, VLANs, WireGuard, DNS, and the addressing convention.
- Hardware lists per-site inventory, NIC allocation, RAM, and storage.
- Switching maps Site A and Site B ports, switch roles, and operating rules.
- OPNsense contains the migration phases and UniFi handoff.
- Compute & storage covers Proxmox clusters, ZFS, Ceph, and PBS.
- Kubernetes tracks cluster planning and machine-network allocation.
- Platform services covers DNS VMs, certificates, Kafka, and container infrastructure.
- Operations contains IPMI/KVM procedures, build phases, and current build state.
- Reference collects IP tables, port tables, the hardware bill of materials, and the decision log.
AORXI Homelab Documentation
Architecture decisions, IP plans, hardware inventory, runbooks, and interactive tools for the two-site AORXI private cloud.
How It All Fits Together
Current state, target topology, ownership boundaries, control services, storage, and build sequence for the two-site AORXI private cloud.