Skip to content

Garry's Opinionated OpenClaw/Hermes Agent Brain

TypeScript

docs(ubicloud): gstack's 4 h sweep covers only the caller's own TTL-less VMs; -t<H> in the name format

garrytan01d2bc2c8c60
diff --git a/docs/TESTING.md b/docs/TESTING.md
index e183d029a3..b42a472487 100644
--- a/docs/TESTING.md
+++ b/docs/TESTING.md
@@ -458,7 +458,7 @@ too; build the admin app on the host when updating its committed bundle.
from one heaviest-first work queue; every VM is destroyed on exit. VM setup, scheduling, weights, quota
and flags are in [scripts/ubicloud/README.md](../scripts/ubicloud/README.md).
-VMs are named `ubirun-<owner>-<epoch>-<suffix>`; set `UBI_OWNER` to your thread
+VMs are named `ubirun-<owner>-<epoch>-<suffix>-t<H>`; set `UBI_OWNER` to your thread
code. `scripts/ubicloud/ubi-runner.sh usage` shows vCPUs by owner.
A sleeping machine kills the run with no signal, so teardown never runs: on Capy, run
`ci:ubicloud` as a watched background operation. After any interrupted run, check
diff --git a/scripts/ubicloud/README.md b/scripts/ubicloud/README.md
index 488832b115..f4c5eab2a9 100644
--- a/scripts/ubicloud/README.md
+++ b/scripts/ubicloud/README.md
@@ -34,11 +34,13 @@ the quota. Ubicloud names allow 63 characters of `[a-z0-9-]`, so a full name
stays under 50.
Ubicloud has no VM tags, so the TTL lives in the name, and gstack's
-`ubi-runner.sh reap` reads it the same way. `ci:ubicloud` gives every gate VM a
+`ubi-runner.sh reap` reads the TTL of every name gbrain generates the same way. `ci:ubicloud` gives every gate VM a
two-hour TTL (`--ttl-hours N` changes it, up to 999). `ubi-runner.sh up` and
`run` take the same `--ttl-hours H`; without it their VMs get `-t999` (about
-41 days) for long dev, benchmark and eval VMs, and gstack's reap destroys a
-`ubirun-*` VM with no TTL once it is four hours old. `scripts/ubicloud/reap-expired.ts` is the operator
+41 days) for long dev, benchmark and eval VMs. gstack's `up` also destroys
+the caller's own (`UBI_OWNER`) `ubirun-*` VMs that carry no `-t<H>` (TTL-less or
+older `-x<expiry>` names) once they are four hours old, so give a long-lived VM a
+TTL before running gstack's runner under the same owner. `scripts/ubicloud/reap-expired.ts` is the operator
side of the leak guard: run from the operator's Capy automation, where the
Ubicloud token already lives (never from GitHub Actions), it lists the project's
VMs, selects only names with a TTL (or the older
diff --git a/scripts/ubicloud/ubi-runner.sh b/scripts/ubicloud/ubi-runner.sh
index b77ad4f443..111b1399b3 100755
--- a/scripts/ubicloud/ubi-runner.sh
+++ b/scripts/ubicloud/ubi-runner.sh
@@ -15,10 +15,10 @@
# Needs only bash, curl, python3, ssh, ssh-keygen, and tar locally, so it works
# from dev boxes, containers, and cloud sandboxes.
#
-# Ownership: VMs are named ubirun-<owner>-<epoch>-<suffix>. <owner> is UBI_OWNER
+# Ownership: VMs are named ubirun-<owner>-<epoch>-<suffix>-t<H>. <owner> is UBI_OWNER
# (lowercased, letters and digits only, at most 12 characters, starting with a
# letter) or a random per-machine id kept in $STATE_ROOT/owner-id. Ubicloud names
-# allow 63 characters of [a-z0-9-], so a full name stays under 40.
+# allow 63 characters of [a-z0-9-], so a full name stays under 50.
#
# Expiry: every name `up` and `run` generate ends in a TTL,
# ubirun-<owner>-<epoch>-<suffix>-t<H>, expiring H hours after creation: H is