Epic Goal

Default Kubernetes scheduler is stable and enterprise grade software that does the scheduling job pretty well .Default kubernetes schedule a job or many jobs in a sequence which is good for most of the use cases like web server but not for HPC workload . 

Now let's talk about HPC workload, a scientific workload like genome sequencing or calculating the number of stars in the universe. The data for this type of workload is so big that it requires big powerful machines to do computations and it takes time. Now with containers we can break down that big workload into small jobs that can fit in a container but all these jobs are interlinked and need to start and finish at the same time to give accurate data but kubernetes scheduler can only schedule jobs in sequence . To solve the scheduling problem of HPC workload where it requires jobs to start, execute and finish all at the same time , kubernetes requires a new scheduler, a HPC-native scheduler . 

• Make kubeflux part of k8 scheduler plugin https://github.com/kubernetes-sigs/scheduler-plugins
• HPC scheduler 

Why is this important?

• …

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>