| Filename | Latest commit message | Latest commit date |
|---|---|---|
ccf9951e5d
The swarm writes agent-configs/<agent> when it creates an agent, before any hive is told to deploy it. setup_proposed authored a second copy of those same bytes locally, so an agent's initial config had two sources of truth, each unaware of the other and free to disagree. It now clones that repo and falls back to the template only when there is nothing there to take. Preferred-source rather than a new-path-only variant because provision_container is the Provision node for the swarm deploy and the approval flow both, and cannot tell them apart. The approval flow creates agent-configs/<agent> only after the first spawn (forge_after_first_spawn), so it finds nothing and lands on the template: the fallback becomes unreachable when hive-level create is removed, rather than becoming something someone has to find and delete. clone, not the neighbouring init+fetch. A failed fetch leaves an empty .git behind, and that .git is exactly the byte setup_proposed reads to decide whether seeding is still needed, so the fallback would have seen a seeded repo. git removes a directory it created when a clone fails. --branch main also makes an empty repo fail cleanly instead of cloning to an unborn HEAD that would look seeded. |
||
| .. | ||
| 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.deploy.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.