OpenStack Compute (Nova)
Go to file
Sean Mooney 387823b36d Fix max cpu topologies with numa affinity
Nova has never supported specifying per numa node
cpu toplogies. Logically the  cpu toplogy of a guest
is independent of its numa toplogy and there is no
way to model different cpu toplogies per numa node
or implement that in hardware.

The presence of the code in nova that allowed the generation
of these invalid configuration has now been removed as it
broke the automatic selection of cpu topologies based
on hw:max_[cpus|sockets|threads] flavor and image properties.

This change removed the incorrect code and related unit
tests with assert nova could generate invalid topologies.

Closes-Bug: #1910466
Change-Id: Ia81a0fdbd950b51dbcc70c65ba492549a224ce2b
2021-06-18 12:34:22 +01:00
api-guide/source Trival change: spell error of Shelve 2021-04-07 02:10:19 +00:00
api-ref/source trivial: fix word duplication in api ref 2021-03-22 09:22:39 +01:00
devstack Switch to new rolevar for run-tempest role 2021-04-09 16:06:10 +00:00
doc Merge "docs: Add releases to libvirt distro support matrix" 2021-06-11 14:40:22 +00:00
etc/nova Allow versioned discovery unauthenticated 2020-04-03 21:24:28 +00:00
gate gate: Remove test_evacuate.sh 2021-06-15 17:35:20 +01:00
nova Fix max cpu topologies with numa affinity 2021-06-18 12:34:22 +01:00
playbooks zuul: Replace grenade and nova-grenade-multinode with grenade-multinode 2021-04-29 11:05:58 +01:00
releasenotes Fix max cpu topologies with numa affinity 2021-06-18 12:34:22 +01:00
roles [OVN] Adapt the live-migration job scripts to work with OVN 2021-03-15 09:41:03 +00:00
tools Move 'check-cherry-picks' test to gate, n-v check 2021-06-16 15:51:38 +01:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore tox: Integrate mypy 2020-05-15 15:59:53 +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 Switch to hacking 2.x 2020-01-17 11:30:40 +00:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Move 'check-cherry-picks' test to gate, n-v check 2021-06-16 15:51:38 +01:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00:00
HACKING.rst Add a hacking rule for assert_has_calls 2020-09-28 23:08:15 +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 docs: Remove references to XenAPI driver 2020-08-31 15:53:31 +01:00
bindep.txt bindep: Install python3 and python3-devel on CentOS 8 and Fedora 2020-10-03 13:20:21 +01:00
lower-constraints.txt requirements: Add types-paramiko 2021-06-09 15:18:47 +01:00
mypy-files.txt mypy: Add type annotations to 'nova.pci' 2021-04-26 18:06:21 +01:00
requirements.txt Use the new type HostDomainOpt. 2021-05-19 10:29:56 +02:00
setup.cfg setup.cfg: Resolve warning 2021-03-09 12:49:50 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt requirements: Add types-paramiko 2021-06-09 15:18:47 +01:00
tox.ini Move 'check-cherry-picks' test to gate, n-v check 2021-06-16 15:51:38 +01: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: