prep for next ai session

This commit is contained in:
2026-08-01 15:45:23 -05:00
parent 46c35106fb
commit 6244c1cc25
139 changed files with 16712 additions and 0 deletions
+25
View File
@@ -0,0 +1,25 @@
# Naming and DNS Policy
> **Canonical naming policy for the PFVCluster fleet.**
> Established: 2026-07-31
## Rule
**The Proxmox VM name is the canonical identifier.** Everything else
derives from it:
1. **VM name** (set via `qm set <vmid> --name <name>`) is the source of truth
2. **DNS records** (Technitium, forward + reverse) must match the VM name exactly
3. **Tailscale node name** must match the VM name
4. **Monitoring/alerting** (Beszel, Uptime Kuma, LibreNMS) uses the VM name
5. **Inventory/k8s** references use the VM name
Any mismatch between VM name and DNS/Tailscale name is a **critical bug**
that must be fixed. The Technitium DNS API key is stored at
`~/.secrets/api-keys.env` for programmatic DNS management.
## Tools
- Technitium DNS API key: `~/.secrets/api-keys.env`
- Uptime Kuma API key: `~/.secrets/api-keys.env`
- DNS audit: `perf/scripts/probe-vm-dns.sh`
+70
View File
@@ -0,0 +1,70 @@
# Physical Systems (Pi's + other hardware)
> **Access patterns and locations for physical infrastructure devices.**
> Updated: 2026-07-31
## Raspberry Pi systems
All accessible via Tailscale. Use `localuser` (passwordless sudo to root)
except where noted.
| Name | Tailscale IP | LAN IP | Access | Purpose |
|------|-------------|--------|--------|---------|
| pfvsvrpi | 100.91.151.113 | 192.168.1.230 | `localuser` | Server Pi (general purpose) |
| subopi-dev-3 | 100.64.231.65 | 192.168.1.232 | via subodev jump | Suborbital dev Pi 3 |
| subopi-dev-4 | 100.65.224.85 | 192.168.1.231 | via subodev jump | Suborbital dev Pi 4 |
> **Note from operator:** "use subodev to get into subopi-*" — subodev is
> a jump host for the suborbital Pi's.
## Network devices discovered (non-Proxmox)
| IP | Device | Type | Identified via |
|----|--------|------|---------------|
| 192.168.0.12 | pfv-core-sw01 | Dell PowerConnect 5448 | SNMP |
| 192.168.0.7 | pfv-tor3-mgmt | Neyland 24T (PC5324) | SNMP |
| 192.168.0.8 | (unidentified) | Neyland 24T (PC5324) | SNMP |
| 192.168.0.9 | pfv-tor3-stor | Neyland 24T (PC5324) | SNMP |
| 192.168.1.166 | pfv-stor1 | Linux 4.14.22 (Synology?) | SNMP |
| 192.168.1.182 | UAP-AC-LR | UniFi AP (FW 6.8.2.15592) | SNMP |
| 192.168.1.230 | pfvsvrpi | Linux 6.12.62 (RPi) | SNMP |
| 192.168.1.231 | subopi-dev-4 | Linux 6.12.25 (RPi) | SNMP |
| 192.168.1.232 | subopi-dev-3 | Linux 6.12.9 (RPi) | SNMP |
| 192.168.1.217 | subopi3 | Linux 6.12.25 (RPi) | SNMP |
## Other identified hosts (SSH open, unidentified)
| IP | Notes |
|----|-------|
| 192.168.0.72 | SSH open, no SNMP — investigate |
| 192.168.0.250 | SSH open, no SNMP — investigate |
| 192.168.1.138 | SSH open — investigate |
| 192.168.1.181 | SSH open — investigate |
| 192.168.1.192 | SSH open — investigate |
| 192.168.1.201 | SSH open — investigate |
| 192.168.1.205 | SSH open — investigate |
| 192.168.1.214 | SSH open — investigate |
| 192.168.1.223 | SSH open — investigate |
| 192.168.1.226 | SSH open — investigate |
| 192.168.1.228 | SSH open — investigate |
| 192.168.2.5 | SSH open — investigate (tsys3 vmbr0) |
| 192.168.3.1 | SSH open — investigate (gateway/router?) |
| 192.168.3.78 | SSH open — investigate |
## 192.168.3.12-24 range
These 13 hosts respond to ping but have no SSH/SNMP. Likely:
- IoT devices
- Cameras
- Phones (VoIP)
- Other DHCP clients
## UniFi Access Points
| AP | Port (core-sw01) | Model | FW |
|----|-----------------|-------|-----|
| UAP-AC-LR | g9 (2902 inErrors!) | UAP-AC-LR | 6.8.2.15592 |
| UAP-AC-Lite | g38 (590 inErrors!) | UAP-AC-Lite | (unknown) |
Both managed by UniFi controller (likely on Home Assistant VM 100 or
pfv-stor1). UniPoller exports metrics to Prometheus.