dd3f899fbe
Historically Nova has not set any CPU model for guests started with the libvirt driver. This means they are all using the per-hyervisor default settings for CPU model. With KVM/QEMU guests the model was traditionally a very conserative choice which exposed minimal features. This is significantly limits the performance of applications. Further the model has changed over time, so the exact default model is unpredictable. Switching Nova to use the host CPU model by default should improve the out of the box performance & give a known setup. This does not impact migration compatibility, since the migration code is already doing comparison checks against the source and destination host CPU model, regardless of the actual model used in the guest. In the future the migration code should be tweaked so that it actually compares the current guest CPU model, against the target host CPU model, which would potentially broaden the migration compatibility pool. With this patch there is a new libvirt_cpu_mode="none" which can be used to explicitly prevent any CPU model setting in the instance XML. The default value None, will now default to "none" for LXC/UML/etc, and "host-model" for QEMU/KVM Fixes: bug #1003373 Implements: blueprint libvirt-xml-cpu-model Change-Id: I5b96e4532b6a960e1608dd6e19ae9d194379fb6a Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMWare, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the dicussion on the mailing list, at:
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests. Further developer focused documentation is available at:
Changes to OpenStack Nova should be submitted for review via the Gerrit tool, following the workflow documented at:
-- End of broadcast