diff options
| author | James E. Blair <jim@acmegating.com> | 2021-09-03 13:23:44 -0700 |
|---|---|---|
| committer | James E. Blair <jim@acmegating.com> | 2021-09-10 10:54:59 -0700 |
| commit | aee6ef6f7f93c3c1dccd0576165d71ac1eecd13e (patch) | |
| tree | f0a8684b7dee96117fd939ce73da0540c9991024 /releasenotes | |
| parent | b41f467340f875101ecb366232e5ddda6714e993 (diff) | |
| download | zuul-aee6ef6f7f93c3c1dccd0576165d71ac1eecd13e.tar.gz | |
Report nodepool resource stats gauges in scheduler
We currently report nodepool resource usage whenever we use or return
nodes. This now happens on the executors, and they don't have a
global view of all nodes used. The schedulers do, and they already
have a periodic stats reporting method.
Shift the reporting of node resource gauges to the scheduler. To make
this efficient, use a tree cache for nodes. Because node records
alone don't have enough information to tie them back to a tenant or
project, use the new user_data field on the Node object to store that
info when we mark a node in use. Also, store the zuul system id on
the node, so that we can ensure we're only reporting nodes that belong
to us.
Update the node list in the REST API to use the cache as well, and
also filter its results by zuul system id and tenant.
Depends-On: https://review.opendev.org/807362
Change-Id: I9d0987b250b8fb54b3b937c86db327d255e54abd
Diffstat (limited to 'releasenotes')
| -rw-r--r-- | releasenotes/notes/nodepool-4.3.0-6969ad89ea27a75e.yaml | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/releasenotes/notes/nodepool-4.3.0-6969ad89ea27a75e.yaml b/releasenotes/notes/nodepool-4.3.0-6969ad89ea27a75e.yaml new file mode 100644 index 000000000..dd2203def --- /dev/null +++ b/releasenotes/notes/nodepool-4.3.0-6969ad89ea27a75e.yaml @@ -0,0 +1,6 @@ +--- +upgrade: + - | + Nodepool 4.3.0 is now required. Zuul stores additional + information in node records in preparation for supporting multiple + schedulers. |