submodule: advance guru-rmm (runbook cleanup done); memory: old VM decommissioned + .47 dropped
This commit is contained in:
@@ -32,9 +32,10 @@ provisioned on the new box: source repo /home/guru/gururmm @ main 7c2f20e (rsync
|
||||
Pluto (Administrator@172.16.3.36) SSH auth OK for Windows builds. NOTE: gururmm has NO .gitea/workflows
|
||||
-- builds run via the **webhook-handler path** (Gitea webhook http://172.16.3.30/webhook/build ->
|
||||
nginx :80 /webhook/ -> :9000 -> build-*.sh on the server), NOT Gitea Actions. Pipeline wired end-to-end;
|
||||
not yet exercised by a real build. **Still pending post-cutover:** drop `.47` (new box) + `.46` (VM)
|
||||
mgmt IPs; decommission the old VM after a stability soak (VM parked on .46, powered on, DATA PRISTINE
|
||||
for rollback -- do NOT delete yet).
|
||||
not yet exercised by a real build. **Post-cutover cleanup DONE (2026-06-12):** old VM `GuruRMM`
|
||||
decommissioned after the soak — `virsh destroy`+`undefine`, `vdisk1.img` deleted, `.46` released;
|
||||
`.47` mgmt IP dropped from the physical box's netplan (eno1 now carries only `172.16.3.30`). The
|
||||
rollback anchor was intentionally retired; there is no longer a parked VM.
|
||||
|
||||
|
||||
**History (pre-cutover — now DONE, retained for context).** The GuruRMM server/build-pipeline
|
||||
|
||||
Reference in New Issue
Block a user