> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/learn-the-platform/zh/mo-kuai-7-duo-zu-hu/07-multi-tenancy.md).

# 概述

通过适当的隔离设计多租户环境，创建租户，分配资源，并配置租户配方以实现标准化交付。

## 学习目标

在本模块结束时，你将能够：

* **设计多租户环境** 具有适当的隔离和资源边界
* **创建租户并分配资源** 使用 VergeOS 租户管理系统
* **配置租户配方** 用于标准化、可重复的租户部署

## 前置条件

* 完成 [模块 1：架构基础](/learn-the-platform/zh/mo-kuai-1-jia-gou-ji-chu/01-architecture.md) -- 理解 VergeOS 平台架构
* 完成 [模块 4：网络](/learn-the-platform/zh/mo-kuai-4-wang-luo/04-networking.md) -- 理解虚拟网络和租户网络隔离
* 完成 [模块 5：存储](/learn-the-platform/zh/mo-kuai-5-cun-chu/05-storage.md) -- 理解 vSAN 分层和存储分配
* 完成 [模块 6：虚拟机](/learn-the-platform/zh/mo-kuai-6-xu-ni-ji/06-virtual-machines.md) -- 理解虚拟机部署和配方

## 预计时间

**3 小时** （1.5 小时阅读 + 1.5 小时实验）

## 主题

* [**虚拟数据中心概念**](/learn-the-platform/zh/mo-kuai-7-duo-zu-hu/01-vdc-concepts.md) — 理解 VergeOS 租户作为隔离的虚拟数据中心、资源分配模型和租户层级结构。
* [**创建和配置租户**](/learn-the-platform/zh/mo-kuai-7-duo-zu-hu/02-creating-tenants.md) — 创建租户、分配计算、内存和存储配额，以及配置租户级网络。
* [**租户模板**](/learn-the-platform/zh/mo-kuai-7-duo-zu-hu/03-tenant-recipes.md) — 构建可复用的租户配方，用于标准化部署，包括预配置网络、虚拟机和设置。
* [**资源分配与扩展**](/learn-the-platform/zh/mo-kuai-7-duo-zu-hu/04-resource-allocation.md) — 租户节点规划、合理规模调整策略，以及单节点和多节点租户部署的扩展路径。
* [**租户隔离与安全**](/learn-the-platform/zh/mo-kuai-7-duo-zu-hu/05-isolation-security.md) — 多租户部署中的租户间网络隔离、资源保障和安全边界。
* [**实验：多租户环境**](/learn-the-platform/zh/mo-kuai-7-duo-zu-hu/lab.md) — 创建租户、分配资源、从租户配方部署，并验证租户隔离。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verge.io/learn-the-platform/zh/mo-kuai-7-duo-zu-hu/07-multi-tenancy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.