OpenStack Compute (Nova)
Go to file
Kashyap Chamarthy c07495d9d6 Add a workaround to skip hypervisor version check on LM
When turned on, this will disable the version-checking of hypervisors
during live-migration.  This can be useful for operators in certain
scenarios when upgrading.  E.g. if you want to relocate all instances
off a compute node due to an emergency hardware issue, and you only have
another old compute node ready at the time.

Note, though: libvirt will do its own internal compatibility checks, and
might still reject live migration if the destination is incompatible.

Closes-Bug: #1982853

Change-Id: Iec387dcbc49ddb91ebf5cfd188224eaf6021c0e1
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
(cherry picked from commit 00ed8a232b)
2023-01-27 10:54:24 +01:00
api-guide/source [doc] port-resource-request-groups not landed in Xena 2021-09-06 13:03:22 +02:00
api-ref/source api-ref: Adjust BFV rescue non-support note. 2021-11-22 14:19:25 -05:00
devstack Switch to new rolevar for run-tempest role 2021-04-09 16:06:10 +00:00
doc enable blocked VDPA move operations 2022-11-17 15:15:44 +00:00
etc/nova Merge "Add missing [oslo_reports] options" 2021-08-24 13:41:16 +00:00
gate Enable unified limits in the nova-next job 2022-03-04 03:42:14 +00:00
nova Add a workaround to skip hypervisor version check on LM 2023-01-27 10:54:24 +01:00
playbooks zuul-job for Adds Pick guest CPU architecture based on host arch 2022-02-25 16:55:43 -05:00
releasenotes Add a workaround to skip hypervisor version check on LM 2023-01-27 10:54:24 +01:00
roles [OVN] Adapt the live-migration job scripts to work with OVN 2021-03-15 09:41:03 +00:00
tools tools: Ignore bot-generated branch creation patches 2021-09-27 10:20:34 +01: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 [stable-only] Update .gitreview for stable/yoga 2022-03-11 11:01:28 +01:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.pre-commit-config.yaml Add autopep8 to tox and pre-commit 2021-11-08 12:37:27 +00:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml nova-live-migration tests not needed for Ironic 2022-08-23 12:17:33 -07:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00:00
HACKING.rst Add two new hacking rules 2021-09-01 12:26:52 +01: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: Remove references to XenAPI driver 2020-08-31 15:53:31 +01:00
bindep.txt tests: Allow bindep and test-setup.sh to run on EL distros 2021-06-18 12:34:27 +01:00
mypy-files.txt Follow up for unified limits 2022-03-04 03:42:58 +00:00
requirements.txt Add logic to enforce local api and db limits 2022-02-24 16:21:02 +00:00
setup.cfg Lightbits LightOS driver 2022-02-22 16:17:29 +01:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Move optional build dependencies to 'extras' 2022-01-28 12:27:06 +00:00
tox.ini [CI] Install dependencies for docs target 2022-04-28 20:14:34 +02:00

README.rst

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, 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: