Merge C24 federation: another llmgw cluster as a provider

Conflicts with facility-aware placement (config, control, admin API routes,
store test tables) all keep both; the generated reference and OpenAPI
document regenerated.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-10-05 01:29:35 +02:00
commit 33334c8f33
33 files changed
+2945 -24

No files matched your search

@@ -0,0 +1,22 @@
-- Other llmgw clusters this one federates with (`llmgw ctl federation add`):
-- each peer's address, the file on the control plane holding the key this
-- cluster uses there, whether requests sent to it carry tags naming who sent
-- them, the peer's own cluster id, and the models it last offered.
--
-- The models are kept, not only fetched, so a catalog that names one of them
-- as a fallback is whole at startup, before the peer has been asked again:
-- a local model falling back to a peer's would otherwise be skipped as
-- naming a model that is not there. Stored as JSON for the same reason a
-- runtime model's definition is: a list of what the peer says about each,
-- which grows.
CREATE TABLE federation_peers (
name TEXT PRIMARY KEY,
url TEXT NOT NULL,
key_file TEXT NOT NULL DEFAULT '',
send_tags INTEGER NOT NULL DEFAULT 0,
cluster TEXT NOT NULL DEFAULT '',
models TEXT NOT NULL DEFAULT '[]',
synced_at INTEGER NOT NULL DEFAULT 0,
created_at INTEGER NOT NULL,
created_by TEXT NOT NULL DEFAULT ''
);