Fix tox -e docs
This was missed in I90ee8a2081c2a0465441a8d81d161f4887b4e1fb presumably because we no longer get warnings as errors, or some such wickedness. Anyway, this fixes docs build using tox. Change-Id: Ic8ec0c54a7c6502a0a4ea91d034fa9c1ae5e59d4 Closes-Bug: #1767192
This commit is contained in:
parent
ceac5d5469
commit
3c95254b1c
@ -398,12 +398,12 @@ The Filter Scheduler weighs hosts based on the config option
|
||||
|
||||
* |RAMWeigher| Compute weight based on available RAM on the compute node.
|
||||
Sort with the largest weight winning. If the multiplier,
|
||||
:oslo.config:opt:`filter_scheduler.ram_weight_multiplier`, is negative, the
|
||||
:oslo.config:option:`filter_scheduler.ram_weight_multiplier`, is negative, the
|
||||
host with least RAM available will win (useful for stacking hosts, instead
|
||||
of spreading).
|
||||
* |CPUWeigher| Compute weight based on available vCPUs on the compute node.
|
||||
Sort with the largest weight winning. If the multiplier,
|
||||
:oslo.config:opt:`filter_scheduler.cpu_weight_multiplier`, is negative, the
|
||||
:oslo.config:option:`filter_scheduler.cpu_weight_multiplier`, is negative, the
|
||||
host with least CPUs available will win (useful for stacking hosts, instead
|
||||
of spreading).
|
||||
* |DiskWeigher| Hosts are weighted and sorted by free disk space with the largest
|
||||
|
Loading…
Reference in New Issue
Block a user