Hi Wilfred Thanks for putting things together, this looks really good. I really like the concepts introduced in the proposal, such as priority fencing and offset brilliant ideas! I have one major doubt here, which is more related to how users can consume this feature. I have added some comments in the doc, pls check. The key idea is I want to make sure this is something users can easily understand and use these concepts to achieve what they cannot do in the past. And at the same time, they won't get confused by lots of implications.
Thanks Weiwei On Thu, Dec 1, 2022 at 5:42 PM Wilfred Spiegelenburg <[email protected]> wrote: > Hi, > > Priorities are a standard feature in K8s. YuniKorn has only had a very > limited use of priorities in Daemon Set preemption and request sorting. > Extending this into the rest of the scheduling cycle has been on the cards > for a long time. > > This design does not change the sorting of requests, i.e. AllocationAsk, > within an application. Priority based sorting has been used since our > earliest releases. Adding a different sorting for requests falls outside of > the design. > > Implementation will be tracked under YUNIKORN-1 > > Please provide feedback on the design > > Wilfred > > [1] > > https://docs.google.com/document/d/1P_xlWSj65BiwAglvDvFyrnh8wZ7M72FRtIg199fyHNo/edit?usp=sharing >
