This allows for specifying granular CPU feature flags, when
specifying CPU models. It should be set only if cpu_mode
and cpu_model
conf parameter are set and cpu_mode
parameter value is set to “custom”.
The recent “Meltdown” CVE fixes have resulted in critical
performance penalty which impacts every Nova guest within
certain CPU models.
More info is available in nova release notes.
Fix live_migration_inbound_addr when used with non-default port/user/extra_params
live_migration_scheme was being used when live_migration_inbound_addr was set. This prohibits a non-default port/user/extra_params being used which is often required to fully describe the uri, particularly for the ssh transport (see https://bugs.launchpad.net/nova/+bug/1671288).
However live_migration_inbound_addr also works with live_migration_uri, so for now revert back to using live_migration_uri in all cases.
Correct permissions on the nova logfiles.
If the nova-manage
commands (such as dbsync) were initially run as
root then subsequent runs as the nova user would fail as the logfile is
owned by root (see bug 1671681).
The ownership of all nova logfiles is now checked before configuring
nova, as a similar issue could prevent a service starting, and the
nova-manage command is now run as the correct user.
Adds nova::params::nova_user and nova::params::nova_group. nova::cron::archive_deleted_rows::user now defaults to nova::params::nova_user instead of hardcoding ‘nova’
discover_hosts_in_cells_interval
option in the scheduler
manifest. Changing this option is needed for bare metal clouds starting
with the Ocata release.pci_alias
to alias
pci_passthrough_whitelist
to passthrough_whitelist
pci_alias
pci_passthrough_whitelist
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.