Repository navigation
feat(lab): dotfiles OS-layer VMs, phase 1: Debian, Fedora and Windows (#920) - #1083
Conversation
…#920) ADR-0090 decides one on-demand guest per dotfiles OS layer on Saruman, templates 903-909 and guests 191-198 at .91-.98, built from an installer where one exists and from the publisher's image where not, and run from a `clean` snapshot taken stopped. Phase 1 writes tpl-debian-13 (903, preseed over HTTP as Kali's) and tpl-fedora-server (904, kickstart on an OEMDRV disc), lists both ISOs from their publishers' signed hashes, and declares dot-debian, dot-fedora and dot-windows (an unactivated clone of 911) in a `dotfiles` pool. The new runbook test-the-dotfiles-layers.md is the rollback, bootstrap and read loop. Also corrects packer/README.md: 911 and 912 were both rebuilt on 2026-10-07 after the SetupComplete.cmd fix. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…yer-vms-643b16 # Conflicts: # docs/changelog.md
…#920) Anaconda 44 stopped the first build at 'Error enabling service cloud-init: 1'. cloud-init 24.3 renamed its units, so there is no cloud-init.service, and Fedora's presets enable the real ones anyway. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…resets leave it out (#920) 2f97981 dropped `cloud-init` from the services line (no such unit since cloud-init 24.3) and relied on Fedora's presets for the real units. f44's 90-default.preset enables cloud-config, cloud-final, cloud-init-main and cloud-init-local, but not cloud-init-network, which is WantedBy=cloud-init.target only. cloud-init-main (`--all-stages`) waits for each stage's unit to signal it, so without it the network stage — network config and SSH keys from the Proxmox cloud-init drive — may never run on a clone. The unit exists in f44's cloud-init 26.x, so naming it cannot hit the "Error enabling service" stop. Not yet proved on a build: `systemctl is-enabled cloud-init-network` and `cloud-init status --long` on a clone are the check. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
I pushed 8e1eaeb on top of 2f97981. It adds Why: 2f97981 relies on Fedora's presets to enable cloud-init's units. f44's Not yet proved on a build. On the built template or a clone: systemctl is-enabled cloud-init-network.service
cloud-init status --longThe first should say 🤖 Generated with Claude Code |
…yer-vms-643b16 # Conflicts: # docs/changelog.md
…yer-vms-643b16 # Conflicts: # docs/changelog.md
|
Garrett would like this merged once a build proves it. Where it stands:
For the owning session:
🤖 Generated with Claude Code |
The first build's 10s boot_wait, copied from Kali, typed `c` before the installer menu was drawn, and the menu has no timeout. Typing the same lines from the console booted the installer, which fetched the preseed from phoenix:8800 and ran unattended. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…yer-vms-643b16 # Conflicts: # docs/changelog.md
…yer-vms-643b16 # Conflicts: # docs/changelog.md
…ew entries stop conflicting with it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…or (#920) The first apply's Linux guests came up with no login: Debian ships a system group `operator` (gid 37), so cloud-init's useradd exited 9, and Fedora ships a system user of that name. The guests now pass `tester`, the Windows guest's bootstrap user too; every other guest keeps `operator`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… key; first as-run rows (#920) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e console, not over SSH (#920) Debian passes clean. Fedora exits 0 with 14 tools missing: yazi's cargo build fills the per-user quota on Fedora's tmpfs /tmp and the downloads after it fail. Windows cannot be tested over SSH at all: winget, MSIX, winget configure and scoop's junctions each fail in a network logon. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… say what the builds and first runs found (#920) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…llowPrelease fix, and a way past OOBE (#920) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…yer-vms-643b16 # Conflicts: # docs/architecture.md # docs/network.md
There was a problem hiding this comment.
🟡 Changes recommended
The runbook races asynchronous rollback, may apply unrelated OpenTofu changes, and leaves required network diagrams stale.
8 open findings
Add new inventory hosts to network diagrams · New Wait for snapshot rollback before starting VM · New Apply winget prerequisite correction before configuring · New Target the specific guest module during rebuild · New Correct NixOS image-building path per ADR-0090 · New Remove roadmap status and completion date · New Correct count of new Linux templates · New Clarify shared Debian installer exception · New
What changed in this PR
Implements phase 1 of #920 by adding reproducible Debian and Fedora templates plus on-demand Debian, Fedora, and Windows dotfiles test guests.
Changes:
- Adds Packer templates and verified installer pins.
- Provisions three OpenTofu guests in a dedicated pool.
- Documents architecture, inventory, decisions, and testing procedures.
| File | Description |
|---|---|
README.md |
Updates documentation counts. |
tofu/README.md |
Documents dotfiles guests and pool. |
tofu/guests.tf |
Defines the three test guests. |
tofu/modules/guest/variables.tf |
Supports new templates and disk floors. |
scripts/collect-iso-store-state.sh |
Pins Debian and Fedora ISOs. |
packer/variables.pkr.hcl |
Adds installer variables. |
packer/README.md |
Documents template inventory. |
packer/debian.pkr.hcl |
Builds the Debian template. |
packer/debian/preseed.cfg.pkrtpl |
Automates Debian installation. |
packer/fedora.pkr.hcl |
Builds the Fedora template. |
packer/fedora/ks.cfg.pkrtpl |
Automates Fedora installation. |
docs/runbooks/test-the-dotfiles-layers.md |
Adds the testing workflow. |
docs/runbooks/provision-lab-guests.md |
Documents the pool ACL. |
docs/runbooks/build-the-lab-templates.md |
Adds template build instructions. |
docs/roadmap.md |
Adds phased rollout planning. |
docs/network.md |
Adds guest inventory and addresses. |
docs/changelog.md |
Records phase-one results. |
docs/architecture.md |
Adds the guests to architecture inventory. |
docs/adr/0090-test-the-dotfiles-os-layers-on-on-demand-saruman-guests.md |
Records the design decision. |
docs/adr/0074-build-the-lab-templates-with-packer-from-phoenix.md |
Notes the expanded template strategy. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
… task waits, targeted replace (#920) - The network diagram gets dot-debian, dot-fedora and dot-windows in VLAN 30's Saruman box; network.png re-rendered at 1.5x (cairosvg; nothing outside the edited area changed). - The runbook waits on each Proxmox task's UPID and checks it ended OK before the next call, so a start never meets a guest still locked by a rollback. - A rebuild's -replace is paired with -target, so it cannot apply anything else pending in the state. - The Windows commands fix configuration.dsc.yaml before winget configure, not after; dotgibson/dotfiles-Windows#285 linked. - ADR-0074's note separates NixOS's image builder from Alpine's and Gentoo's publisher images; the roadmap keeps order, not dates or status; two sentences in build-the-lab-templates.md made plain. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er boots an on-demand guest (#1101) The provider's `started` defaults to true and the module never set it, so every plan that met a stopped on-demand guest proposed started false -> true, and an untargeted apply would have booted it. Found reconciling #1083 after merge: dot-debian and dot-fedora (stopped) showed it; carbuncle and siren would have too had they been off. A guest is still started on creation. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>


Phase 1 of #920 (does not close it). ADR-0090 records the whole design. This PR builds Debian, Fedora and Windows.
What
Templates
packer/debian.pkr.hcl, 903tpl-debian-13: trixie netinst with a preseed served over Packer's HTTP server on 8800, the same way Kali's is. Secure Boot stays on.packer/fedora.pkr.hcl, 904tpl-fedora-server: Server 44 netinst with a kickstart on anOEMDRVdisc, which Anaconda reads with no boot argument.curlandgit, which the bootstrap preflight needs.Installers
collect-iso-store-state.sh'sEXPECTEDlist.Guests (
tofu/guests.tf), in a newdotfilespool and taggeddotfiles;on-demand:dot-debian(191)dot-fedora(192)dot-windows(198), an unactivated clone of 911Module:
tofu/modules/guestnow accepts 903 and 904 and knows their disk floors.Docs
test-the-dotfiles-layers.md: Kea reservations, apply, acleansnapshot taken stopped, the rollback, bootstrap andcore doctorloop for each layer, and a standardtesteruser on Windows because scoop refuses an elevated shell.build-the-lab-templates.mdandprovision-lab-guests.md§2 (the/pool/dotfilesgrant).network.md,architecture.md, the README counts, the changelog and roadmap entries, and a NOTE banner on ADR-0074.Also fixed:
packer/README.mdclaimed 911 was unbuilt and 912 needed a rebuild. Their descriptions show both were rebuilt on 2026-10-07, after #1031.Verified
packer fmt -checkandpacker validate -syntax-only(1.16.1) pass.tofu fmt -checkandtofu validate(1.13.1) pass.check_docs.py,yamllint --strictandcollect-iso-store-state.sh --self-testpass.Built and run on Saruman (2026-10-08)
ISOs
smaug-isoand readstate="match".Templates
-force, and every build passedpacker-smoke.sh.cloud-initunit name;cloud-init-networknamed explicitly. The second is commit8e1eaeb, from another session.boot_waitraised to 20s.Guests
-target. The four pendinglab-domaintag updates on 150–153 were left alone: they only catch the state up with tags root set by hand.cleansnapshot, taken while stopped.tester. Debian has a system group namedoperatorand Fedora a system user, so the module's defaultoperatorcan't be created on either.First dotfiles runs (details in the runbook's as-run table)
/tmp(a dotfiles-Fedora issue).winget, MSIX installs,winget configureand scoop's junctions all fail in a network logon. The runbook now says to run it from the console.Still open
Phases 2–4 (openSUSE and Arch; Alpine and Gentoo from their images; NixOS) follow in separate PRs.
🤖 Generated with Claude Code