OpenStack Compute (Nova)
Go to file
Balazs Gibizer 9cacaad14e cleanup evacuated instances not on hypervisor
When the compute host recovers from a failure the compute manager
destroys instances that were evacuated from the host while it was down.
However these code paths only consider evacuated instances that are
still reported by the hypervisor. This means that if the compute
host is recovered in a way that the hypervisor lost the definition
of the instances (for example the compute host was redeployed) then
the allocation of these instances will not be deleted.

This patch makes sure that the instance allocation is cleaned up
even if the driver doesn't return that instance as exists on the
hypervisor.

Note that the functional test coverage will be added on top as it needs
some refactoring that would make the bugfix non backportable.

Change-Id: I4bc81b482380c5778781659c4d167a712316dab4
Closes-Bug: #1724172
2019-05-28 16:04:14 +02:00
api-guide/source [Trivial doc change] Admin can overwrite the locked_reason of an owner 2019-05-14 19:04:08 +00:00
api-ref/source Merge "Update description of valid whitelist for non-admin user" 2019-05-23 07:30:53 +00:00
devstack Merge "Add nova-multi-cell job" 2019-04-30 21:18:42 +00:00
doc Merge "[Docs] Fix minor typo" 2019-05-25 00:54:42 +00:00
etc/nova Replace git.openstack.org URLs with opendev.org URLs 2019-04-24 13:59:57 +08:00
gate Pass --nic when creating servers in evacuate integration test script 2019-04-01 09:58:01 -04:00
nova cleanup evacuated instances not on hypervisor 2019-05-28 16:04:14 +02:00
playbooks/legacy Enable image type query support in nova-next 2019-05-07 10:24:21 -07:00
releasenotes Add --before to nova-manage db archive_deleted_rows 2019-05-23 11:07:08 +10: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 Skip novnc tests in multi-cell job until bug 1830417 is fixed 2019-05-24 14:23:05 -04:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Hacking N362: Don't abbrev/alias privsep import 2019-04-04 20:42:43 +00: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 Docs: modernise links 2018-03-24 20:27:11 +08:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Merge "Bindep does not catch missing libpcre3-dev on Ubuntu" 2018-02-14 07:31:09 +00:00
lower-constraints.txt Move patch_exists() to nova.test.TestCase for reuse 2019-05-24 16:22:48 +01:00
requirements.txt Merge "Add image type capability flags and trait conversions" 2019-05-04 20:32:15 +00:00
setup.cfg Update Python 3 test runtimes for Train 2019-05-09 17:35:43 +08:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Move patch_exists() to nova.test.TestCase for reuse 2019-05-24 16:22:48 +01:00
tox.ini Delete the placement code 2019-04-28 20:06:15 +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: