-
Notifications
You must be signed in to change notification settings - Fork 535
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
2 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,9 @@ | ||
# 7.7 资源模型及编排调度 | ||
|
||
本节所述的“资源模型”指的是狭义上的物理资源(如 CPU、内存、存储)。物理资源与 Kubernetes 的基本单元 Pod 存在直接的供需关系,并影响容器编排调度逻辑的设计。 | ||
|
||
从编排 Pod 的层面看,调度(scheduling)的职责是实现资源提供者(Node)与资源使用者(Pod)之间的最佳匹配。要达成这一目标,管理和分配集群资源时至少需要清楚以下几个问题: | ||
|
||
- 集群中有哪些种类的资源,如何表示这些资源,即资源模型该如何设计? | ||
- 如何描述容器的资源请求?如何描述一个 Node 当前的资源分配状态。例如,已分配资源和未分配资源的数量? | ||
- 如果节点资源不足,节点中的容器该如何处理? | ||
- 调度需要知道整个集群的资源状态,如何解决大规模集群的调度效率问题? | ||
|
||
接下来,笔者将围绕上述问题展开讨论 Kubernetes 资源模型、QoS(Quality of Service,服务质量)以及调度器(kube-scheduler)的设计。 | ||
接下来,笔者将围绕上述问题展开讨论 Kubernetes 资源模型、异构资源扩展以及默认调度器(kube-scheduler)的设计。 |