Files
gstack/docs
Garry Tanandcapy-ai[bot] 67f1f82fbb Stop Ubicloud fan-outs overshooting the vCPU limit and owners deleting each other's VMs (GST-2852) (#4430)
* Stop Ubicloud fan-outs overshooting the vCPU limit and owners deleting each other's VMs (GST-2852)

The runner's quota check now reads usage and books the new VM's vCPUs under
one lock per machine, so shards started together see each other instead of
all passing on the same reading. A new room command prints how many VMs of a
size fit now, so a fan-out can size each batch. When usage can't be read,
a UBI_QUOTA_VCPUS ceiling refuses the create instead of letting it through.

VM names keep the whole owner id (up to 31 characters) instead of its first
12, so owners sharing a prefix no longer reap each other's VMs (#3748). A VM
named under the old cut form is still reaped by the machine that recorded it.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Add the changelog entry for the Ubicloud quota and owner-id fixes (GST-2852)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* fix: pre-landing review fixes

Review-Finding: p1/specialist-batched#1 reader=testing
Review-Finding: p1/specialist-batched#2 reader=red-team
Review-Finding: p1/specialist-batched#3 reader=testing
Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Say which old-form VMs a long owner still reaps in the changelog entry (GST-2852)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

* Name the room command in the Ubicloud skill summary (GST-2852)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

---------

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
2026-11-17 11:11:34 +00:00
..