Skip to content

docs: record that the lab guest is built and its log sources verified (#262) #325

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Gerrrt merged 1 commit into from
Sep 5, 2026
+23 −7
Merged

docs: record that the lab guest is built and its log sources verified (#262) #325

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions docs/roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -507,11 +507,12 @@ what left this one unfireable for months.
`*_URL` variables changed, and that file has two sinks, so a lab without a
Prometheus points the second one at `10.0.99.20` and inverts the isolation
the ADR exists for.
[#264](https://github.com/Gerrrt/HomeLab/issues/264) is built:
`stacks/lab/` holds the compose file, both configs, four alert rules and
their unit tests, and the secrets template. What is left of it is a deploy,
which needs [#262](https://github.com/Gerrrt/HomeLab/issues/262) — the guest
on `Saruman` — to exist first.
[#264](https://github.com/Gerrrt/HomeLab/issues/264) is built **and
running**: `stacks/lab/` is deployed on `alexander`
([#262](https://github.com/Gerrrt/HomeLab/issues/262), 2026-09-05), the guest
on `Saruman` that ADR-0020 called for. Four services, its own age key, its own
leaf from the estate's CA, and three Loki log sources confirmed on the host —
the check the Ubuntu-over-Debian decision exists for.
→ [runbook](runbooks/build-the-lab-guest.md) Building it made the tooling stack-aware
(`render-config.sh` derives its required keys per stack rather than demanding
the estate's ten, `reload-config.sh` skips services a stack does not declare,
Expand Down
19 changes: 17 additions & 2 deletions docs/runbooks/build-the-lab-guest.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,21 @@
KVM or `shiva`), an Ubuntu Server ISO, and a shell on the monitoring host for
the certificate in §5

> **Status — 2026-09-05: `alexander` is built and `stacks/lab` is running.**
>
> Ubuntu 26.04 LTS, `10.0.30.40`, `bc:24:11` OUI. §7 passed with all three Loki
> jobs — `/var/log/auth.log`, `/var/log/syslog` and `/var/log/journal` — so the
> file sources are collecting and not merely configured.
>
> **26.04 ships rsyslog**, which §0 could not assume: both files are present and
> `syslog:adm 0640`, the ownership `LOG_READ_GID` is derived from. That is one
> LTS confirmed, not a guarantee about the next one — §7 stays the check.
>
> Two things bit on the way through and are fixed rather than described: the
> lab's `.sops.yaml` rule matched nothing, so §4 encrypted to the estate's key
> (#321), and `make validate` told the guest to install the estate's timers
> (#323). Both are in the repository's history if the symptoms recur.

This builds the host [ADR-0020](../adr/0020-run-the-lab-stack-in-a-guest-with-its-own-prometheus.md)
called for: a guest, **not** the hypervisor, because a compose stack is Docker
and Docker would rewrite the iptables of the box whose own firewall ADR-0014
Expand Down Expand Up @@ -244,14 +259,14 @@ so a fresh clone on `alexander` does not have it and `scp` would fail into a
directory that is not there:

```bash
ssh you@10.0.30.40 'mkdir -p HomeLab/certificates && chmod 700 HomeLab/certificates'
ssh garnet@10.0.30.40 'mkdir -p HomeLab/certificates && chmod 700 HomeLab/certificates'

CERTS=/home/robo/code/Gerrrt/HomeLab/certificates
scp -3 -p \
robo@10.0.99.20:$CERTS/ca.pem \
robo@10.0.99.20:$CERTS/grafana-lab.matrix.elysium.pem \
robo@10.0.99.20:$CERTS/grafana-lab.matrix.elysium-key.pem \
you@10.0.30.40:HomeLab/certificates/
garnet@10.0.30.40:HomeLab/certificates/
```

`-3` routes the copy through the Mac without writing either file to its disk,
Expand Down