2fe96819c2
Since we now use placement to verify basic CPU/RAM/disk resources, we should default to disabling the equivalent scheduler filters. Oddly enough, CoreFilter was already disabled so now also disable RamFilter and DiskFilter. Closes-Bug: #1709328 Change-Id: Ibe1cee1cb2642f61a8d6bf9c3f6bbee4f2c2f414
11 lines
512 B
YAML
11 lines
512 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
Since we now use Placement to verify basic CPU/RAM/disk resources when
|
|
using the FilterScheduler, the ``RamFilter`` and ``DiskFilter`` entries are
|
|
being removed from the default value for the ``enabled_filters`` config
|
|
option in the ``[filter_scheduler]`` group. If you are overriding this
|
|
option, you probably should remove them from your version. If you are
|
|
using CachingScheduler you may wish to enable these filters as we will
|
|
not use Placement in that case.
|