Some checks failed
Build and Test / build (debug, clang) (push) Has been cancelled
Build and Test / build (debug, gcc) (push) Has been cancelled
Build and Test / build (release, clang) (push) Has been cancelled
Build and Test / build (release, gcc) (push) Has been cancelled
Build and Test / macos (push) Has been cancelled
Build and Test / docker (push) Has been cancelled
Pillar data (deploy/salt/pillar/) + README for the deploying agent: hub-and-spoke (sensor export -> central fleet train + overlay -> distribute), role assignment, CLI surface, security invariants, and the honest gaps (no `fleet overlay` CLI yet, node_id not wired, no multi-node/docker-swarm validation). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
3.6 KiB
3.6 KiB
Strawberry distributed deployment (Salt) — contract for the deploying agent
This directory holds the Salt pillar (data contract) for deploying Strawberry's distributed learning. The SLS states (install/config/egress/distribute) are to be authored separately (by the deploying agent) and consume this pillar.
pillar/strawberry.sls— the full pillar schema with defaults + required fields.pillar/top.sls— example role assignment (sensor vs central).
Architecture (what this release actually is)
Hub-and-spoke, NOT peer-to-peer.
sensor nodes central node
------------ ------------
daemon -> store (also a sensor, optionally)
strawberry export --out bundle.sbx --(Salt pull)--> bundle_dir/
strawberry fleet train bundle_dir --out shadow.sbm
merge_rarity_overlay(...) -> fleet-overlay.sbo [NO CLI YET]
model_dir/ <--(Salt push)---------- distribute: shadow.sbm + fleet-overlay.sbo
(round 2+ exports carry fleet_bits)
- There is no node-to-node transport, no gossip/DHT, no decentralized aggregation.
- Egress is central-pull (Salt orchestration /
cp.pushof a sealed, redacted bundle). The bundle artifact contract is stable, so an object store / mTLS collector can replace the pull later without daemon changes. - Promotion is operator-only, never automatic. States distribute
shadow.sbm; a model only acts afterstrawberry model promotepasses the pre-registered gate (docs/evaluation/stage4-promotion-gate.md). Keep promotion a human step.
CLI surface the states invoke (exists today on main)
strawberry export <store_dir> --out <file>— sensor egress. Auto-includes fleet rarity when<model_dir>/fleet-overlay.sbois present.strawberry fleet train <bundle_dir> --out <model.sbm>— central merge + train shadow model.
GAPS the deploying agent must close (honest status)
- No
strawberry fleet overlayCLI.merge_rarity_overlay()(sum per-node rarity sketches ->fleet-overlay.sbo) is a library function only — there is no CLI verb to produce the overlay on the central node. The overlay step in the pillar (central.overlay_out) cannot run until that verb is added (a small increment:strawberry fleet overlay <bundle_dir> --out fleet-overlay.sbo). node_idis not yet a daemon config key. Export stampsnode_uidfromread_node_uid("")(machine-id/hostname hash). Wiringconfig.node_idthrough to export is a follow-up; until then,config.node_idin the pillar is advisory.- No
--sinceincremental export — each export is a full pass over the store. - No multi-node validation. The pipeline is unit/component + single-binary tested; it has
not been run as a real multi-node fleet (N daemons -> central pull -> merge across hosts
-> distribute -> re-export). A docker-swarm end-to-end is the recommended acceptance test
before fleet rollout (the plan's deferred
docker-livemilestone).
Paths (binary defaults)
- store /
db_path:/var/lib/strawberry/evidence model_dir:/var/lib/strawberry/model(holdsshadow.sbm,promoted.sbm,rarity.state,fleet-overlay.sbo)
Security invariants the states must preserve
capture_redact_cmdline: true(argv redaction before storage) — do not disable on a fleet.- No new inbound listener on sensor nodes — export is an outbound read-only artifact pulled over the trusted channel; the daemon sandbox stays intact.
- Reviewed, sha256-pinned binaries only; verify the pin before install.