Commit Graph

8 Commits

Author SHA1 Message Date
josh 994152bedf Use sanhook to expose ISO as block device during kernel/initrd boot
build-and-push / test (push) Successful in 35s
build-and-push / build-and-push (push) Successful in 1m12s
The CPIO-embedded initrd approach failed (too large for iPXE memory).
Instead, use iPXE's sanhook to connect the ISO as a SAN block device
before booting with kernel/initrd. The installer finds the ISO on the
SAN device while we retain control over kernel parameters.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-05-14 14:09:12 -04:00
josh e2dd78d8f9 Embed ISO in initrd for PXE boot with loop-mount wrapper
build-and-push / test (push) Successful in 35s
build-and-push / build-and-push (push) Successful in 1m8s
Instead of sanboot (which can't pass kernel params for automation),
switch back to kernel/initrd boot. The ISO is embedded in the initrd
as a CPIO append. A pxe-init wrapper script loop-mounts the ISO
before handing off to the original init, so the installer finds it
as a block device. Uses rdinit=/pxe-init kernel parameter.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-05-14 12:11:18 -04:00
josh a8f8801a90 Switch to sanboot for PXE ISO delivery
build-and-push / test (push) Successful in 36s
build-and-push / build-and-push (push) Successful in 1m7s
Proxmox has no kernel parameter for HTTP ISO fetch. Instead, use
iPXE's sanboot command to present the ISO as a virtual CD over HTTP.
The installer finds it as a block device and boots normally.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-05-14 11:23:48 -04:00
josh 81abb94806 Serve full ISO for PXE boot via proxmox-iso-url kernel param
build-and-push / test (push) Successful in 34s
build-and-push / build-and-push (push) Successful in 1m11s
The Proxmox installer needs the full ISO to access packages and
installer data. Previously the ISO was deleted after extracting
kernel+initrd. Now we keep it as original.iso and serve it via HTTP.
The iPXE script passes proxmox-iso-url=<url> so the installer
fetches the ISO over the network instead of scanning block devices.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-05-14 11:11:45 -04:00
josh 44c358a89b Fix initrd loading with explicit iPXE name binding
build-and-push / test (push) Successful in 34s
build-and-push / build-and-push (push) Successful in 1m14s
iPXE needs --name on the initrd command and initrd=<name> on the
kernel line to properly pass the initrd to the kernel. Without this,
the kernel never receives the initrd, causing VFS mount failure.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-05-14 11:03:03 -04:00
josh 846b6847a5 Fix kernel panic by adding ramdisk_size to iPXE kernel params
build-and-push / test (push) Successful in 35s
build-and-push / build-and-push (push) Successful in 1m12s
The Proxmox initrd is too large for the default ramdisk allocation,
causing VFS to fail mounting root. Add ramdisk_size=16777216 (16GB)
along with rw, quiet, and splash=verbose for proper installer boot.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-05-14 10:55:34 -04:00
josh 4774600040 Add boot image management with ISO extraction and serving
build-and-push / test (push) Successful in 34s
build-and-push / build-and-push (push) Successful in 1m7s
Upload Proxmox ISOs via API or dashboard UI, extract kernel+initrd
using pure-Go iso9660 library, store on disk, and serve over HTTP
for PXE booting. Dynamic kernel/initrd filenames per image replace
the previous hardcoded paths.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-05-09 21:26:31 -04:00
josh bda568b25c Initial implementation: host lifecycle + PXE + admin dashboard
Go service for Proxmox homelab cluster provisioning. Handles PXE boot,
Proxmox autoinstall (answer file generation), cluster join via SSH,
and Infrastructure API registration.

- Host state machine (registered → pxe_ready → installing → ready)
- dnsmasq supervisor with MAC-based allowlist
- iPXE script and Proxmox answer file generation
- First-boot phone-home → cluster join → infra registration
- Operation locking with expiry (409 on conflict)
- SSE event hub for real-time dashboard updates
- Admin dashboard (host grid, detail, registration form)
- Config-driven server types with hot-reload
- Docker deployment (multi-stage fat image)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-05-03 20:55:14 -04:00