mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-10-12 01:07:35 +02:00
One named workload validation package for RF=2 sync_all: - Scenario: cp13-8-real-workload-validation.yaml (6 phases) - ext4 proof: write 200 files → failover → fsck + file count + md5sum diff - pgbench proof: TPC-B on promoted replica (database durability) - Disturbance: one bounded failover (kill primary, promote replica) Workload envelope doc: phase-13-cp8-workload-validation.md - Named topology, transport, workloads, disturbance, exclusions - Pass criteria: fsck passes, 200 files, checksums match, pgbench TPS > 0 - Maps each pass criterion to accepted CP13-1..7 semantics - Explicit non-claims: not rollout approval, not NVMe, not soak, not CP13-9 Reuses existing infrastructure: - cp85-db-ext4-fsck.yaml pattern (extended with checksums + pgbench) - benchmark-pgbench.yaml actions (pgbench_init/pgbench_run) Must run on real hardware (m01/M02). Cannot run in unit test harness. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
.private
Private working area for sw-block.
Use this for:
- phase development notes
- roadmap/progress tracking
- draft handoff notes
- temporary design comparisons
- prototype scratch work not ready for
design/orprototype/
Recommended layout:
.private/phase/: phase-by-phase development notes.private/roadmap/: short-term and medium-term execution notes.private/handoff/: notes forsw,qa, or future sessions
Phase protocol:
- each phase should normally have:
phase-xx.mdphase-xx-log.mdphase-xx-decisions.md
- details are defined in
.private/phase/README.md
Promotion rules:
- stable vision/design docs go to
../design/ - real prototype code stays in
../prototype/ .private/is for working material, not source of truth