| Filename | Latest commit message | Latest commit date |
|---|---|---|
8b55a8b9fd
`POST /api/agents` now requires `hive` alongside `name`. It is parsed as an `Ident` like `name` already was, and then checked against the roster loaded from `SWARM_CONTROLLER_HIVES` -- a hive that is not in this swarm is a 400 naming the ones that are, rather than a typo accepted and forgotten. The roster check is what makes the field worth having; without it nothing notices until a deploy message is addressed to a hive that does not exist. `hive` is an address, not an attribute of the agent: it is where a deploy message goes over the queue, so nothing writes it into the agent's config repo. A config naming its own hive would be a second statement of where the agent lives, free to drift from the queue that actually delivers to it. It rides on the `InitAgentConfigRepo` node payload because the graph is the only thing carrying the operator's choice forward from the API boundary; seeding does not consume it. The node that routes on it is the deploy node in #3124. The refusal is asserted by effect -- the test checks that *nothing was queued*, not just the status code, since a version that queued the graph and then complained would satisfy a status-only assertion while still creating the agent. This is a breaking change for every existing caller: the swarm-UI create page posts `{name}` only and needs its hive dropdown to land alongside. |
||
| .. | ||
| src | ||
| Cargo.toml | ||
| README.md | ||
swarm-controller
The swarm-level daemon. Where hive-c0re owns the agents on one host, this
owns what is true across hives — so a swarm runs one of them and most hives
leave it off.
Opt-in per host via services.hyperhive.swarm.controller.enable, which is
deliberately not derived from services.hyperhive.enable: turning it on is
a statement about swarm topology, not about whether hyperhive is installed.
What it does today
Serves one /health endpoint and holds no state.
That is the whole intent of the first slice. The point is to make the unit
real — service user, runtime and state directories, socket, nginx
reachability — so the swarm-level surfaces that follow have somewhere to land.
Inventing those surfaces before they are agreed would bake in a shape nobody
chose. See #3066 and the hyperhive.swarm consolidation epic.
Why a unix socket, not a port
The hive-gateway's nginx is the only intended client and reaches the socket through a bind-mount. A listener that is never bound to an address cannot be reached from off-host by mistake.
The socket path is services.hyperhive.swarm.controller.socketPath, default
/run/swarm-controller/controller.sock, exported to the process as
SWARM_CONTROLLER_SOCKET.
⚠️ The socket's directory is its access control
The socket is 0666. It has to be: nginx runs as a different user and
connect(2) needs write. This matches how hive-c0re publishes the per-agent
sockets, and rests on the same argument — "the bind source dir is per-agent on
host so blast radius is unchanged."
What keeps that safe is that the directory holds one socket. So:
Never point
socketPathat a directory that carries anything else./run/hyperhiveabove all — it holdshost.sock, the host admin socket. Pointing nginx at that directory to reach this socket would put the admin socket within its reach too.
nginx is a host service, so nothing narrows what it can reach except the directory itself — that is the whole of the access control. A unit test pins the default path so a tidying edit fails instead of reviewing cleanly.
RuntimeDirectoryPreserve=yes and the daemon's stale-socket unlink on start are
a pair: preserving the directory without the unlink means bind fails with
EADDRINUSE after a restart.
Packaging
Built by the workspace derivation and extracted as its own package
(nix build .#swarm-controller). Deliberately not in nix/packages'
daemonBins — that list is the core stack and drives the bundle
services.hyperhive.c0re.package points at, so folding this in would put a
swarm-scoped service into every hive's closure.