openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
55,023 Commits 9 Branches 82 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Lucian Petrut 12b361f0b4 Avoid error state for recovered instances after failed migrations 
Most users expect that if a live migration fails but the instance
is fully recovered, it shouldn't enter 'error' state. Setting
the migration status to 'error' should be enough. This simplifies
debugging, making it clear that the instance dosn't have to be
manually recovered.

This patch changed this behavior, indirectly affecting the Hyper-V
driver: Idfdce9e7dd8106af01db0358ada15737cb846395

We'll stop propagating exceptions when managing to recover the
instance, which matches the reference driver (libvirt) behavior.

Change-Id: I16c200ebf0a996865ddce5688434e9c9ad69e331
Closes-Bug: 1841411
 		2019-08-26 11:36:56 +03:00
api-guide/source doc: fix links for server actions in api guide 2019-07-26 15:47:02 -04:00
api-ref/source Update api-ref for 2.75 to add config_drive in server update response 2019-08-20 12:58:36 +00:00
devstack Merge "Add nova-multi-cell job" 2019-04-30 21:18:42 +00:00
doc Merge "doc: remove confusing docs about aggregate allocation ratios" 2019-08-22 20:13:47 +00:00
etc/nova Cleanup no longer required filters and add a release note. 2019-02-27 20:45:16 +00:00
gate Make a failure to purge_db fail in post_test_hook.sh 2019-08-21 19:21:55 +00:00
nova Avoid error state for recovered instances after failed migrations 2019-08-26 11:36:56 +03:00
playbooks Merge "Convert nova-next to a zuul v3 job" 2019-07-26 18:02:40 +00:00
releasenotes Merge "Remove deprecated [neutron]/url option" 2019-08-22 19:57:32 +00:00
roles/run-post-test-hook Convert nova-next to a zuul v3 job 2019-07-23 11:32:35 -04:00
tools Replace git.openstack.org URLs with opendev.org URLs 2019-04-24 13:59:57 +08:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Delete the placement code 2019-04-28 20:06:15 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:45:52 +00:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Process [compute] in $NOVA_CPU_CONF in nova-next 2019-08-23 14:11:48 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Add a hacking rule for useless assertions 2019-08-21 14:42:53 +09:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
README.rst Update api-ref location 2019-07-22 19:17:28 +02:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt bindep: Remove dead markers 2019-07-18 11:27:13 +01:00
lower-constraints.txt Merge "Bump minimum ksa (3.16.0) and sdk (0.34.0)" 2019-08-22 00:51:15 +00:00
requirements.txt Bump minimum ksa (3.16.0) and sdk (0.34.0) 2019-08-15 09:16:58 -05:00
setup.cfg Remove nova-consoleauth 2019-07-05 15:04:47 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Tests: autospecs all the mock.patch usages 2019-08-19 09:43:10 -05:00
tox.ini Merge "tox: Keeping going with docs" 2019-08-07 20:39:56 +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: