Topology mapped one NUMA node per CPU, so on a 2-socket SNC2 host (nodes 0-3) node 1 went to CPU1 and nodes 2-3 got no CPU: the second BlueField-3, four GPUs and several NICs rendered unattached. Use numa-nodes.txt (node=N package=P), now carried by parser v26 as TopologyEvidence.NUMANodes; without it, fall back to contiguous per-socket blocks of zero-based node ids. Pin parser v26.0.0. ADL-082. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
LOGPile Bible
bible-local/ is the project-specific source of truth for LOGPile.
Keep top-level docs minimal and put maintained architecture/API contracts here.
Rules
- Documentation language: English only
- Update relevant bible files in the same change as the code
- Record significant architectural decisions in
10-decisions.md - Do not duplicate shared rules from
bible/
Read order
| File | Purpose |
|---|---|
| 01-overview.md | Product scope, modes, non-goals |
| 02-architecture.md | Runtime structure, state, main flows |
| 04-data-models.md | Stable data contracts and canonical inventory |
| 03-api.md | HTTP endpoints and response contracts |
| 05-collectors.md | Live collection behavior |
| 06-parsers.md | Archive parser framework and vendor coverage |
| 07-exporters.md | Raw export, Reanimator export, batch convert |
| docs/hardware-ingest-contract.md | Reanimator ingest schema mirrored locally |
| docs/privacy-scan.md | Customer-data / anonymization scan of ingested sources |
| docs/log-sanitization.md | In-place, length-preserving redaction of customer data |
| 08-build-release.md | Build and release workflow |
| 09-testing.md | Test expectations and regression rules |
| 10-decisions.md | Architectural Decision Log |
Fast orientation
- Entry point:
cmd/logpile/main.go - HTTP layer:
internal/server/ - Core contracts:
git.mchus.pro/reanimator/parser/v20/models - Live collection:
internal/collector/ - Archive parsing and Redfish analysis: external module
git.mchus.pro/reanimator/parser/v20(see06-parsers.md) - Export conversion:
internal/exporter/ - Frontend consumer:
web/static/js/app.js
Maintenance rule
If a document becomes stale, either fix it immediately or delete it. Stale docs are worse than missing docs.