Files
logpile/bible-local/02-architecture.md
Mikhail ChusavitinandClaude Opus 5.5 cb2e38223e chore: update parser module to v38.0.0, script parser bumps
Move logpile to git.mchus.pro/reanimator/parser/v38 v38.0.0 (ADL-085).
Add scripts/bump-parser.sh, which bumps the parser, tests, commits, tags
the release as v<counter>.<parser major>, pushes and builds (ADL-086).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-26 18:07:28 +03:00

4.2 KiB

02 — Architecture

Runtime stack

Layer Implementation
Language Go 1.22+
HTTP net/http + http.ServeMux
UI Embedded templates and static assets via go:embed
State In-memory only
Build CGO_ENABLED=0, single binary

Default port: 8082

Audit result rendering is delegated to embedded reanimator/chart, vendored as git submodule internal/chart. LOGPile remains responsible for upload, collection, parsing, normalization, and Reanimator export generation.

Code map

cmd/logpile/main.go          entrypoint and CLI flags
internal/server/             HTTP handlers, jobs, upload/export flows
internal/collector/          live Redfish/BMC collection, acquisition-time profile tuning
internal/analyzer/           shared analysis helpers
internal/exporter/           CSV and Reanimator conversion
internal/chart/              vendored `reanimator/chart` viewer submodule
internal/topology/           standalone topology.json builder and static SVG renderer
web/                         embedded UI assets

Archive parsing, Redfish replay/analysis, and the models data contracts live in the external module git.mchus.pro/reanimator/parser/v38 (see 06-parsers.md, ADL-080) — not in this tree anymore.

The topology view is owned by LOGPile, not by the chart submodule. The main UI opens GET /topology/current in a separate browser tab. The renderer consumes a standalone topology.json document built from the normalized Reanimator projection plus optional static evidence imported from Bee support bundles. It does not poll telemetry or execute host commands.

Server state

internal/server.Server stores:

Field Purpose
result Current AnalysisResult shown in UI and used by exports
detectedVendor Parser/collector identity for the current dataset
rawExport Reopenable raw-export package associated with current result
jobManager Shared async job state for collect and convert flows
collectors Registered live collectors (redfish, ipmi)
convertOutput Temporary ZIP artifacts for batch convert downloads

State is replaced only on successful upload or successful live collection. Failed or canceled jobs do not overwrite the previous dataset.

Main flows

Upload

  1. POST /api/upload receives multipart field archive
  2. The server resolves the source family
  3. JSON inputs are checked for raw-export package or AnalysisResult snapshot
  4. Non-JSON archives go through parser.NewService().AnalyzeArchivePayload(...) (git.mchus.pro/reanimator/parser/v38)
  5. Archive metadata is normalized onto AnalysisResult
  6. Result becomes the current in-memory dataset

Live collect

  1. POST /api/collect validates request fields
  2. Server creates an async job and returns 202 Accepted
  3. Selected collector gathers raw data
  4. For Redfish, collector runs minimal discovery, matches Redfish profiles, and builds an acquisition plan
  5. Collector applies profile tuning hints (for example crawl breadth, prefetch, bounded plan-B passes)
  6. Collector saves raw_payloads.redfish_tree plus acquisition diagnostics
  7. Result is normalized, source metadata applied, and state replaced on success

Batch convert

  1. POST /api/convert accepts multiple files
  2. Each supported file is analyzed independently
  3. Successful results are converted to Reanimator JSON
  4. Outputs are packaged into a temporary ZIP artifact
  5. Client polls job status and downloads the artifact when ready

Redfish design rule

Live Redfish collection and offline Redfish re-analysis must use the same replay path. The collector first captures raw_payloads.redfish_tree, then the replay logic builds the normalized result.

Redfish is being split into two coordinated phases:

  • acquisition: profile-driven snapshot collection strategy
  • analysis: replay over the saved snapshot with the same profile framework

PCI IDs lookup

Lookup order:

  1. Embedded pci.ids inside git.mchus.pro/reanimator/parser/v38/pciids
  2. ./pci.ids
  3. /usr/share/hwdata/pci.ids
  4. /usr/share/misc/pci.ids
  5. /opt/homebrew/share/pciids/pci.ids
  6. Extra paths from LOGPILE_PCI_IDS_PATH

Later sources override earlier ones for the same IDs.