58bad8e6b1
Being able to set cpu_mode to "custom" is nice but doesn't do us much good if users then have to resort to nova_nova_conf_overrides to set cpu_model and/or cpu_model_extra_flags. Instead, honor nova_cpu_model and nova_cpu_model_extra_flags variable. Also add a release note saying that for those users who did previously set these flags via nova_nova_conf_overrides, they should move those bits to the newly understood variables. Change-Id: I889e70826c5c631b86305b512b86fba2b89521b4
19 lines
894 B
YAML
19 lines
894 B
YAML
---
|
|
features:
|
|
- You can now set the Libvirt CPU model and feature flags from the
|
|
appropriate entry under the ``nova_virt_types`` dictionary variable
|
|
(normally ``kvm``).
|
|
``nova_cpu_model`` is a string value that sets the CPU model; this
|
|
value is ignored if you set any ``nova_cpu_mode`` other than
|
|
``custom``.
|
|
``nova_cpu_model_extra_flags`` is a list that allows you to specify
|
|
extra CPU feature flags not normally passed through with
|
|
``host-model``, or the ``custom`` CPU model of your choice.
|
|
upgrade:
|
|
- If your configuration previously set the ``libvirt/cpu_model``
|
|
and/or ``libvirt/cpu_model_extra_flags`` variables in a
|
|
``nova_nova_conf_overrides`` dictionary, you should consider
|
|
moving those to ``nova_cpu_model`` and
|
|
``nova_cpu_model_extra_flags`` in the appropriate entry (normally
|
|
``kvm``) in the ``nova_virt_types`` dictionary.
|