zuul/nodepool
Code Issues Proposed changes

Add ability to ignore provider quota for a pool

Browse Source 
In some circumstances it is useful to tell the launcher to
ignore the provide quota and just trust the max-* settings
for that pool instead.

This particular need arises when using Rackspace public cloud
for both instances and OnMetal nodes. In this situation the
quota for instances and for OnMetal nodes is different, but
nodepool only queries the quota for instances. When trying to
build OnMetal nodes, the quota check fails - but should not.

In this circumstance, instead of making shade/nodepool
complicated by figuring out how to calculate disparate quota
types, it makes sense to rather just allow nodepool to ignore
the quota for a pool to try executing the build instead.

While this is our use-case, it may also be useful to others
for other reasons.

Change-Id: I232a1ab365795381ab180aceb48e8c87843ac713
This commit is contained in:
Jesse Pretorius
2018-07-10 12:30:44 +01:00
committed by Jesse Pretorius (odyssey4me)
parent 03b7b4baef
commit 4c8b5f4f99
7 changed files with 264 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
releasenotes/notes/ignore-provider-quota-aa19e7a7271ee106.yaml Normal file
View File

@@ -0,0 +1,8 @@
---
features:
- |
A new boolean pool variable ``ignore-provider-quota`` has been added to
allow the provider quota to be ignored for a pool. Instead, nodepool only
checks against the configured max values for the pool and the current usage
based on stored data. This may be useful in circumstances where the
provider is incorrectly calculating quota.