Skip to content

Pass effective Requirements to Compute's run_job/run_jobs#4020

Open
un-def wants to merge 1 commit into
masterfrom
issue_4019_run_job_jobs_with_effective_requirements
Open

Pass effective Requirements to Compute's run_job/run_jobs#4020
un-def wants to merge 1 commit into
masterfrom
issue_4019_run_job_jobs_with_effective_requirements

Conversation

@un-def

@un-def un-def commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Most backend don't need it -- they provision machines/containers based on offers, which are already filtered against the effective Requirements, but both Slurm and Kubernetes backends completely ignore provided offers and rely on Requirements instead, which they previously took from the JobSpec, which is generated from the Run configuration only.

Fixes: #4019

Most backend don't need it -- they provision machines/containers based
on offers, which are already filtered against the effective
Requirements, but both Slurm and Kubernetes backends completely ignore
provided offers and rely on Requirements instead, which they previously
took from the JobSpec, which is generated from the Run configuration
only.

Fixes: #4019
@un-def un-def requested a review from r4victor July 9, 2026 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Kubernetes, Slurm: effective resource requirements are not used

1 participant