Infrastructure automation for OpenHVX. OpenTofu provisions the simulated Windows hosts in the local KVM lab; Ansible and PowerShell configure existing Hyper-V hosts and management VMs; Kubernetes manifests declare the application release. OpenHVX remains the source of truth for tenant resources.
Start with the documentation index.
Run from this repository's root with mise installed:
mise install
mise run bootstrap
mise run testbootstrap installs Python dependencies in .venv/ and Ansible collections in
.ansible/. System prerequisites are described in the relevant runbook.
test performs offline validation; it does not deploy the platform.
| Task | Guide |
|---|---|
| Install the lab and connect to K3s/OpenHVX | Lab setup and access |
| Understand the layout and edit configuration | Repository structure |
| Provision Windows hosts on blank lab disks | Windows installation |
| Deploy or resume OpenHVX | Lab deployment |
| Manage the VyOS VMs | VyOS lifecycle |
| Inspect the network planning contract and results | Network PoC |
| Check implemented capabilities and limits | Current status |
For an existing non-lab host inventory, the shared runner requires an explicit inventory and credentials; it does not load lab secrets:
PLATFORM_INVENTORY=/absolute/path/to/inventory.yml mise run platform:deployThis entry point configures the Windows/Hyper-V baseline. Follow the detailed lab runbook for infrastructure VMs and application deployment.
Keep .lab/, local OpenTofu state/plans and installation media private. Preserve
existing credentials, SSH trust and VM ownership receipts during recovery. See
configuration and state ownership
before modifying these files. No lab acceptance result establishes production HA.