> 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-1-jia-gou-ji-chu/01-architecture.md).

# 概述

## 学习目标

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

* **描述 VergeOS 是什么** 以及其统一操作系统方法如何不同于传统三层基础架构和其他 HCI 平台
* **比较 HCI 和 UCI 部署模型** 并针对给定用例推荐合适的拓扑
* **解释 VergeFS（vSAN）存储** 包括层级架构、数据分布和冗余机制
* **描述核心 Fabric 网络** 以及节点间通信、vSAN 复制和 VM 热迁移流量如何流动
* **识别 VergeOS 节点类型和集群概念** 包括控制器节点、横向扩展节点、仅计算和仅存储角色

## 前置条件

无——这是培训计划的第一模块。无需任何 VergeOS 经验。

## 预计时间

**2 小时** (1.5 小时阅读 + 0.5 小时实验)

## 主题

* [**什么是 VergeOS？**](/learn-the-platform/zh/mo-kuai-1-jia-gou-ji-chu/01-vergeos-overview.md) — 统一的超融合操作系统：在单一平台中整合 VergeHV（计算）、VergeFS（存储）和 VergeFabric（网络）。它如何与 VMware、Nutanix 和传统基础架构比较。
* [**HCI 与 UCI**](/learn-the-platform/zh/mo-kuai-1-jia-gou-ji-chu/02-hci-vs-uci.md) — 面向不同扩展需求的两种部署模型。超融合（HCI）将计算和存储一起扩展；超统一融合（UCI）则通过专用节点类型独立扩展它们。
* [**vSAN 与 VergeFS 存储**](/learn-the-platform/zh/mo-kuai-1-jia-gou-ji-chu/03-vsan-vergefs.md) — 软件定义的分布式存储，采用分层驱动器（Tier 0 用于元数据，Tier 1–5 用于工作负载数据）、全局重复数据删除和自愈冗余。
* [**核心 Fabric 与网络**](/learn-the-platform/zh/mo-kuai-1-jia-gou-ji-chu/04-core-fabric.md) — 承载 vSAN 复制、集群协调和热迁移流量的节点间私有网状网络。双交换机冗余和巨型帧要求。
* [**集群与节点类型**](/learn-the-platform/zh/mo-kuai-1-jia-gou-ji-chu/05-clusters-nodes.md) — VergeOS 如何将节点组织成具有不同角色的集群：控制器、横向扩展、仅计算和仅存储。
* [**实验：探索架构**](/learn-the-platform/zh/mo-kuai-1-jia-gou-ji-chu/lab.md) — 通过动手探索 VergeOS Terraform 试验环境，追踪部署拓扑、检查基础设施即代码模式，并为客户场景设计部署方案。


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verge.io/learn-the-platform/zh/mo-kuai-1-jia-gou-ji-chu/01-architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.