vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(pve9 plan): keep ESH DNS up during the NAS reboot (unmount 2 shares instead of stopping VM 100)

Browse Source
This commit is contained in:
vh
2026-10-03 15:50:31 -07:00
parent 48f28cfe93
commit 473c52dc6b
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/runbooks/esh-pve-cluster-pve9-upgrade-plan.md
+4
View File
@@ -63,6 +63,10 @@ one-off backups of 103-107 to pbs-ana (1530-1532); pve8to9 0 FAIL. Then:
dockerd did not restart it. zigbee2mqtt restart-looped without its broker until mosquitto was started by hand dockerd did not restart it. zigbee2mqtt restart-looped without its broker until mosquitto was started by hand
(`compose up -d`, 15:45). **After any VM 100 reboot, check mosquitto and zigbee2mqtt.** (`compose up -d`, 15:45). **After any VM 100 reboot, check mosquitto and zigbee2mqtt.**
- Total ESH impact: DNS ~6 min (15:33-15:39); DB ~12 min; Zigbee ~13 min; NAS/media ~4 min. - Total ESH impact: DNS ~6 min (15:33-15:39); DB ~12 min; Zigbee ~13 min; NAS/media ~4 min.
- **Better for the real esh-nas-pve reboot: do NOT shut VM 100 down. That is what took ESH DNS out.** Only two of its containers use
the NAS shares: `calibre-web-automated` (/mnt/books) and `beszel-agent` (stats of /mnt/books and /mnt/backup). Stop those two,
`umount /mnt/books /mnt/backup` inside VM 100, reboot the NAS host, then remount and start them. DNS, Z2M/mosquitto and the rest
stay up. VM 101 still has to shut down (its disk is qcow2 on the `esh-nas` NFS storage).
## Pre-flight (no guest downtime) ## Pre-flight (no guest downtime)