Epic Goal

• Enable the Secondary Scheduler Operator on ppc64le and s390x

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.
• The operator makes it easier to work with Scheduler Plugins and formalizes the support for scheduling changes.

Scenarios
1. As an OpenShift user, I want to schedule work based on plugins, and use the scheduler-plugins via the Secondary Scheduler Operator.

Acceptance Criteria

• The Operator installs via the Operator Hub.
• The Operator is configurable and changes workload scheduling.
• The plugins load into the OpenShift Container Platform and can be used for decision making when scheduling workloads.

Dependencies (internal and external)
1. This work should be done in parallel with scheduler plugins

Previous Work (Optional):

1. Identified the work needed

•    SME Review and Discussion with Red Hat’s multiarch to provide details of investigation
•    Enable multiarch image in midstream distgit
•    Enable multiarch image in scheduler-plugins (upstream/openshift)

2. Google Drive is updated https://docs.google.com/document/d/1rLzRLhPu7p21o8e7rNVgnaEGH3TaaMl3/edit?usp=share_link&ouid=115017881165553944060&rtpof=true&sd=true

Open questions::
1. Should we verify each architecture for each plugin using the Operator.

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.