-
Feature
-
Resolution: Done
-
Normal
-
None
Feature Overview (aka. Goal Summary)
- Feature Parity for Kubernetes SIG/RH Packaged - Scheduler Plugins
- Enable Power and s390x builds for Scheduler Plugins
Why is this important?
- Scheduling is a key component of workload management. Plugins enable customer specific/use case specific decisions to be made when scheduling the workload. e.g., to the closest NUMA node, the proper architecture, and many other decisions
Goals (aka. expected user outcomes)
For IBM Power and IBM Z, as an OpenShift user, I want to schedule work based on plugins, and know it works on Power. https://github.com/kubernetes-sigs/scheduler-plugins#plugins
Requirements (aka. Acceptance Criteria):
- There is an SIG container build that runs in MU supported architectures on OpenShift.
- The plugins load into the OpenShift Container Platform and can be used for decision making when scheduling workloads.
Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed. Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.
Deployment considerations | List applicable specific needs (N/A = not applicable) |
Self-managed, managed, or both | Yes |
Classic (standalone cluster) | Yes |
Hosted control planes | Yes |
Multi node, Compact (three node), or Single node (SNO), or all | Yes |
Connected / Restricted Network | Yes |
Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | IBM Power, IBM Z |
Operator compatibility | n/a |
Backport needed (list applicable versions) | n/a |
UI need (e.g. OpenShift Console, dynamic plugin, OCM) | n/a |
Other (please specify) |
Use Cases (Optional):
Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.
<your text here>
Questions to Answer (Optional):
Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.
<your text here>
Out of Scope
High-level list of items that are out of scope. Initial completion during Refinement status.
<your text here>
Background
Provide any additional context is needed to frame the feature. Initial completion during Refinement status.
<your text here>
Customer Considerations
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. Initial completion during Refinement status.
<your text here>
Documentation Considerations
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.
<your text here>
Interoperability Considerations
Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? Initial completion during Refinement status.
<your text here>