You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/design/capacity-dra-support.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -151,6 +151,8 @@ In practice:
151
151
152
152
These two responsibilities are complementary rather than overlapping.
153
153
154
+
For consumable capacity, Volcano accounts the logical total. A request for two devices with `8Gi` of memory each consumes `16Gi` of the queue's `memory.deviceclass/<DeviceClass>` quota. This does not solve physical fragmentation: if the cluster has two `8Gi` devices, a single Pod that needs `10Gi` on one device can still pass queue quota while failing the final DRA allocation.
155
+
154
156
## Root Queue and Total Resource View
155
157
156
158
For DRA resources, the cluster-wide total can come from actual cluster state or from an administrator’s explicit queue configuration.
Copy file name to clipboardExpand all lines: docs/user-guide/how_to_use_dra_quota.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,9 +53,14 @@ data:
53
53
- name: drf
54
54
- name: predicates
55
55
- name: capacity
56
+
arguments:
57
+
capacity.DynamicResourceAllocationEnable: true
58
+
capacity.DRAConsumableCapacityEnable: true
56
59
- name: nodeorder
57
60
```
58
61
62
+
The capacity plugin arguments are optional. When they are not set, Volcano uses the corresponding Kubernetes feature gate values as defaults.
63
+
59
64
## Queue Key Formats
60
65
61
66
Use the following keys in `spec.capability`, `spec.deserved`, and `spec.guarantee`.
@@ -67,6 +72,8 @@ Use the following keys in `spec.capability`, `spec.deserved`, and `spec.guarante
67
72
68
73
These keys can coexist with normal resources such as `cpu`, `memory`, and `nvidia.com/gpu`.
69
74
75
+
Consumable-capacity requests are counted per allocated device. For example, a ResourceClaim requesting `count: 2` and `memory: 8Gi` consumes `16Gi` of the queue key `memory.deviceclass/<DeviceClass>`.
76
+
70
77
## Queue Configuration Examples
71
78
72
79
### Whole-Card GPU Queue
@@ -303,6 +310,8 @@ The following request styles are not the main quota-accounting target:
303
310
304
311
If your environment relies heavily on those modes, evaluate behavior carefully before treating them as strict queue quota signals.
305
312
313
+
Queue quota is a logical total-resource check. It does not guarantee that the requested capacity can be placed on a specific physical device layout. For example, a queue may have `16Gi` of total GPU memory quota, while one Pod requesting `10Gi` still cannot fit onto any single `8Gi` device. Kubernetes DRA and the installed driver make the final physical allocation decision.
314
+
306
315
## Best Practices
307
316
308
317
1. Use `ResourceClaimTemplate` for per-Pod allocation lifecycle
0 commit comments