Allowing setting use_job_duration with non-exclusive partitions. #4696
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Task: DWS - allow setting
use_job_durationwith non-exclusive partitionsApproach: putting a reservation on a provisioned node, that starts when DWS EOL is expected.
Changes:
Removed the restriction that use_job_duration can only be used in exclusive partitions from documentation and code.
Added functions to create and delete Slurm reservations when use_job_duration is enabled.
Updated the provisioning logic to automatically handle Slurm reservations at node boot and termination.
Minor doc and code cleanups related to DWS Flex options.
Expected Behavior:
nodes are provisioned with max_run_duration passed to DWS
all jobs, that have job time set to finish before DWS node expires can be scheduled on this node (provided that resources are available, if not - a new node is provisioned)
if the job specifies a job time that exceeds DWS node expiration, then new node(s) will be created for this job
when no jobs are running on nodes, SuspendTime takes effect, and deprovisions node, after defined time.