mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 11:46:35 +00:00
kevinveenbirkenbachandClaude Opus 4.8
cb52a72f2e
The drill entry gate treated 'deploys no swarm service' as 'has nothing to restore', but the backup chain operates on NFS volumes and deployed backup units, not on scheduler objects; bigbluebutton's seven NFS-backed volumes went entirely unproven. Gate the drill solely on the NFS-flagged volume and make only the full-disaster step workload-aware: stack roles keep docker stack rm, node-local roles get their compose project (label com.docker.compose.project=<entity>, the compose handler's --project convention) stopped on every node so no writer races the export wipe and restore. Declare workload: node-local on bigbluebutton so the phantom-service converge/chaos gates skip while play, e2e and now the drill keep running; svc-runner stays skipped via its missing NFS volume. Document the nine drill steps host-by-host in the README. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Script Collection
This directory contains automation scripts used across the project.
-
system/ contains host and system-facing helpers.
-
container/ contains helpers that run inside the local container.
-
github/ contains GitHub workflow helper scripts.
-
For the canonical Make target index, see make.md.
-
🛠️ Organize operational helpers for development, CI, release, and maintenance
-
🧭 Separate responsibilities into focused subdirectories with clear scope
-
📚 Keep script-based workflows discoverable and easier to navigate
The scope of this folder is script organization at the repository level. Detailed responsibilities belong in the README files of the respective subdirectories.