跳转到文档内容
版本:下一个

Diagram Inventory

This page catalogs every diagram across the repository: docs/, blog/, i18n/, versioned_docs/, and static/. It serves as the input for the diagram redraw work tracked in #421.

Scope note: Blog event-photo images (KubeCon booth shots, keynote photos, speaker photos) are excluded - they are photographs, not technical diagrams. Only images that communicate architecture, flow, or system behavior are listed here.


Legend

FieldValues
FormatSVG, PNG, JPG, JPEG, PlantUML
Statuscurrent - accurate and up to date; outdated - terminology or structure stale; unknown - content not verifiable without visual inspection; screenshot - UI capture, not a diagram
Source filePath to editable source (.plantuml, .drawio, .graffle), or none
Control/data planeseparated - clearly distinct; partial - mixed; n/a - not applicable to this diagram type

1. Core Concepts - Architecture and Flow Diagrams

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/common/core-concepts/architect.jpgJPGdocs/core-concepts/architecture.md, i18n/zh/.../core-concepts/architecture.md, all versioned versionsnoneoutdated (JPG, not SVG; no source)not separated
static/img/docs/common/core-concepts/device-plugin-flow-en.svgSVGdocs/core-concepts/gpu-virtualization.mddocs/core-concepts/device-plugin-flow.plantumlcurrentn/a (sequence diagram)
static/img/docs/common/core-concepts/device-plugin-flow.svgSVGi18n/zh/.../core-concepts/gpu-virtualization.mdi18n/zh/.../core-concepts/device-plugin-flow.plantumlcurrentn/a (sequence diagram)
static/img/docs/common/core-concepts/hami-architecture-en.svgSVGdocs/core-concepts/gpu-virtualization.mddocs/core-concepts/hami-architecture.plantumlcurrentpartial
static/img/docs/common/core-concepts/hami-architecture.svgSVGi18n/zh/.../core-concepts/gpu-virtualization.mdi18n/zh/.../core-concepts/hami-architecture.plantumlcurrentpartial

Notes:

  • architect.jpg is the primary architecture overview diagram used on docs/core-concepts/architecture.md. It is in JPG format with no editable source. It must be redrawn as SVG with a source file.
  • The two PlantUML-based SVGs (device-plugin-flow-*.svg, hami-architecture-*.svg) have source files and are in good shape. They should be checked for control/data plane separation when redrawn.

2. Developer Docs - HAMi Core Design

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/common/developers/hami-core-design/hami-arch.pngPNGdocs/developers/hami-core-design.md, zh equivalentnoneunknownnot separated
static/img/docs/common/developers/hami-core-design/hami-core-position.pngPNGdocs/developers/hami-core-design.md, zh equivalentnoneunknownnot separated
static/img/docs/common/developers/hami-core-design/sample-nvidia-smi.pngPNGdocs/developers/hami-core-design.md, zh equivalentnonescreenshotn/a

Notes:

  • hami-arch.png and hami-core-position.png have no source files. Both must be recreated as SVG with editable source.
  • sample-nvidia-smi.png is a terminal screenshot illustrating virtualized GPU memory output. It is not an architectural diagram and does not require redrawing, but may need refreshing if command output changes.

3. Developer Docs - Scheduling

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/common/developers/scheduling/scheduler-policy-story.pngPNGdocs/developers/scheduling.md, zh equivalentnoneunknownnot separated
static/img/docs/common/developers/scheduling/node-scheduler-policy-demo.pngPNGdocs/developers/scheduling.md, zh equivalentnoneunknownnot separated
static/img/docs/common/developers/scheduling/gpu-scheduler-policy-demo.pngPNGdocs/developers/scheduling.md, zh equivalentnoneunknownnot separated

Notes:

  • All three scheduling diagrams are PNG with no source files. They must be redrawn as SVG.
  • These diagrams describe the Binpack and Spread scheduling policy logic. They are visible in the latest docs/developers/scheduling.md and its zh counterpart.

4. Developer Docs - Protocol

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/common/developers/protocol/protocol-register.pngPNGdocs/developers/protocol.md (EN only)noneunknownnot separated
static/img/docs/common/developers/protocol/device-registration.pngPNGi18n/zh/.../developers/protocol.md (ZH only)noneunknownnot separated
static/img/docs/common/developers/protocol/task-dispatch.pngPNGi18n/zh/.../developers/protocol.md (ZH only)noneunknownnot separated

Inconsistency found: The EN docs/developers/protocol.md references only protocol-register.png. The ZH version references device-registration.png and task-dispatch.png - two different files that do not appear in the EN doc. The EN doc appears to be missing the task dispatch diagram. This inconsistency must be resolved before redrawing.


5. Developer Docs - WebUI Architecture

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/common/developers/hami-webui-architecture-diagram.svgSVGdocs/developers/hami-webui-development-guide.md, zh equivalent, blog/hami-webui-v1-1-0-release/index.mdnonecurrentnot separated

Notes:

  • This diagram is already SVG, which is correct. However, it has no editable source file (no .drawio or .graffle). A source file must be added to static/img/src/ when it is next updated.

6. Developer Docs - Dynamic MIG

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/en/dynamic-mig/hami-dynamic-mig-structure.pngPNGdocs/developers/dynamic-mig.md, zh equivalent, all versioned versionsnoneunknownnot separated
static/img/docs/en/dynamic-mig/hami-dynamic-mig-procedure.pngPNGdocs/developers/dynamic-mig.md, zh equivalent, all versioned versionsnoneunknownnot separated

Notes:

  • Both images are PNG, no source files. Referenced from both EN and ZH current docs and all versioned docs.
  • These were added recently (master update includes them as new files). Their accuracy relative to the current codebase is unknown.

7. Developer Docs - Kunlunxin Topology

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/common/developers/kunlunxin-topology/kunlunxin-filter.pngPNGdocs/developers/kunlunxin-topology.md, zh equivalentnoneunknownnot separated

8. Key Features Diagrams

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/common/key-features/example.pngPNGdocs/key-features/device-sharing.md, zh equivalentnoneunknownn/a
static/img/docs/common/key-features/hard-limit.jpgJPGdocs/key-features/device-resource-isolation.md, zh equivalentnoneunknownn/a

Versioned-only key features diagrams (not referenced in current docs/):

Image pathFormatReferenced inSource fileStatus
static/img/docs/common/key-features/features/overall-relationship.pngPNGversioned_docs/version-v2.4.1, version-v2.5.0 onlynoneorphaned in current docs
static/img/docs/common/key-features/features/overall-scheduling.pngPNGversioned onlynoneorphaned in current docs
static/img/docs/common/key-features/features/overall-rescheduling.pngPNGversioned onlynoneorphaned in current docs
static/img/docs/common/key-features/features/cluster-failover.pngPNGversioned onlynoneorphaned in current docs
static/img/docs/common/key-features/features/unified-operation.pngPNGversioned onlynoneorphaned in current docs
static/img/docs/common/key-features/features/unified-search.pngPNGversioned onlynoneorphaned in current docs
static/img/docs/common/key-features/features/unified-access.pngPNGversioned onlynoneorphaned in current docs
static/img/docs/common/key-features/features/unified-resourcequota.pngPNGversioned onlynoneorphaned in current docs
static/img/docs/common/key-features/features/service-governance.pngPNGversioned onlynoneorphaned in current docs

Notes:

  • The 9 features/ images are referenced only from versioned_docs/version-v2.4.1/key-features/features.md and version-v2.5.0/key-features/features.md. They are not present in any current docs/ page. They must be kept for versioned doc rendering but are not candidates for redrawing in the current doc set.
  • hard-limit.jpg is JPG. Should be converted to PNG or SVG.

9. Mindmaps

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/en/mindmap/hami-vgpu-mind-map-en.pngPNGdocs/developers/mindmap.md, all versioned versionsnoneunknownn/a
static/img/docs/zh/mindmap/hami-vgpu-mind-map-zh.pngPNGi18n/zh/.../developers/mindmap.md, all versioned versionsnoneunknownn/a

Notes:

  • Both mindmaps carry the title "HAMi VGPU mind map". The "VGPU" scope is narrower than HAMi's current support surface, which now covers Cambricon MLU, Hygon DCU, Kunlunxin XPU, Metax GPU, Iluvatar Corex, and Ascend NPU in addition to NVIDIA VGPU.
  • Neither mindmap has an editable source file. Updating them requires a full redraw.
  • Full content accuracy cannot be assessed from this inventory without visual inspection of the PNG files. A maintainer familiar with current HAMi architecture must review before any decision to update or remove.
  • Tracked for redesign in issue #414.

10. Device Userguide Diagrams

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/common/userguide/metax-device/metax-gpu/metax-topology.jpgJPGdocs/userguide/metax-device/metax-gpu/enable-metax-gpu-schedule.md, zh equivalentnoneunknownnot separated
static/img/docs/common/userguide/metax-device/metax-gpu/metax-spread.jpgJPGdocs/userguide/metax-device/metax-gpu/enable-metax-gpu-schedule.md, zh equivalentnoneunknownnot separated
static/img/docs/common/userguide/metax-device/metax-gpu/metax-binpack.jpgJPGdocs/userguide/metax-device/metax-gpu/enable-metax-gpu-schedule.md, zh equivalentnoneunknownnot separated
static/img/docs/common/userguide/kunlunxin-device/kunlunxin-topology.jpgJPGdocs/userguide/kunlunxin-device/enable-kunlunxin-schedule.md, docs/developers/kunlunxin-topology.md, zh equivalentsnoneunknownnot separated

Notes:

  • All device userguide diagrams are JPG. They must be redrawn as SVG per WS4 requirements.
  • Metax GPU diagrams cover PCIe topology, Spread scheduling policy, and Binpack scheduling policy.
  • Kunlunxin topology diagram shows NUMA node connections on the P800 server.

11. WebUI Screenshots

These are UI captures, not architecture or flow diagrams. They do not require redrawing but may need refreshing when the WebUI is updated.

Image pathFormatReferenced in
static/img/docs/en/userguide/webui-overview.pngPNGdocs/userguide/hami-webui-user-guide.md, blog/hami-webui-v1-1-0-release/index.md
static/img/docs/en/userguide/webui-node-list.pngPNGsame
static/img/docs/en/userguide/webui-node-detail.pngPNGsame
static/img/docs/en/userguide/webui-accelerator-list.pngPNGsame
static/img/docs/en/userguide/webui-accelerator-detail.pngPNGsame
static/img/docs/en/userguide/webui-workload-list.pngPNGsame
static/img/docs/en/userguide/webui-workload-detail.pngPNGsame
static/img/docs/zh/userguide/webui-*.png (7 files)PNGzh userguide

12. Contributor Guide Diagram

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/docs/common/contributor/github-workflow/git-workflow.pngPNGdocs/contributor/github-workflow.md, zh equivalentnoneunknownn/a

13. Homepage Component Diagrams

Image pathFormatReferenced inSource fileStatusControl/data plane
static/img/gpu-sharing-diagram.svgSVGsrc/components/BeforeAfterComparison.jsnoneunknownnot separated
static/img/gpu-sharing-diagram-zh.svgSVGsrc/components/BeforeAfterComparison.jsnoneunknownnot separated

Notes:

  • These SVGs are rendered in the homepage comparison component. They are already in SVG format. Source files (.drawio or similar) are missing.

14. Blog - Technical Diagram

Image pathFormatReferenced inSource fileStatus
static/img/blog/flowchart.jpegJPEGblog/2024-12-31-post/index.mdnoneunknown

Notes:

  • blog/2024-12-31-post/index.md also references an external image hosted on GitHub (raw.githubusercontent.com). External image hosting is fragile and should be migrated to static/img/.

Known Issues Found During Inventory

Broken image reference

docs/contributor/contribute-docs.md (line 153) references:

/img/docs/common/architecture/hami-arch.png

The directory static/img/docs/common/architecture/ does not exist. The file at that path does not exist. The correct path for the HAMi core architecture image is:

/img/docs/common/developers/hami-core-design/hami-arch.png

This is a broken link that will cause a missing image in the rendered page.

Protocol diagram inconsistency (EN vs. ZH)

The EN docs/developers/protocol.md references only protocol-register.png (device registration).

The ZH i18n/zh/.../developers/protocol.md references both device-registration.png and task-dispatch.png.

The EN page is missing the task dispatch diagram. This must be reconciled before either page is considered complete.


Summary: Diagrams Requiring Redraw as SVG

Priority list for the redraw work in #421:

PriorityImageCurrent formatReason
Highstatic/img/docs/common/core-concepts/architect.jpgJPGPrimary architecture overview; main entry point for new users
Highstatic/img/docs/common/developers/hami-core-design/hami-arch.pngPNGCore internal design diagram, no source
Highstatic/img/docs/common/developers/hami-core-design/hami-core-position.pngPNGCore internal design diagram, no source
Highstatic/img/docs/en/mindmap/hami-vgpu-mind-map-en.pngPNGOutdated scope ("VGPU" only), no source - see #414
Highstatic/img/docs/zh/mindmap/hami-vgpu-mind-map-zh.pngPNGSame as above
Mediumstatic/img/docs/common/developers/scheduling/scheduler-policy-story.pngPNGNo source
Mediumstatic/img/docs/common/developers/scheduling/node-scheduler-policy-demo.pngPNGNo source
Mediumstatic/img/docs/common/developers/scheduling/gpu-scheduler-policy-demo.pngPNGNo source
Mediumstatic/img/docs/common/developers/protocol/protocol-register.pngPNGNo source; EN/ZH inconsistency must be resolved first
Mediumstatic/img/docs/common/developers/protocol/device-registration.pngPNGNo source; ZH-only
Mediumstatic/img/docs/common/developers/protocol/task-dispatch.pngPNGNo source; ZH-only, missing from EN
Mediumstatic/img/docs/en/dynamic-mig/hami-dynamic-mig-structure.pngPNGNo source
Mediumstatic/img/docs/en/dynamic-mig/hami-dynamic-mig-procedure.pngPNGNo source
Lowstatic/img/docs/common/userguide/metax-device/metax-gpu/metax-topology.jpgJPGDevice-specific, no source
Lowstatic/img/docs/common/userguide/metax-device/metax-gpu/metax-spread.jpgJPGDevice-specific, no source
Lowstatic/img/docs/common/userguide/metax-device/metax-gpu/metax-binpack.jpgJPGDevice-specific, no source
Lowstatic/img/docs/common/userguide/kunlunxin-device/kunlunxin-topology.jpgJPGDevice-specific, no source
Lowstatic/img/docs/common/key-features/hard-limit.jpgJPGShould be PNG or SVG
Lowstatic/img/docs/common/developers/kunlunxin-topology/kunlunxin-filter.pngPNGNo source
Lowstatic/img/docs/common/contributor/github-workflow/git-workflow.pngPNGNo source
Lowstatic/img/gpu-sharing-diagram.svgSVGAlready SVG; missing source file only
Lowstatic/img/gpu-sharing-diagram-zh.svgSVGAlready SVG; missing source file only
CNCFHAMi 是 CNCF Sandbox 项目