4c8b5f4f99
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
9 lines
373 B
YAML
9 lines
373 B
YAML
---
|
|
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.
|