| Filename | Latest commit message | Latest commit date |
|---|---|---|
bac4a8b6a1
The controller verified a knowledge delivery, logged it, and returned OK. Nothing downstream ever heard about it, so a hive learned the repository had changed only by registering its own webhook — which is the last-writer-wins contention this issue is about. The event carries no payload. The hive-side handler this replaces reads two fields from Forgejo's push webhook and uses neither — both are filters — then runs `git pull`, which re-derives everything from the repository. What crosses the queue is an edge trigger, and fields would invent a contract nobody reads. One subject per hive, so the callout policy can express "this hive may hear its own events" at all; a subject with no hive component is the same subject for every hive. `ConfigPr` deliveries are deliberately not forwarded. A hive does not want to hear that a config PR opened — it wants to be told when to rebuild from main, which the controller decides after a merge rather than by relaying this delivery. That is deploy coordination's job, and the empty arm is there so the omission reads as scoped rather than forgotten. Fails soft: a missed announcement costs a hive stale knowledge until its next boot pull, which is the same cost as a webhook delivery to a hive that was down — what this replaces. A permission failure cannot be observed at the call site (a NATS authorization violation is reported asynchronously on the connection, reaching a client as a timeout or as nothing), so the doc says the flush proves only that the bytes left this process and points at the server log. |
||
| .. | ||
| 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.