openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
47,917 Commits 10 Branches 95 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
02a82c41f9
Go to file
Matt Riedemann 02a82c41f9 Add release note for force live migration allocations 
When forcing a destination host during live migration, conductor
bypasses the scheduler, performs some pre-migration checks and then
casts to the specified destination compute host directly.

With change I40b5af5e85b1266402a7e4bdeb3705e1b0bd6f3b we are still
bypassing the scheduler but conductor will attempt to allocate
resources against the specified destination host, which could fail
and result in the live migration failing even though the force flag
was specified in the API.

This change simply adds a release note for the new behavior which
was missing from the original fix.

Change-Id: I1811dfa59865c0a878522007e0070f0fde8344f0
Related-Bug: #1712008
2017-09-06 11:30:52 -04:00
api-guide/source Update doc to indicate nova-network deprecated 2017-08-31 08:08:33 +08:00
api-ref/source api-ref: add warnings about forcing the host for live migrate/evacuate 2017-08-31 16:07:22 -04:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Skip test_rebuild_server_in_error_state for cells v1 2017-08-11 12:42:29 -04:00
doc Merge "explain payload inheritance in notification devref" 2017-09-06 13:29:59 +00:00
etc/nova rootwrap.d cleanup mislabeled files 2017-08-01 16:09:18 +10:00
gate move gate hooks to gate/ 2017-01-04 11:05:16 +00:00
nova Merge "Fix ValueError if invalid max_rows passed to db purge" 2017-09-06 13:28:39 +00:00
placement-api-ref/source [placement] Add api-ref for allocation_candidates 2017-08-10 11:26:19 +00:00
plugins/xenserver XenAPI Remove useless files when use os-xenapi lib 2017-01-10 18:06:17 -08:00
releasenotes Add release note for force live migration allocations 2017-09-06 11:30:52 -04:00
tools Prevent blank line at start of migration placeholders 2017-08-25 18:43:19 +01:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Structure for simply managing placement-api-ref 2017-03-24 15:15:53 +03: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 [placement] Adjust the name of the gabbi tests 2016-09-20 19:14:44 +00:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt List system dependencies for running common tests 2016-08-24 06:49:32 +02:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Enable global hacking checks and removed local checks 2017-02-10 15:09:37 +01:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Add a maintainers file 2015-05-23 03:22:07 +10:00
README.rst doc: Rework README to reflect new doc URLs 2017-08-03 16:06:08 -04:00
requirements.txt Updated from global requirements 2017-09-05 12:19:55 +00:00
setup.cfg Using plain routes for the microversions test 2017-07-23 22:43:53 +08:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Updated from global requirements 2017-08-30 23:26:21 +00:00
tests-functional-py3.txt Remove invalid URL in gabbi tests 2017-01-17 21:10:45 +00:00
tests-py3.txt Skip unit tests for SSL + py3 2017-03-02 14:30:16 +08:00
tox.ini [placement] Make placement_api_docs.py failing 2017-08-10 11:27:13 +00:00

README.rst

Team and repository tags

image

OpenStack Nova

OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.

Use the following resources to learn more.

API

To learn how to use Nova's API, consult the documentation available online at:

For more information on OpenStack APIs, SDKs and CLIs in general, refer to:

Operators

To learn how to deploy and configure 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

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

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:

Other Information

During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: