MakerFLOSS/docs/hardware/srv07.md
sjat f047332e94
All checks were successful
Build docs site / build (push) Successful in 53s
Build slides / build (push) Successful in 1m11s
docs(hardware): record srv07 real specs and identity, correct mf04 mapping
srv07 verified on-site 2026-07-17: it is the Ansible/OS host mf04
(i3-4360T 2c/4t, 16 GB, 500 GB HDD, Debian 13), renamed to srv07 to match
the sticker. The naming-scheme migration row said mf04 -> srv05 — corrected
with a dated note. pp02: srv07's LAN path was restored 2026-07-17; the new
rear patch of port 8 is ad hoc and still needs recording.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-17 17:20:41 +02:00

1.3 KiB

hostname kind status cluster location cpu cpu_cores cpu_threads ram_gb storage_gb storage_type nic_gbps rack mounted_on shelf_face shelf_slot chassis_u power links
srv07 server staging tappaas The pile Intel Core i3-4360T @ 3.20GHz 2 4 16 500 hdd 1 rack01 shf02 front 1 6
pdu outlet
pdu01 1
pdu outlet
pdu02 1
local peer peer_port speed_gbps
eth0 pp02 8 1

Notes

  • Specs read live 2026-07-17 (lscpu/free/lsblk): i3-4360T (2c/4t), 16 GB RAM, 500 GB HDD (Seagate ST3500418AS). Runs Debian 13 (trixie).
  • This is the machine Ansible (AnsibleBaobabV4) managed as mf04; the OS hostname was renamed mf04 → srv07 on 2026-07-17 to match the sticker. The naming-scheme guide's migration row originally said mf04 → srv05; that was a mis-mapping (srv05's page describes an i5-3570K box).
  • SSH on :7576 (project standard), user sjat. WireGuard split-tunnel to the makerfloss VPS (wg1 peer 10.13.0.3, unit wg-quick@mf-srv07) dials out automatically on boot.
  • LAN path restored 2026-07-17 (DHCP lease 10.0.0.183). The rear patch pp02:8 → sw01:7 had been removed when sw01:7 became the sw06 uplink, so the box had no LAN path; the current rear patching still needs to be recorded — confirm on-site which switch/port it lands on and update this page + pp02.