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: keps/sig-scheduling/5007-device-attach-before-pod-scheduled/README.md
+3-27Lines changed: 3 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -330,43 +330,19 @@ This issue needs to be resolved before the beta is released.
330
330
### DRA Scheduler Plugin Design Overview
331
331
332
332
This document outlines the design of the DRA Scheduler Plugin, focusing on the handling of fabric devices.
333
-
Key additions include new attributes for device identification, enhancements to `AllocatedDeviceStatus`, and the process for handling `ResourceSlices` upon attachment failure.
333
+
Key additions include `BindingConditions` and `BindingFailureConditions for device identification and preparetion, enhancements to `AllocatedDeviceStatus.Conditions`, and the process for handling `ResourceSlices` upon attachment failure.
334
334
The composable controller design is also discussed, emphasizing efficient utilization of fabric devices.
335
335
336
336

337
337
338
338
#### BasicDevice Enhancements
339
339
340
-
To indicate whether a device is a fabric device, fields are added to the `Basic` within `Device`.
340
+
To indicate that the device is a Fabric device or other device that requires some preparation (e.g. attachment), some fields are added to the `Basic` within `Device`.
341
341
These fields will be used by the controller that exposes the `ResourceSlice` to notify whether the device is a fabric device.
342
342
343
343
```go
344
-
// Device represents one individual hardware instance that can be selected based
345
-
// on its attributes. Besides the name, exactly one field must be set.
346
-
typeDevicestruct {
347
-
// Name is unique identifier among all devices managed by
348
-
// the driver in the pool. It must be a DNS label.
349
-
//
350
-
// +required
351
-
Namestring
352
-
353
-
// Basic defines one device instance.
354
-
//
355
-
// +optional
356
-
// +oneOf=deviceType
357
-
Basic *BasicDevice
358
-
}
359
-
360
344
// BasicDevice represents a basic device instance.
361
345
typeBasicDevicestruct {
362
-
// Attributes defines the set of attributes for this device.
363
-
// The name of each attribute must be unique in that set.
364
-
//
365
-
// The maximum number of attributes and capacities combined is 32.
366
-
//
367
-
// +optional
368
-
Attributesmap[QualifiedName]DeviceAttribute
369
-
370
346
// BindingConditions defines the conditions for binding.
371
347
//
372
348
// +optional
@@ -562,7 +538,7 @@ And until the device is actually attached to the node, the user does not know wh
562
538
563
539
Because of this concept, the Pool and ResourceSlice exposed by Composable DRA controller are separate for each model.
564
540
The devices in the Pool for each model have unique device names, but are essentially information about how many devices of this model are in the ResourceSlice.
565
-
Composable DRA controoler also add a model name and so on into the attributes of each device.
541
+
Composable DRA controller also add a model name and so on into the attributes of each device.
0 commit comments