-
v0.15.3
Stable
gitea-actions
released this
2026-10-29 21:07:44 +01:00 | 77 commits to main since this releaseA model stopped and kept, or removed with its files; the second mirror fixed where it was tried.
Upgrading.
- No migrations. The control planes carry stop, start and purge; the nodes need nothing new.
- The mirrors carry the fixes: on each mirror's machine,
sudo llmgw upgrade v0.15.3 --service llmgw-mirror.
A mirror with a peer then works out the checksums its older files lack, once, which reads every such file.
Added
- A model stopped and kept, and a model removed with its files.
llmgw ctl model stop|start MODEL: none of its
replicas run, it stays in the catalog with its files, and start runs it again scaled as it was; requests are told an
administrator stopped it.llmgw ctl model remove MODEL --purge(DELETE /api/v1/models/{name}?purge=true) also
deletes every version of it on the mirror, a second mirror following, and the nodes' copies once its replicas have
stopped; what another model uses stays. Both are in the console's model menu.
Fixed
llmgw mirror add-peeron a mirror with a machine of its own. It set the second mirror up and then
failed for want of the control plane's server.yaml; now it prints thellmgw ctl config set mirror.peers
to run on a control plane.- Models fetched before checksums were kept reach the second mirror. A mirror kept in step copies only what it
can check, and those files had no sha256; a mirror with peers now works theirs out and records them, once. - A file removed with
llmgw mirror removeis gone from the mirror's answers too. The running mirror kept
reporting a file it had fetched as present for a week after it was removed, so a control plane could place a
model on a file that was not there; and the removal was not recorded, so a mirror kept in step copied it back.
Downloads