b1a0aee1ab
The CPU power management feature of the libvirt driver, enabled with [libvirt]cpu_power_management, only manages dedicated CPUs and does not touch share CPUs. Today nova-compute refuses to start if configured with [libvirt]cpu_power_management=true [compute]cpu_dedicated_set=None. While this is functionally not limiting it does limit the possibility to independently enable the power management and define the cpu_dedicated_set. E.g. there might be a need to enable the former in the whole cloud in a single step, while not all nodes of the cloud will have dedicated CPUs configured. This patch removes the strict config check. The implementation already handles each PCPU individually, so if there are an empty list of PCPUs then it does nothing. Closes-Bug: #2043707 Change-Id: Ib070e1042c0526f5875e34fa4f0d569590ec2514
12 lines
491 B
YAML
12 lines
491 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Relaxed the config option checking of the cpu_power_management feature of
|
|
the libvirt driver. The nova-compute service will start with
|
|
[libvirt]cpu_power_management=True and an empty [compute]cpu_dedicated_set
|
|
configuration. The power management is still only applied to dedicated CPUs.
|
|
So the above configuration only allowed to ensure that cpu_power_management
|
|
can be enabled independently for configuring cpu_dedicated_set during
|
|
deployment.
|
|
|