« lib/IO/K8s/Api/Resource/V1beta2/ResourcePool.pm
↑ Summary
lib/IO/K8s/Api/Resource/V1beta2/ResourceSliceSpec.pm »
| 1 | package IO::K8s::Api::Resource::V1beta2::ResourceSlice; | ||
| 2 | # ABSTRACT: ResourceSlice represents one or more resources in a pool of similar resources, managed by a common driver. A pool may span more than one ResourceSlice, and exactly how many ResourceSlices comprise a pool is determined by the driver. At the moment, the only supported resources are devices with attributes and capacities. Each device in a given pool, regardless of how many ResourceSlices, must have a unique name. The ResourceSlice in which a device gets published may change over time. The unique identifier for a device is the tuple <driver name>, <pool name>, <device name>. Whenever a driver needs to update a pool, it increments the pool.Spec.Pool.Generation number and updates all ResourceSlices with that new number and new resource definitions. A consumer must only use ResourceSlices with the highest generation number and ignore all others. When allocating all resources in a pool matching certain criteria or when looking for the best solution among several different alternatives, a consumer should check the number of ResourceSlices in a pool (included in each ResourceSlice) to determine whether its view of a pool is complete and if not, should wait until the driver has completed updating the pool. For resources that are not local to a node, the node name is not set. Instead, the driver may use a node selector to specify where the devices are available. This is an alpha type and requires enabling the DynamicResourceAllocation feature gate. | ||
| 3 | 5 | our $VERSION = '1.112'; | |
| 4 | 5 | ▶ | use IO::K8s::APIObject; |
|
Subroutine
BEGIN: called CC=1 SCAR=0.0
| |||
| 5 | |||
| 6 | |||
| 7 | 5 | k8s spec => 'Resource::V1beta2::ResourceSliceSpec', 'required'; | |
| 8 | |||
| 9 | |||
| 10 | 5 | 1; | |
| 11 | |||
| 12 | __END__ | ||