ops: retire VM 101 (DC) and VM 104 (nh3-laser) from running + backups; infra-ops login on pbs-ana/pbs-nh3; nh3-pve-2 follow-ups verified done

This commit is contained in:
vh
2026-10-04 16:37:15 -07:00
parent d0c1bc628a
commit 0e3ab447af
9 changed files with 13 additions and 13 deletions
+1 -1
View File
@@ -6,7 +6,7 @@ possibly a dev environment for security-software work. Standalone node, not clus
- **Host:** `10.100.250.62` on nh3-mgmt (`nh3-pve-2.nh3.internal`, `nh3-pve-2.phasefinal.com` in /etc/hosts). Static
in `/etc/network/interfaces`, plus a UDM reservation on `38:05:25:3b:a0:a8`. `ssh infra-ops@10.100.250.62`
(fleet key, NOPASSWD sudo with `log_output`).
- PVE 9.2.21, installed 2026-10-03 on site to the right disk (the 256 GB Toshiba).
- PVE 9.2.21, installed 2026-10-03 on site to the right disk (the 256 GB Toshiba). **Follow-ups DONE 2026-10-04:** Prime rebooted it at 0724 onto 7.0.14-20; verified 1635: `.62` on vmbr0, `nic0` up at 1 Gb with `arp_ignore=8` + IPv6 off, MeshCentral shows `nh3-pve-2-amt` connected (CIRA, power on), ceph + pve enterprise sources `Enabled: false`, 0 upgradable, no failed units. No guests yet.
| NIC | MAC | Chip | Use |
|---|---|---|---|
+1 -1
View File
@@ -27,7 +27,7 @@ after a power loss** is the column that matters in a recovery: a guest listed as
| 100 | nh3-docker (`10.100.50.40`) | VM | 1 | up |
| 101 | nh3-extdev (`10.100.50.42`) | VM | 1 | up |
| 102 | nh3-dev (`10.100.10.50`) | VM | 1 | up |
| 104 | nh3-laser | VM | — | **stays off — on-demand** (Prime, 2026-09-24) |
| 104 | nh3-laser | VM | — | **stays off — on-demand** (Prime, 2026-09-24); `onboot 0` + excluded from vzdump 2026-10-04 (Prime: not in use). Before any start: enroll MS 2023 Secure Boot certs (`qm enroll-efi-keys 104`) |
| 105 | pbs-nh3 (`10.100.50.90`) | VM | 1 | up (onboot added 2026-09-24; it had none and stayed down after the outage) |
| 108 | opnsense-lab | VM | 0 | stays off (lab) |
| 103 | nh3-wg | CT | 1 | up |
+1 -1
View File
@@ -1,6 +1,6 @@
# pbs-ana
> **2026-10-04: PBS 4.2.7 on Debian 13.7 (kernel 6.12.111)**, upgraded from 3.4.8 (`docs/runbooks/pbs-pbs4-upgrade-plan.md`). PBS-on-plain-Debian install (no `proxmox-backup` meta package, Debian kernel), so `pbs3to4` FAILs one check by design. infra-ops has no login here: root ops go through the hypervisor's guest agent (`qm guest exec`).
> **2026-10-04: PBS 4.2.7 on Debian 13.7 (kernel 6.12.111)**, upgraded from 3.4.8 (`docs/runbooks/pbs-pbs4-upgrade-plan.md`). PBS-on-plain-Debian install (no `proxmox-backup` meta package, Debian kernel), so `pbs3to4` FAILs one check by design. **`ssh infra-ops@10.250.50.90`** (uid 850, fleet key, NOPASSWD sudo with `log_output`) since 2026-10-04 (Prime); the hypervisor's guest agent (`qm guest exec`) is the fallback if the network is down.
Proxmox Backup Server — **fleet primary**. VM on pfi-pve with an
NFS-mounted datastore on the Ana NAS. All 5 hypervisors (pfi-pve,
+1 -1
View File
@@ -1 +1 @@
lkraven@10.250.50.90
infra-ops@10.250.50.90
+1 -1
View File
@@ -1,6 +1,6 @@
# pbs-nh3
> **2026-10-04: PBS 4.2.7 on Debian 13.7 (kernel 6.12.111)**, upgraded from 3.4.8 (`docs/runbooks/pbs-pbs4-upgrade-plan.md`). PBS-on-plain-Debian install (no `proxmox-backup` meta package, Debian kernel), so `pbs3to4` FAILs one check by design. infra-ops has no login here: root ops go through the hypervisor's guest agent (`qm guest exec`).
> **2026-10-04: PBS 4.2.7 on Debian 13.7 (kernel 6.12.111)**, upgraded from 3.4.8 (`docs/runbooks/pbs-pbs4-upgrade-plan.md`). PBS-on-plain-Debian install (no `proxmox-backup` meta package, Debian kernel), so `pbs3to4` FAILs one check by design. **`ssh infra-ops@10.100.50.90`** (uid 850, fleet key, NOPASSWD sudo with `log_output`) since 2026-10-04 (Prime); the hypervisor's guest agent (`qm guest exec`) is the fallback if the network is down.
Proxmox Backup Server — **DR mirror**. VM on nh3-pve with an
NFS-mounted datastore on the NH3 Synology. Pulls nightly from pbs-ana
+1 -1
View File
@@ -1 +1 @@
lkraven@10.100.50.90
infra-ops@10.100.50.90
+1 -1
View File
@@ -30,7 +30,7 @@ live here. Full enumeration as of 2026-05-14 (via `qm list` on the
hypervisor):
- **VM 100** — `pbs-ana` (Proxmox Backup Server; 10.250.50.90) — `servers/pbs-ana/`
- **VM 101** — `PFI-ANA-DC` — Active Directory domain controller; **not yet in `servers/` inventory**
- **VM 101** — `PFI-ANA-DC` — Active Directory domain controller; **not in use: shut down, `onboot 0`, excluded from vzdump since 2026-10-04 (Prime)**
- **VM 102** — `ana-docker` (PFI-ANA-Docker) — `servers/ana-docker/`
- **VM 103** — `PFI-SlaveBot` — **not yet in `servers/` inventory** (purpose TBD)
- **VM 104** — `PFI-Mongo` — MongoDB host; **not yet in `servers/` inventory**