remove the old snapshot store; tombstone its options
This commit is contained in:
parent
de3c5cbb65
commit
20d286f06a
1 changed files with 97 additions and 1308 deletions
|
|
@ -332,43 +332,6 @@ in
|
|||
# deployment-shape switch rather than swarm bookkeeping, so it lives
|
||||
# with its consequences instead of here.
|
||||
|
||||
options.services.hyperhive.swarm.snapshotStore = {
|
||||
address = lib.mkOption {
|
||||
type = lib.types.nullOr lib.types.str;
|
||||
default = null;
|
||||
example = "10.100.0.1";
|
||||
description = ''
|
||||
Mesh address of the swarm's snapshot store — the single
|
||||
`btrfs receive` endpoint every hive in this swarm pushes agent
|
||||
snapshots to. Bare IP, no prefix.
|
||||
|
||||
There is exactly **one** store per swarm, not one per peer: the
|
||||
receiver keys destinations by *agent*, so an agent that migrates
|
||||
between hives keeps a single unbroken incremental chain. Per-hive
|
||||
stores would split that chain in two, which is the case the store
|
||||
exists to serve.
|
||||
|
||||
Null means this swarm has no store configured, and pushing fails
|
||||
saying so rather than guessing an address. Set it on every hive
|
||||
that pushes; the receiving host separately sets
|
||||
`services.hyperhive.snapshotStore.enable`.
|
||||
'';
|
||||
};
|
||||
|
||||
port = lib.mkOption {
|
||||
type = lib.types.port;
|
||||
default = 51821;
|
||||
description = ''
|
||||
TCP port the swarm's snapshot store listens on. Must match the
|
||||
receiving host's `services.hyperhive.snapshotStore.port`.
|
||||
|
||||
Defaulted (unlike `address`) because it is a shared convention
|
||||
both sides read from the same option docs — whereas an address
|
||||
is deployment-specific and cannot be guessed.
|
||||
'';
|
||||
};
|
||||
};
|
||||
|
||||
# How this hive reaches the swarm queue to offer its own status
|
||||
# (hive-c0re's `swarm_status`): the token endpoint below, which follows
|
||||
# the swarm's IdP address wherever that is, and the queue's URL under
|
||||
|
|
|
|||
Loading…
Reference in a new issue