Skip to content

Appendix B

Reference Map

Appendix

Where each architecture chapter gets its source material.

This appendix maps the HTML architecture chapters to the current design sources used to write them. Architecture authority wins over operational guides when the two disagree.

Reference Map Aid

Use this appendix as a compact reviewer aid: first find the chapter that owns the concept, then check the primary source row for the design authority, and finally use operational guides only for current command spelling or deployment examples.

Reviewer source order
architecture chapter
checks
architecture authority doc
then
interface spec
then
operations guide
Chapter Primary Sources
00-02 Reading Guide, Platform Overview, Components And Ownership, and current component interface summaries.
03 Linux Host Control And Data Plane plus the kernel UAPI and gateway route implementation.
04 Metadata Authority and the SBS service/data ownership boundary.
05-06 Logical Storage Geometry and Logical-To-Physical Mapping.
07 Replicated Backend and shared gateway/SBS interface summaries.
08 Erasure Coding Backend and topology placement summaries.
09 Write Visibility And Ordering and the storage substrate visibility model.
10-11 Read Views, Snapshots, And Clones and Reachability And GC.
12 Zero, Discard, And Reclaim.
13 Kernel-Gateway Dataplane.
14 Topology, Placement, And Expansion.
15 Observability And Validation plus release evidence summaries.
16 Kubernetes/CSI Integration Case.
17 Edition And Release Boundaries and current public support matrix wording.
Appendix C kernel/uapi/namrbd_netlink.h, gateway/httpapi/server.go, cmd/namrbd-iscsi-gateway, cmd/sbsctl, iscsi, third_party/gotgt, proto/sbs/admin/v1/*.proto, proto/sbs/v1/volume.proto, cmd/sbs-service/main.go, cmd/sbs-data/main.go, and component interface summaries.

First Edition Rule

This HTML edition intentionally presents the current architecture. Every chapter should trace to at least one current authority source. Earlier project notes remain valuable for project history, and operational guides are useful for current user-visible names, but neither is used as first-edition teaching flow when it conflicts with the current authority set.

\<- Previous Next: Interface Specifications ->