Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 3 additions & 6 deletions .github/workflows/docs-health.yml
Original file line number Diff line number Diff line change
Expand Up @@ -33,12 +33,9 @@ jobs:
run: npm run format:check

- name: Build Site
env:
DOCUSAURUS_SITE_URL: http://127.0.0.1:3000
run: npm run build

- name: Broken Internal Link Check
run: |
npx --yes linkinator ./build --recurse --skip "^https?://" --verbosity error 2>&1 | tee linkinator-output.txt
if grep -q "BROKEN" linkinator-output.txt; then
echo "::error::Broken internal links found"
exit 1
fi
run: bash scripts/check-links.sh
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -5,5 +5,6 @@ node_modules
.hugo_build.lock
.idea
build
.worktrees/
.DS_Store
changelog/source
2 changes: 1 addition & 1 deletion blog/hami-at-kubecon-eu-2026/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@ During the conference, the HAMi community will continue to curate and publish re
Stay connected:

- [HAMi GitHub Repository](https://github.com/Project-HAMi/HAMi)
- [HAMi Community Website](https://project-hami.io)
- [HAMi Community Website](/)

If you'll be in Amsterdam, come find us at Project Pavilion.

Expand Down
2 changes: 1 addition & 1 deletion blog/hami-cncf-incubating/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Our sincere thanks to CNCF TOC Chair [Karena Angell](https://www.linkedin.com/fe

HAMi is a heterogeneous compute virtualization and scheduling middleware for Kubernetes. Through container-level hard isolation, it finely partitions GPU memory and compute so that multiple workloads can safely share a single accelerator. Founded by maintainers [Xiao Zhang](https://github.com/wawa0210) and [Mengxuan Li](https://github.com/archlitchi), it is built by developers worldwide under CNCF governance.

Today, HAMi is used by hundreds of organizations across a dozen-plus accelerators including NVIDIA, Ascend, Cambricon, Hygon, Moore Threads, Enflame, Kunlunxin, MetaX, AWS Neuron, and Vastai (see the [supported device list](https://project-hami.io/docs/userguide/device-supported)). [CNCF case studies](/case-studies) document production practices at China Merchants Bank, SNOW Corp., NIO, KE Holdings, DaoCloud, SF Technology, and PREP EDU, spanning finance, automotive, mobility, logistics, education, and cloud services. HAMi-core integrates with the Kubernetes default scheduler, [Volcano](https://github.com/volcano-sh/volcano/blob/master/docs/user-guide/how_to_use_gpu_sharing.md), [Kueue](https://github.com/kubernetes-sigs/kueue), [Koordinator](https://koordinator.sh/docs/user-manuals/device-scheduling-gpu-share-with-hami), and the [KAI Scheduler](/blog/hami-core-adopted-by-nvidia-kai-scheduler).
Today, HAMi is used by hundreds of organizations across a dozen-plus accelerators including NVIDIA, Ascend, Cambricon, Hygon, Moore Threads, Enflame, Kunlunxin, MetaX, AWS Neuron, and Vastai (see the [supported device list](/docs/userguide/device-supported)). [CNCF case studies](/case-studies) document production practices at China Merchants Bank, SNOW Corp., NIO, KE Holdings, DaoCloud, SF Technology, and PREP EDU, spanning finance, automotive, mobility, logistics, education, and cloud services. HAMi-core integrates with the Kubernetes default scheduler, [Volcano](https://github.com/volcano-sh/volcano/blob/master/docs/user-guide/how_to_use_gpu_sharing.md), [Kueue](https://github.com/kubernetes-sigs/kueue), [Koordinator](https://koordinator.sh/docs/user-manuals/device-scheduling-gpu-share-with-hami), and the [KAI Scheduler](/blog/hami-core-adopted-by-nvidia-kai-scheduler).

This milestone was made possible by a global community of nearly 500 contributors from dozens of countries. [Dynamia](https://www.dynamia.ai), [DaoCloud](https://www.daocloud.io), [4Paradigm](https://www.4paradigm.com), [NVIDIA](https://www.nvidia.com), and [Huawei Cloud](https://www.huawei.com), together with many individual developers, user enterprises, and ecosystem partners, have each made irreplaceable contributions.

Expand Down
2 changes: 1 addition & 1 deletion blog/hami-core-adopted-by-nvidia-kai-scheduler/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ A simple way to understand HAMi's position:
- **KAI Scheduler** decides "who uses which GPU, and when" (the scheduling layer).
- **HAMi** ensures "once allocated, that is all you get, and you cannot take more" (the isolation layer).

Only by combining the two do you get true production-grade GPU sharing. HAMi supports NVIDIA GPUs, Huawei Ascend NPUs, Cambricon MLUs, Hygon DCUs, Kunlun XPUs, and many other heterogeneous accelerators, making it the open source solution with the broadest coverage in cloud-native GPU virtualization. For the full list of supported accelerators, see the [HAMi documentation](https://project-hami.io/docs/userguide/device-supported).
Only by combining the two do you get true production-grade GPU sharing. HAMi supports NVIDIA GPUs, Huawei Ascend NPUs, Cambricon MLUs, Hygon DCUs, Kunlun XPUs, and many other heterogeneous accelerators, making it the open source solution with the broadest coverage in cloud-native GPU virtualization. For the full list of supported accelerators, see the [HAMi documentation](/docs/userguide/device-supported).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Hyphenate “open-source”.

open source should be hyphenated here; it reads better as open-source.

✏️ Suggested tweak
-... making it the open source solution with the broadest coverage in cloud-native GPU virtualization.
+... making it the open-source solution with the broadest coverage in cloud-native GPU virtualization.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Only by combining the two do you get true production-grade GPU sharing. HAMi supports NVIDIA GPUs, Huawei Ascend NPUs, Cambricon MLUs, Hygon DCUs, Kunlun XPUs, and many other heterogeneous accelerators, making it the open source solution with the broadest coverage in cloud-native GPU virtualization. For the full list of supported accelerators, see the [HAMi documentation](/docs/userguide/device-supported).
Only by combining the two do you get true production-grade GPU sharing. HAMi supports NVIDIA GPUs, Huawei Ascend NPUs, Cambricon MLUs, Hygon DCUs, Kunlun XPUs, and many other heterogeneous accelerators, making it the open-source solution with the broadest coverage in cloud-native GPU virtualization. For the full list of supported accelerators, see the [HAMi documentation](/docs/userguide/device-supported).
🧰 Tools
🪛 LanguageTool

[grammar] ~51-~51: Use a hyphen to join words.
Context: ...geneous accelerators, making it the open source solution with the broadest covera...

(QB_NEW_EN_HYPHEN)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@blog/hami-core-adopted-by-nvidia-kai-scheduler/index.md` at line 51, The
phrase in the blog copy should be hyphenated as open-source rather than open
source. Update the sentence in the markdown content near the HAMi accelerator
coverage paragraph so the wording reads naturally and consistently, keeping the
rest of the sentence unchanged.

Source: Linters/SAST tools


## Integration architecture: how HAMi and KAI Scheduler work together

Expand Down
2 changes: 1 addition & 1 deletion blog/hami-meetup-beijing-2025/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: "HAMi Meetup Beijing 2025 Recap"
date: "2025-12-27"
description: "HAMi Meetup Beijing was held on December 27, 2025. This article is available in Chinese only."
authors: [hami_community]
tags: ["Meetup"]
tags: ["HAMi", "Meetup", "Heterogeneous Compute", "GPU Virtualization", "Cloud Native"]
unlisted: true
---

Expand Down
11 changes: 10 additions & 1 deletion blog/hami-meetup-shanghai-2025/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,16 @@ title: "HAMi Meetup Shanghai 2025 Recap"
date: "2025-11-30"
description: "HAMi Meetup Shanghai was held on November 30, 2025. This article is available in Chinese only."
authors: [hami_community]
tags: ["Meetup"]
tags:
[
"Meetup",
"Shanghai",
"Heterogeneous Compute Scheduling",
"GPU Virtualization",
"Kubernetes",
"Domestic Compute",
"AI Training and Inference Optimization",
]
unlisted: true
---

Expand Down
12 changes: 11 additions & 1 deletion blog/hami-meetup-shenzhen-2026/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,17 @@ title: "HAMi Meetup Shenzhen 2026 Recap"
date: "2026-04-25"
description: "HAMi Meetup Shenzhen was held on April 25, 2026. This article is available in Chinese only."
authors: [hami_community]
tags: ["Meetup"]
tags:
[
"HAMi",
"Meetup",
"Shenzhen",
"GPU Virtualization",
"Heterogeneous Compute Scheduling",
"DRA",
"Cloud Native",
"AI Infrastructure",
]
unlisted: true
---

Expand Down
6 changes: 3 additions & 3 deletions blog/hami-v2-9-0-release/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -206,7 +206,7 @@ helm repo update
helm upgrade hami hami-charts/hami -n kube-system
```

For complete installation documentation, refer to: [https://project-hami.io/docs/installation/online-installation](https://project-hami.io/docs/installation/online-installation)
For complete installation documentation, refer to: [/docs/installation/online-installation](/docs/installation/online-installation)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Use descriptive anchor text for these links.

The relative targets are fine, but rendering raw paths makes the release note harder to scan.

✏️ Suggested tweak
-For complete installation documentation, refer to: [/docs/installation/online-installation](/docs/installation/online-installation)
+For complete installation documentation, refer to the [installation guide](/docs/installation/online-installation)

-Website: [/](/)
+Website: [HAMi homepage](/)

-Documentation: [/docs/](/docs/)
+Documentation: [HAMi docs](/docs/)

Also applies to: 242-242, 269-269

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@blog/hami-v2-9-0-release/index.md` at line 209, The release note links
currently use raw path text, which hurts readability; update the affected
markdown in the release note to use descriptive anchor text instead of exposing
the relative URL. Keep the same targets, but change the link labels in the
installation references and any other matching instances in this document so
readers can scan the note without seeing bare paths.


:::warning[Upgrade notes]

Expand Down Expand Up @@ -239,7 +239,7 @@ Since the v2.8.0 release, the HAMi website and documentation have undergone the

Thanks to [@mesutoezdil](https://github.com/mesutoezdil) for contributions to optimizing HAMi official documentation.

Website: [https://project-hami.io](https://project-hami.io)
Website: [/](/)

Website repository: [https://github.com/Project-HAMi/website](https://github.com/Project-HAMi/website)

Expand All @@ -266,6 +266,6 @@ We sincerely welcome more developers, users, and ecosystem partners to join the
- GitHub Release: [https://github.com/Project-HAMi/HAMi/releases/tag/v2.9.0](https://github.com/Project-HAMi/HAMi/releases/tag/v2.9.0)
- HAMi-DRA: [https://github.com/Project-HAMi/HAMi-DRA](https://github.com/Project-HAMi/HAMi-DRA)
- Volcano vGPU Device Plugin: [https://github.com/Project-HAMi/volcano-vgpu-device-plugin](https://github.com/Project-HAMi/volcano-vgpu-device-plugin)
- Documentation: [https://project-hami.io](https://project-hami.io)
- Documentation: [/docs/](/docs/)
- Community Discord (recommended): [https://discord.gg/Amhy7XmbNq](https://discord.gg/Amhy7XmbNq)
- Community CNCF Slack: [https://cloud-native.slack.com/archives/C07T10BU4R2](https://cloud-native.slack.com/archives/C07T10BU4R2)
2 changes: 1 addition & 1 deletion blog/kubecon-india-2026-recap/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ The demo illustrated how HAMi and vCluster together support practical multi-tena

Throughout the Project Pavilion, visitors experienced two hands-on demonstrations highlighting real-world AI inference on Kubernetes.

For readers who want to reproduce parts of the vLLM workflow, see the [HAMi vLLM lab](https://project-hami.io/tutorials/labs/hami-vllm).
For readers who want to reproduce parts of the vLLM workflow, see the [HAMi vLLM lab](/tutorials/labs/hami-vllm).

### Demo 1: Production AI Inference with vLLM and SGLang

Expand Down
8 changes: 4 additions & 4 deletions docs/installation/aws-installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ If both the **hami-device-plugin** and **hami-scheduler** pods are in the `Runni

### NVIDIA Devices

- [Use Exclusive GPU](https://project-hami.io/docs/userguide/nvidia-device/examples/use-exclusive-card)
- [Allocate Specific Device Memory to a Container](https://project-hami.io/docs/userguide/nvidia-device/examples/allocate-device-memory)
- [Allocate Device Core Resources to a Container](https://project-hami.io/docs/userguide/nvidia-device/examples/allocate-device-core)
- [Assign Tasks to MIG Instances](https://project-hami.io/docs/userguide/nvidia-device/examples/dynamic-mig-example)
- [Use Exclusive GPU](/docs/userguide/nvidia-device/examples/use-exclusive-card)
- [Allocate Specific Device Memory to a Container](/docs/userguide/nvidia-device/examples/allocate-device-memory)
- [Allocate Device Core Resources to a Container](/docs/userguide/nvidia-device/examples/allocate-device-core)
- [Assign Tasks to MIG Instances](/docs/userguide/nvidia-device/examples/dynamic-mig-example)
2 changes: 1 addition & 1 deletion docs/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ Release branches and PRs are managed as follows:
- Branches are created for each major or minor release.
- The branch name will contain the version, for example release-1.2.
- Patch releases are created from a release branch.
- For critical fixes that need to be included in a patch release, PRs should always be first merged to master and then cherry-picked to the release branch. PRs need to be guaranteed to have a release note written and these descriptions will be reflected in the next patch release. The cherry-pick process of PRs is executed through the script. See [cherry-pick usage](https://project-hami.io/docs/contributor/cherry-picks).
- For critical fixes that need to be included in a patch release, PRs should always be first merged to master and then cherry-picked to the release branch. PRs need to be guaranteed to have a release note written and these descriptions will be reflected in the next patch release. The cherry-pick process of PRs is executed through the script. See [cherry-pick usage](/docs/contributor/cherry-picks).
- For complex changes, specially critical bugfixes, separate PRs may be required for master and release branches.
- The milestone mark (for example v1.4) will be added to PRs which means changes in PRs are one of the contents of the corresponding release.
- During PR review, the Assignee selection is used to indicate the reviewer.
Expand Down
5 changes: 3 additions & 2 deletions docusaurus.config.js
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@ const { themes } = require("prism-react-renderer");
const lightTheme = themes.github;
const darkTheme = themes.dracula;
const defaultLocale = "en";
const siteUrl = (process.env.DOCUSAURUS_SITE_URL || "https://project-hami.io").replace(/\/$/, "");

async function localizedBlogPlugin(context, opts) {
const p = await require("@docusaurus/plugin-content-blog").default(context, opts);
Expand Down Expand Up @@ -32,7 +33,7 @@ localizedBlogPlugin.validateOptions = require("@docusaurus/plugin-content-blog")
module.exports = {
title: "HAMi",
tagline: "Heterogeneous AI Computing Virtualization Middleware",
url: "https://project-hami.io",
url: siteUrl,
baseUrl: "/",
onBrokenLinks: "throw",
trailingSlash: false,
Expand Down Expand Up @@ -135,7 +136,7 @@ module.exports = {
tagName: "link",
attributes: {
rel: "canonical",
href: "https://project-hami.io/",
href: `${siteUrl}/`,
},
},
{
Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
---
title: 介绍 HAMi
authors: [hami_community]
slug: introducing-hami
tags: [介绍, GPU 共享, Kubernetes]
---

## 什么是 HAMi?
Expand Down
Original file line number Diff line number Diff line change
@@ -1,8 +1,9 @@
---
layout: post
title: HAMi 项目 GPU Pod 调度流程源码走读
slug: hami-gpu-scheduling-source-code
catalog: true
tag: [Kubernetes, GPU, AI]
tags: [Kubernetes, GPU, AI, Source Code, 调度]
authors: [elrond_wang]
---

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@ KubeCon 期间的主舞台 Demo 将展示 GPU 共享与调度在 Kubernetes 中
欢迎关注:

- [HAMi GitHub 仓库](https://github.com/project-hami/hami)
- [HAMi 社区官网](https://project-hami.io)
- [HAMi 社区官网](/zh/)

如果你也会在阿姆斯特丹,欢迎来 Project Pavilion 找到我们。

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ tags: ["CNCF", "Incubating"]

HAMi 是面向 Kubernetes 的异构算力虚拟化与调度中间件,通过容器级硬隔离精细切分 GPU 显存与算力,让多个工作负载安全共享同一张加速器。项目由 [张潇](https://github.com/wawa0210)、[李孟轩](https://github.com/archlitchi) 等维护者发起,在 CNCF 治理下由全球开发者共建。

今天,HAMi 已被数百家组织采用,覆盖 NVIDIA、昇腾、寒武纪、海光、摩尔线程、燧原、昆仑芯、MetaX、AWS Neuron、Vastai 等十余种加速器(见[支持设备列表](https://project-hami.io/docs/userguide/device-supported)),并以 [CNCF 案例研究](/zh/case-studies)的形式记录了招商银行、SNOW Corp.、蔚来、贝壳、DaoCloud、顺丰科技、PREP EDU 等的落地实践,横跨金融、汽车、出行、物流、教育与云服务。HAMi-core 已与 Kubernetes 默认调度器、[Volcano](https://github.com/volcano-sh/volcano/blob/master/docs/user-guide/how_to_use_gpu_sharing.md)、[Kueue](https://github.com/kubernetes-sigs/kueue)、[Koordinator](https://koordinator.sh/docs/user-manuals/device-scheduling-gpu-share-with-hami) 以及 [KAI Scheduler](/zh/blog/hami-core-adopted-by-nvidia-kai-scheduler) 完成集成。
今天,HAMi 已被数百家组织采用,覆盖 NVIDIA、昇腾、寒武纪、海光、摩尔线程、燧原、昆仑芯、MetaX、AWS Neuron、Vastai 等十余种加速器(见[支持设备列表](/docs/userguide/device-supported)),并以 [CNCF 案例研究](/zh/case-studies)的形式记录了招商银行、SNOW Corp.、蔚来、贝壳、DaoCloud、顺丰科技、PREP EDU 等的落地实践,横跨金融、汽车、出行、物流、教育与云服务。HAMi-core 已与 Kubernetes 默认调度器、[Volcano](https://github.com/volcano-sh/volcano/blob/master/docs/user-guide/how_to_use_gpu_sharing.md)、[Kueue](https://github.com/kubernetes-sigs/kueue)、[Koordinator](https://koordinator.sh/docs/user-manuals/device-scheduling-gpu-share-with-hami) 以及 [KAI Scheduler](/zh/blog/hami-core-adopted-by-nvidia-kai-scheduler) 完成集成。

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Inspect zh blog posts for docs links that may need a /zh/ prefix.
rg -n '\]\(/docs/' i18n/zh/docusaurus-plugin-content-blog

Repository: Project-HAMi/website

Length of output: 2430


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Inspect site i18n/doc routing config and related zh docs link usage.
git ls-files docusaurus.config.* sidebars.* i18n/zh | sed -n '1,200p'
echo '--- docusaurus config outline ---'
ast-grep outline docusaurus.config.* --view expanded 2>/dev/null || true
echo '--- search for docsRouteBasePath / locale routeBasePath ---'
rg -n 'docsRouteBasePath|routeBasePath|defaultLocale|locales|i18n|/zh/docs|/docs/' docusaurus.config.* i18n/zh -g '!**/node_modules/**'

Repository: Project-HAMi/website

Length of output: 50377


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Find the exact file listing the docs navigation or localization links.
fd -t f 'docusaurus.config.*|sidebars.*|doc.*' .

Repository: Project-HAMi/website

Length of output: 1787


🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo '--- docusaurus.config.js relevant sections ---'
sed -n '60,90p;210,290p' docusaurus.config.js

echo '--- custom docs plugin outline ---'
ast-grep outline src/plugins/docs/index.js --view expanded 2>/dev/null || true

echo '--- custom docs plugin search ---'
rg -n 'routeBasePath|docsRouteBasePath|currentLocale|/zh/docs|/docs' src/plugins/docs/index.js docusaurus.config.js

Repository: Project-HAMi/website

Length of output: 4997


Use the zh docs path here

This link sends Chinese readers to the default docs locale; the matching Chinese page exists at /zh/docs/userguide/device-supported.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@i18n/zh/docusaurus-plugin-content-blog/hami-cncf-incubating/index.md` at line
19, The link in this blog content points Chinese readers to the default docs
locale instead of the Chinese docs page. Update the “支持设备列表” href in this
Markdown file to use the zh docs path, matching the existing Chinese routing
convention (for example, the device-supported page under /zh/docs).


这一里程碑离不开全球贡献者与社区的共建:HAMi 至今已汇聚来自几十个国家的近 500 名贡献者。[密瓜智能(Dynamia)](https://www.dynamia.ai)、[DaoCloud](https://www.daocloud.io)、[第四范式](https://www.4paradigm.com)、[NVIDIA](https://www.nvidia.com)、[华为云](https://www.huawei.com),以及众多个人开发者、用户企业与生态伙伴,都作出了不可替代的贡献。

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ HAMi 是 CNCF 沙箱项目,专注于异构 AI 算力虚拟化中间件。其
- **KAI Scheduler** = 决定「谁在什么时候用什么 GPU」(调度层)
- **HAMi** = 确保「用了就只有这么多,不能多占」(隔离层)

两者结合,才能实现真正意义上的生产级 GPU 共享。HAMi 支持 NVIDIA GPU、华为昇腾 NPU、寒武纪 MLU、海光 DCU、昆仑芯 XPU 等多种异构加速卡,是云原生 GPU 虚拟化领域覆盖最广的开源方案。详细的异构加速卡支持信息请参考 [HAMi 官方文档](https://project-hami.io/zh/docs/userguide/device-supported)。
两者结合,才能实现真正意义上的生产级 GPU 共享。HAMi 支持 NVIDIA GPU、华为昇腾 NPU、寒武纪 MLU、海光 DCU、昆仑芯 XPU 等多种异构加速卡,是云原生 GPU 虚拟化领域覆盖最广的开源方案。详细的异构加速卡支持信息请参考 [HAMi 官方文档](/zh/docs/userguide/device-supported)。

## 集成架构:HAMi + KAI Scheduler 如何协作

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ date: "2025-12-27"
description: "12 月 27 日,HAMi Meetup 北京站近百位技术伙伴齐聚,分享异构算力虚拟化、调度策略与生产实践。"
authors: [hami_community]
tags: ["HAMi", "Meetup", "异构算力", "GPU 虚拟化", "云原生"]
image: "hami-meetup-beijing-banner.webp"
image: "./hami-meetup-beijing-banner.webp"
---

![HAMi Meetup 北京站](hami-meetup-beijing-banner.webp)
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -206,7 +206,7 @@ helm repo update
helm upgrade hami hami-charts/hami -n hami-system
```

完整安装文档请参考:[https://project-hami.io/zh/docs/installation/online-installation](https://project-hami.io/zh/docs/installation/online-installation)
完整安装文档请参考:[https://project-hami.io/zh/docs/installation/online-installation](/zh/docs/installation/online-installation)

:::warning[升级注意事项]

Expand Down Expand Up @@ -239,7 +239,7 @@ v2.8.0 发布以来,HAMi 官网与文档经历了有史以来最大规模的

感谢 [@mesutoezdil](https://github.com/mesutoezdil) 对 HAMi 官方文档优化做出的贡献。

官网地址:[https://project-hami.io](https://project-hami.io)
官网地址:[https://project-hami.io/zh/](/zh/)

Website 仓库:[https://github.com/Project-HAMi/website](https://github.com/Project-HAMi/website)

Expand All @@ -266,6 +266,6 @@ HAMi v2.9.0 是一次面向异构设备虚拟化深度、Kubernetes 原生标准
- GitHub Release:[https://github.com/Project-HAMi/HAMi/releases/tag/v2.9.0](https://github.com/Project-HAMi/HAMi/releases/tag/v2.9.0)
- HAMi-DRA:[https://github.com/Project-HAMi/HAMi-DRA](https://github.com/Project-HAMi/HAMi-DRA)
- Volcano vGPU Device Plugin:[https://github.com/Project-HAMi/volcano-vgpu-device-plugin](https://github.com/Project-HAMi/volcano-vgpu-device-plugin)
- 项目文档:[https://project-hami.io](https://project-hami.io)
- 项目文档:[https://project-hami.io/zh/docs/](/zh/docs/)
- 社区 Discord(推荐):[https://discord.gg/Amhy7XmbNq](https://discord.gg/Amhy7XmbNq)
- 社区 CNCF Slack:[https://cloud-native.slack.com/archives/C07T10BU4R2](https://cloud-native.slack.com/archives/C07T10BU4R2)
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ HAMi 在 KubeCon India 的亮相正是对这一趋势的直接回应:通过现

在 Project Pavilion,参观者体验了两场动手演示,展示 Kubernetes 上真实的 AI 推理场景。

如果你希望复现其中一部分 vLLM 工作流,可以参考 [HAMi vLLM 实验](https://project-hami.io/tutorials/labs/hami-vllm)
如果你希望复现其中一部分 vLLM 工作流,可以参考 [HAMi vLLM 实验](/tutorials/labs/hami-vllm)

### Demo 1:基于 vLLM 与 SGLang 的生产级 AI 推理

Expand Down
Loading