mirrors/seaweedfs
1
0
Fork 0
mirror of https://github.com/seaweedfs/seaweedfs.git synced 2026-05-22 09:41:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

G5 kickoff §7a: m01 + M02 infrastructure verification (QA pre-ratify)

Browse Source 
Per QA infra-check round 2026-04-26, surfaces real readiness gaps
before architect ratifies G5-4 schedule:

m01 (192.168.1.181 — primary node):
  ✅ 32-day uptime; sudo password-less; 16 cores; 19 GiB RAM
  ✅ 177 GiB free disk; Go 1.26.2 installed
  ✅ iptables / netns / multi-process tools all available
  ✅ T2 m01 NVMe script template available as pattern reference

M02 (192.168.1.184 — replica node):
  ✅ Reachable from m01 (0.92ms); same kernel; 178 GiB free disk
  ❌ Go NOT installed — must scp binaries from m01

Implication for G5-4:
  Build binaries on m01, scp to M02. Same cross-node binary pattern
  T2 already uses for its iSCSI target deployment. G5-4 skeleton at
  seaweed_block/scripts/iterate-m01-replicated-write.sh implements
  this build-then-scp flow.

No infrastructure blockers. Architecture ready as soon as G5 mini-plan
ratifies scenario list.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
pingqiu
2026-04-26 09:38:57 -07:00
parent a792ed67e5
commit ce78fea36f
1 changed files with 24 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
sw-block/design/v3-phase-15-g5-kickoff.md
View File

@@ -153,6 +153,30 @@ QA reviews mini-plan + scenario catalogue + m01 script; sw reviews framework-pri
---
## §7a m01 + M02 infrastructure verification (QA pre-ratification check 2026-04-26)
QA verified m01 + M02 infrastructure readiness for G5-4 before architect ratifies the batch shape. Findings:
| Surface | m01 (192.168.1.181) | M02 (192.168.1.184) |
|---|---|---|
| Reachability | ✅ 32-day uptime; healthy load avg 0.5 | ✅ 0.92ms ping latency from m01 |
| Kernel | 6.17.0-19-generic | same |
| Disk space | 177 GiB free on /opt | 178 GiB free on /opt |
| Sudo | ✅ password-less (iptables manipulation OK for fault injection) | not verified yet |
| iptables | ✅ runnable | ✅ same kernel; assume same |
| Network namespaces | ✅ supported | ✅ same kernel |
| Multi-process tools | ✅ pgrep / lsof / fuser / ss / netstat | ✅ same kernel |
| CPUs / memory | 16 cores / 19 GiB free | not verified |
| **Go installed** | ✅ Go 1.26.2 at /snap/bin/go | ❌ **NOT installed** |
| T2 m01 script template | ✅ `iterate-m01-nvme.sh` 18.5 KiB | (pattern confirmed) |
| Existing build artifacts | (clean for G5) | `iscsi-target-linux` + `nvme-test-linux` (T2 binaries deployed cross-node) |
**Implication for G5-4 script design**: build binaries on m01 (Go installed), then `scp` to M02 (no Go installed). T2 already uses this cross-node binary pattern for its iSCSI target testing — G5-4 inherits the pattern. **Skeleton at `seaweed_block/scripts/iterate-m01-replicated-write.sh` (DRAFT v0.1) implements this build-then-scp flow.**
**No infrastructure blockers for G5-4.** The architecture is ready for G5-4 hardware first-light as soon as G5 mini-plan ratifies the scenario list.
---
## §8 Open issues blocking ratification
1. **Architect resolution of §2** — accept §2.1/§2.2 scope boundary