pub struct DeviceRequest {
pub admin_access: Option<bool>,
pub allocation_mode: Option<String>,
pub count: Option<i64>,
pub device_class_name: String,
pub name: String,
pub selectors: Option<Vec<DeviceSelector>>,
}
Expand description
DeviceRequest is a request for devices required for a claim. This is typically a request for a single resource like a device, but can also ask for several identical devices.
A DeviceClassName is currently required. Clients must check that it is indeed set. It’s absence indicates that something changed in a way that is not supported by the client yet, in which case it must refuse to handle the request.
Fields§
§admin_access: Option<bool>
AdminAccess indicates that this is a claim for administrative access to the device(s). Claims with AdminAccess are expected to be used for monitoring or other management services for a device. They ignore all ordinary claims to the device with respect to access modes and any resource allocations.
This is an alpha field and requires enabling the DRAAdminAccess feature gate. Admin access is disabled if this field is unset or set to false, otherwise it is enabled.
allocation_mode: Option<String>
AllocationMode and its related fields define how devices are allocated to satisfy this request. Supported values are:
-
ExactCount: This request is for a specific number of devices. This is the default. The exact number is provided in the count field.
-
All: This request is for all of the matching devices in a pool. Allocation will fail if some devices are already allocated, unless adminAccess is requested.
If AlloctionMode is not specified, the default mode is ExactCount. If the mode is ExactCount and count is not specified, the default count is one. Any other requests must specify this field.
More modes may get added in the future. Clients must refuse to handle requests with unknown modes.
count: Option<i64>
Count is used only when the count mode is “ExactCount”. Must be greater than zero. If AllocationMode is ExactCount and this field is not specified, the default is one.
device_class_name: String
DeviceClassName references a specific DeviceClass, which can define additional configuration and selectors to be inherited by this request.
A class is required. Which classes are available depends on the cluster.
Administrators may use this to restrict which devices may get requested by only installing classes with selectors for permitted devices. If users are free to request anything without restrictions, then administrators can create an empty DeviceClass for users to reference.
name: String
Name can be used to reference this request in a pod.spec.containers[].resources.claims entry and in a constraint of the claim.
Must be a DNS label.
selectors: Option<Vec<DeviceSelector>>
Selectors define criteria which must be satisfied by a specific device in order for that device to be considered for this request. All selectors must be satisfied for a device to be considered.
Trait Implementations§
Source§impl Clone for DeviceRequest
impl Clone for DeviceRequest
Source§fn clone(&self) -> DeviceRequest
fn clone(&self) -> DeviceRequest
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source
. Read moreSource§impl Debug for DeviceRequest
impl Debug for DeviceRequest
Source§impl DeepMerge for DeviceRequest
impl DeepMerge for DeviceRequest
Source§fn merge_from(&mut self, other: Self)
fn merge_from(&mut self, other: Self)
other
into self
.