OpenStack Compute (Nova)
Go to file
Matt Riedemann e4e1c6a2f0 libvirt: add comment for vifs_already_plugged=True in finish_migration
Given we unplug VIFs in _cleanup_resize if the host has changed, it's
confusing to pass vifs_already_plugged=True in finish_migration without
some explanation of why we don't check to see if the host has changed
before deciding what the value of vifs_already_plugged should be when
creating the new domain and plugging VIFs again.

After some discussion with Neutron cores, this is the explanation I've
come up with, albeit not a great one, and indicates a gap in some of the
nova/neutron integration story.

Related-Bug: #1323658

Change-Id: I982b6bd0650f29f34c213b6eebbe066f7bd65815
2015-03-06 07:34:08 -08:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
doc Merge "Adds keypair type in nova-api" 2015-03-05 14:41:07 +00:00
etc/nova Merge "Adds xend to rootwrap.d/compute.filters." 2015-02-26 07:03:59 +00:00
nova libvirt: add comment for vifs_already_plugged=True in finish_migration 2015-03-06 07:34:08 -08:00
plugins/xenserver xenapi: don't send terminating chunk on errors 2015-01-14 13:58:18 +00:00
tools Switch to uuidutils from oslo_utils library 2015-02-25 20:05:49 -05: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 Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04: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
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
README.rst Update links in README 2014-05-07 16:06:24 -07:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
openstack-common.conf Switch to uuidutils from oslo_utils library 2015-02-25 20:05:49 -05:00
requirements.txt Updated from global requirements 2015-03-03 17:45:03 +00:00
run_tests.sh Fix likely undesired use of redirection 2015-02-02 16:26:31 +01:00
setup.cfg Disables pci plugin for v2.1 & microversions 2015-03-03 14:20:42 +10:30
setup.py Updated from global requirements 2014-04-30 02:43:45 +00:00
test-requirements.txt Updated from global requirements 2015-02-09 22:44:39 +00:00
tox.ini Force LANGUAGE=en_US in test runs 2015-03-03 09:00:05 -08:00

README.rst

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