zuul/zuul
Code Issues Proposed changes

Add scheduler config options for hold expiration

Browse Source 
This adds max_hold_expiration and default_hold_expiration as
scheduler options.

max_hold_expiration sets the absolute maximum age, in seconds,
a node placed in the hold state will remain available. This
defaults to 0, which means there is no maximum.

default_hold_expiration sets the default value used if no value
is supplied. This defaults to max_hold_expiration.

Change-Id: Ia483ac664e0a2adcec9efb29d3d701f6d315ef3b
This commit is contained in:
David Shrewsbury
2019-09-17 11:14:26 -04:00
parent 2c1c9ae662
commit e8a0d799a6
6 changed files with 188 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
releasenotes/notes/max_hold_age-1c6cef0bce537bce.yaml Normal file
View File

@@ -0,0 +1,8 @@
---
features:
- |
New scheduler options, max_hold_expiration and default_hold_expiration, are
added to control how long nodes held for an autohold request remain
available. The max_hold_expiration option defaults to 0, which means the
held nodes will not automatically expire, and default_hold_expiration
defaults to the value of max_hold_expiration.