[YUNIKORN-2457] [UMBRELLA] Unify ask and allocation

• Type: Improvement
• Status: In Progress
• Priority: Major
• Resolution: Unresolved
• Component/s: core - scheduler, scheduler-interface, shim - kubernetes
• Target Version: 1.6.0
• Assignee: Craig Condit
• Reporter: Craig Condit
• Created: 27/Feb/24 16:18
• Updated: 25/Apr/24 18:54

Description

The core scheduler currently tracks asks and allocations separately. Historically, this was to allow a one-to-many relationship between asks and allocations via the maxAllocations field. However, this logic has never been utilized and causes a lot of special-casing and friction. If we remove maxAllocations, we can unify the ask and allocation objects and simplify the scheduler-interface and tracking facilities.

Sub-Tasks

• SI: Unify ask and allocation APIs: Open
• Core: Merge ask and allocation objects: Open