Open
Description
What would you like to be added?
From @johnbelamaric #130764
For 1.34+: Theoretically, ResourceSlices are just, well, slices of a larger resource pool. Thus, the CapacityPools (and later the Mixins), could be considered unique across the resource pool rather than within the resource slice. If that's true, we could move to a place where we define capacitypools and mixins in one slice, and the devices in different slices. This would allow very large devices partitionable devices that share capacity pools and mixins (think: very large multi-host partitionable devices). Now, we don't do that today because this makes validation hard (impossible?) at admission time. But I want to at least introduce the idea that we might want to do it at some point. Likely we would need a controller to validate across slices and all slices in a pool generation would need to have something set in their status to say they are valid.
Why is this needed?
Further validate the incoming resources.
Metadata
Metadata
Assignees
Labels
Categorizes issue or PR as related to a new feature.Categorizes issue or PR as related to a new feature.Indicates an issue or PR lacks a `triage/foo` label and requires one.Indicates an issue or PR lacks a `triage/foo` label and requires one.Categorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Scheduling.Categorizes an issue or PR as relevant to SIG Scheduling.Categorizes an issue or PR as relevant to WG Device Management.Categorizes an issue or PR as relevant to WG Device Management.
Type
Projects
Status
📋 Backlog