mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-20 13:30:46 +02:00
pingqiuandClaude Opus 4.6
3ba622d9e0
Covers three personas (developer/operator/platform engineer) with: - One-command setup: weed server -block (10 seconds to first volume) - Shell commands: block.list, block.status, block.health, block.create, etc. - REST API: /block/volumes CRUD, /block/health - Observability: Prometheus metrics, alerting rules, Grafana dashboard - Actionable error messages (every error tells you what to do next) - Dry-run by default for all destructive operations Competitive comparison: 10s setup vs Ceph 30min, 13.5x write IOPS, single binary for object + block storage. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
sw-block
Private WAL V2 and standalone block-service workspace.
Purpose:
- keep WAL V2 design/prototype work isolated from WAL V1 production code in
weed/storage/blockvol - allow private design notes and experiments to evolve without polluting V1 delivery paths
- keep the future standalone
sw-blockproduct structure clean enough to split into a separate repo later if needed
Suggested layout:
design/: shared V2 design docsprototype/: code prototypes and experiments.private/: private notes, phase development, roadmap, and non-public working material
Repository direction:
- current state:
sw-block/is an isolated workspace insideseaweedfs - likely future state:
sw-blockbecomes a standalone sibling repo/product - design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths