[YUNIKORN-19] Use placement rules always

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Component/s: core - scheduler
• Assignee: Craig Condit
• Reporter: Wilfred Spiegelenburg
• Created: 04/Mar/20 11:18
• Updated: 03/Aug/23 17:23
• Resolved: 03/Aug/23 17:23

Description

Currently when we do not have a placement rule configured the old behaviour is used. the old behaviour relies on the queue in the submitted application to exist and there is no ACL enforced.
The old behaviour was maintained to not break existing examples and deployments.

The end goal is to use placement rules in all cases even if none are configured:

• replicate the placement behaviour in a default rule if none are configured
• set an open ACL on the root queue in the examples we provide

Issue Links

• is duplicated by: YUNIKORN-434 Scheduler crashes when the queueName in pod spec doesn't contain DOT
• is part of: YUNIKORN-1793 Handle placement rule and queue changes during initialisation (core)