OpenStack Compute (Nova)
Go to file
Lee Yarwood f302bf04ab libvirt: Always copy or recreate disk.info during a migration
The disk.info file contains the path and format of any image, config or
ephermal disk associated with an instance. When using RAW images and migrating
an instance this file should always be copied or recreated. This avoids the Raw
imagebackend reinspecting the format of these disks when spawning the instance
on the destination host.

By not copying or recreating this disk.info file, a malicious image written to
an instance disk on the source host will cause Nova to reinspect and record a
different format for the disk on the destination. This format then being used
incorrectly when finally spawning the instance on the destination.

Conflicts:
    nova/tests/unit/virt/libvirt/test_driver.py
    nova/virt/libvirt/driver.py

SecurityImpact
Closes-bug: #1548450
Change-Id: Idfc16f54049aaeab31ac1c1d8d79a129acc9fb87
2016-03-08 15:04:29 +00:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
doc Kilo-Removing extension "OS-EXT-VIF-NET" from v2.1 ext list 2015-07-07 04:40:44 +00:00
etc/nova remove usage of policy.d which isn't cached 2015-03-31 17:48:35 -04:00
nova libvirt: Always copy or recreate disk.info during a migration 2016-03-08 15:04:29 +00:00
plugins/xenserver xenapi: don't send terminating chunk on errors 2015-01-14 13:58:18 +00:00
tools Avoid MODULEPATH environment var in config generator 2015-03-31 00:00:57 +00:00
.coveragerc Port Cheetah templates to Jinja2 2013-09-02 16:03:34 +02:00
.gitignore remove all traces of pylint testing infrastructure 2015-01-08 11:56:45 +00:00
.gitreview update .gitreview for stable/kilo 2015-04-15 19:58:17 +00:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.testr.conf Add tox -e functional 2014-11-12 15:31:06 -05:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Merge "Add note on running single tests to HACKING.rst" 2015-03-03 15:55:42 +00:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MANIFEST.in Finish AUTHORS transition. 2012-07-05 09:11:37 -05:00
openstack-common.conf Sync from oslo-incubator 2015-03-19 14:28:00 -04:00
README.rst Update links in README 2014-05-07 16:06:24 -07:00
requirements.txt Updated from global requirements 2015-09-19 00:16:56 +00:00
run_tests.sh Fix likely undesired use of redirection 2015-02-02 16:26:31 +01:00
setup.cfg Bump stable/kilo next version to 2015.1.4 2016-01-22 15:42:49 +00:00
setup.py Updated from global requirements 2015-07-13 15:01:57 +00:00
test-requirements.txt Updated from global requirements 2016-02-06 08:29:12 +00:00
tox.ini default tox cmd should also run 'functional' target 2015-03-20 11:43:59 -04:00

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:

http://docs.openstack.org

For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:

https://wiki.openstack.org/wiki/HypervisorSupportMatrix

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:

http://bugs.launchpad.net/nova

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:

https://git.openstack.org/cgit/openstack/nova

Developers should also join the discussion on the mailing list, at:

http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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:

http://docs.openstack.org/developer/nova/

For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.

-- End of broadcast