OpenStack Compute (Nova)
Go to file
Sean Mooney 8449b7caef [compute] always set instance.host in post_livemigration
This change add a new _post_live_migration_update_host
function that wraps _post_live_migration and just ensures
that if we exit due to an exception instance.host is set
to the destination host.

when we are in _post_live_migration the guest has already
started running on the destination host and we cannot revert.
Sometimes admins or users will hard reboot the instance expecting
that to fix everything when the vm enters the error state after
the failed migrations. Previously this would end up recreating the
instance on the source node leading to possible data corruption if
the instance used shared storage.

Change-Id: Ibc4bc7edf1c8d1e841c72c9188a0a62836e9f153
Partial-Bug: #1628606
2022-10-07 12:23:13 +00:00
api-guide/source Updated Suspend definition in server concepts doc 2022-08-02 04:18:10 +00:00
api-ref/source Updated flavors doc 2022-09-17 17:40:52 +00:00
devstack Skip UnshelveToHostMultiNodesTest in nova-multi-cell 2022-08-31 16:52:21 +02:00
doc Merge "Update nova-manage doc page" 2022-09-23 03:40:59 +00:00
etc/nova etc: Highlight absence of packages from config gen 2022-07-14 09:53:52 +01:00
gate Enable unified limits in the nova-next job 2022-03-04 03:42:14 +00:00
nova [compute] always set instance.host in post_livemigration 2022-10-07 12:23:13 +00:00
playbooks zuul-job for Adds Pick guest CPU architecture based on host arch 2022-02-25 16:55:43 -05:00
releasenotes Merge "Update master for stable/zed" 2022-09-22 12:05:25 +00:00
roles [OVN] Adapt the live-migration job scripts to work with OVN 2021-03-15 09:41:03 +00:00
tools Test setting the nova job to centos-9-stream 2022-07-13 14:08:03 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore db: Enable auto-generation of API DB migrations 2021-10-18 20:26:18 +01: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
.pre-commit-config.yaml pre-commit: Sync hacking version, bump plugins 2022-04-05 13:02:18 +01:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Switch to 2023.1 Python3 unit tests and generic template name 2022-09-16 10:02:19 +00:00
bindep.txt Adapt bindep ubuntu-jammy 2022-05-06 08:51:15 +02:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00:00
HACKING.rst Add missing descriptions in HACKING.rst 2022-08-31 12:12:07 +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
mypy-files.txt Basics for PCI Placement reporting 2022-08-25 10:00:10 +02:00
README.rst Remove the PowerVM driver 2022-08-02 15:31:19 +02:00
requirements.txt requires os-traits >= 2.9.0 2022-09-19 08:47:51 +00:00
setup.cfg Remove the PowerVM driver 2022-08-02 15:31:19 +02:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Remove the PowerVM driver 2022-08-02 15:31:19 +02:00
tox.ini Add source dev parsing for vdpa interfaces 2022-08-22 14:57:21 +01:00

OpenStack Nova

image

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 and OpenStack Ironic.

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: