6b494dc99d
The code in commit 7be531fe9462f2b07d4a1abf6687f649d1dfbb89 Author: Daniel P. Berrange <berrange@redhat.com> Date: Tue Jan 15 20:43:48 2013 +0000 Refactor code for setting up libvirt disk mappings accidentally broken launching of instances where the flavor had non-zero swap specified. This was not caught due to complete lack of test coverage for the '_create_image' method. This adds two test cases for that method, exercising this bug. It also fixes a bug in netutils which was not handling a NULL network mapping, which is a valid scenario for several callers. Fixes bug #1131306 Change-Id: I214561ba3ec6440d11a5afb0665e6b6f990bd148 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 discussion 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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast