Skip to content

Commit

Permalink
[YUNIKORN-2276] fix hyperlinks of "Resource Quota Management" page (a…
Browse files Browse the repository at this point in the history
…pache#385)

Reviewers: Chia-Ping Tsai <[email protected]>
  • Loading branch information
chenyulin0719 authored Dec 19, 2023
1 parent 9e5f79c commit 775d999
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
8 changes: 4 additions & 4 deletions docs/user_guide/resource_quota_mgmt.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ Multiple container specifications will be aggregated into one total pod resource
In the case that static queue definitions are used for a queue there is no limit on the type of resource that can be specified in a quota.
Quota annotations on namespaces, used as part of the automatic queue creation, are limited to the equivalent _cpu_ and _memory_ resources.
See the [setup](#Namespace-quota) below for the annotations on the namespace for quotas.
See the [setup](#namespace-quota) below for the annotations on the namespace for quotas.
## Kubernetes and YuniKorn quota interaction
The recommendation is to turn off, not configure, the Kubernetes Namespace quotas.
Expand Down Expand Up @@ -191,7 +191,7 @@ Automatically map a Kubernetes `namespace` to a queue in YuniKorn.
The user creates the required namespaces in Kubernetes.
The YuniKorn k8s shim and core scheduler automatically pass the required information and map the namespace to a queue, creating the queue if it does not exist.
The resource quota will be managed by YuniKorn instead of using the Kubernetes namespace quota.
This does require the namespaces to be setup without Kubernetes quota enforcement and tags as per the [setup](#Namespace-quota) below.
This does require the namespaces to be setup without Kubernetes quota enforcement and tags as per the [setup](#namespace-quota) below.

### Configuration
Apply the following configuration to YuniKorn's configmap:
Expand All @@ -216,7 +216,7 @@ The `create` flag is set to true which will trigger the creation of the queue wi

Applications within the automatically created child queues will be sorted based sorting policy set on the parent queue.
In this case the property `application.sort.policy` is in this configuration set to `stateaware`.
This is a simple app sorting policy applicable for batch jobs, you can find more document [here](sorting_policies.md#StateAwarePolicy).
This is a simple app sorting policy applicable for batch jobs, you can find more document [here](sorting_policies.md#stateawarepolicy).

You can change the configuration using the helm charts during the installation by overwriting the configuration in the
[helm chart template](https://github.com/apache/yunikorn-release/blob/master/helm-charts/yunikorn/values.yaml#L71-L81).
Expand Down Expand Up @@ -290,7 +290,7 @@ partitions:
parent: true
```

The configuration used for the namespace to queue mapping is the same as [above](#Namespace-to-queue-mapping).
The configuration used for the namespace to queue mapping is the same as [above](#namespace-to-queue-mapping).
As an extension to the placement rule a `parent` rule is added to support the grouping.
The parent rule is used to generate the parent, or the queue above, in the hierarchy.
The rule uses the tag `namespace.parentqueue` from the application to generate the parent queue name.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ spec:
在为队列使用静态队列定义的情况下,对配额中可指定的资源类型没有限制。
作为自动队列创建的一部分,命名空间上的配额注释被限制在相当于 _cpu_ 和 _memory_ 的资源。
参见下面的 [设置](#Namespace-quota),了解命名空间上的配额注释。
参见下面的 [设置](#命名空间配额),了解命名空间上的配额注释。
## Kubernetes 和 YuniKorn 配额互动
建议关闭而不是配置 Kubernetes 命名空间配额。
Expand Down Expand Up @@ -193,7 +193,7 @@ labels:
用户在 Kubernetes 中创建所需的命名空间。
YuniKorn k8s shim 和核心调度器会自动传递所需信息,并将命名空间映射到队列中,如果队列不存在,则创建队列。
资源配额将由 YuniKorn 管理,而不是使用 Kubernetes 命名空间配额。
这确实需要按照下面的 [设置](#Namespace-quota) 设置命名空间,不需要 Kubernetes 配额的执行和标签。
这确实需要按照下面的 [设置](#命名空间配额) 设置命名空间,不需要 Kubernetes 配额的执行和标签。

### 配置
将以下配置应用于 YuniKorn 的配置图:
Expand All @@ -218,7 +218,7 @@ partitions:

自动创建的子队列中的应用程序将根据父队列上设置的排序策略进行排序。
在这种情况下,属性 `application.sort.policy` 在此配置中被设置为 `stateaware` 。
这是一个适用于批处理作业的简单应用排序策略,你可以找到更多的文件 [这里](sorting_policies.md#StateAwarePolicy)。
这是一个适用于批处理作业的简单应用排序策略,你可以找到更多的文件 [这里](sorting_policies.md#stateawarepolicy)。

你可以在安装过程中使用 helm charts 来改变配置,通过覆盖在
[helm chart template](https://github.com/apache/yunikorn-release/blob/master/helm-charts/yunikorn/values.yaml#L71-L81)。
Expand Down

0 comments on commit 775d999

Please sign in to comment.