Skip to content

docs(sensor): the compose header says make up, and that fenrir is built #1162

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 2 commits into from
Oct 10, 2026
Merged

docs(sensor): the compose header says make up, and that fenrir is built #1162

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
384e515
docs(sensor): the compose header says make up, and that fenrir is built
Gerrrt Oct 10, 2026
8500ac6
docs(sensor): the runbook has #437's reboot test; the changelog has i…
Gerrrt Oct 10, 2026
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
20 changes: 10 additions & 10 deletions stacks/sensor/compose.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,20 +3,20 @@
# carries its logs to the lab's Loki (#437).
#
# Deployed on: fenrir (10.0.30.90, VLAN 30 / ImaginationLAN) — a guest on
# `Saruman`, VMID 190. NOT BUILT YET. Authored ahead of the guest
# the way stacks/soc was ahead of odin. The build, and the reboot
# proof that closes #437, is docs/runbooks/build-the-sensor-guest.md.
# `Saruman`, VMID 190. Built 2026-09-30 by
# docs/runbooks/build-the-sensor-guest.md, which also has the
# reboot test for #437. The result, run that day, is under
# 2026-09-30 in docs/changelog.md.
# Decided by: docs/adr/0068-mirror-the-lab-bridge-to-zeek-with-tc-not-open-vswitch.md
# — why a `tc` mirror on the Linux bridge rather than Open vSwitch,
# why a guest of its own, and why the check that the mirror is up
# lives on the hypervisor and not here.
# Deploy with: NOT `make up STACK=sensor`. That target renders a secrets file,
# and this stack has none — no service here takes a credential.
# On fenrir, from the repository root:
# cp stacks/sensor/.env.example stacks/sensor/.env
# docker compose -f stacks/sensor/compose.yaml up -d
# stacks/media is the other stack deployed this way, for a
# different reason (#528); README.md has the procedure.
# Deploy with: `make up STACK=sensor`, on fenrir, from the repository root.
# Since #834 the stack has one secret, Alloy's token for the
# lab's ingest proxy, and `make up` renders it from
# secrets/sensor.sops.yaml. Before that it had none and was
# brought up with plain `docker compose`; README.md has the
# one-time secrets-init and secrets-edit steps.
#
# WHAT THIS SEES AND WHY. `fenrir` has two NICs. `net0` is on vmbr0 like every
# other guest and carries this stack's own traffic to alexander. `net1` sits
Expand Down
Loading