f029784eaf
This makes us pass an upper limit to placement when doing scheduling activities. Without this, we'll always receive every host in the deployment (that has space for the request), which may be very large. Closes-Bug: #1746294 Change-Id: I1c34964a74123b3d94ccae89d7cac0426b57b9b6
8 lines
369 B
YAML
8 lines
369 B
YAML
---
|
|
fixes:
|
|
- |
|
|
The FilterScheduler now limits the number of results in the query it makes
|
|
to placement to avoid situations where every compute node in a large
|
|
deployment is returned. This is configurable with the new
|
|
``[scheduler]/max_placement_results`` configuration option, which defaults
|
|
to 1000, a sane starting value for any size deployment. |