openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
60,714 Commits 10 Branches 94 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
11301e7e3f
Go to file
Dan Smith 11301e7e3f Fix vmdk_allowed_types checking 
This restores the vmdk_allowed_types checking in create_image()
that was unintentionally lost by tightening the
qemu-type-matches-glance code in the fetch patch recently. Since we
are still detecting the format of base images without metadata, we
would have treated a vmdk file that claims to be raw as raw in fetch,
but then read it like a vmdk once it was used as a base image for
something else.

Change-Id: I07b332a7edb814f6a91661651d9d24bfd6651ae7
Related-Bug: #2059809
(cherry picked from commit 08be7b2a0d)
2024-07-04 17:12:23 +02:00
api-guide/source Merge "doc: Remove crud from conf.py file" 2023-12-05 12:56:37 +00:00
api-ref/source Reject AZ changes during aggregate add / remove host 2024-05-10 09:36:37 +00:00
devstack Merge "[codespell] doc,devstack and gate typos" 2023-12-11 17:44:04 +00:00
doc Reject AZ changes during aggregate add / remove host 2024-05-10 09:36:37 +00:00
etc/nova Fix missing oslo.versionedobjects library option 2023-09-19 04:43:01 +00:00
gate [S-RBAC] adapt nova-next for port's binding:profile field change 2024-02-22 19:39:39 +00:00
nova Fix vmdk_allowed_types checking 2024-07-04 17:12:23 +02:00
playbooks Test ceph-multistore with a real image 2022-11-09 11:34:02 -08:00
releasenotes Reject AZ changes during aggregate add / remove host 2024-05-10 09:36:37 +00:00
roles run-evacuate-hook: Check cinder before creating BFV server 2024-02-06 17:52:30 +00:00
tools pre-commit: Add mypy 2023-12-20 18:31:47 +00:00
.coveragerc Fix coverage issues with eventlet 2023-11-10 20:12:31 +00:00
.git-blame-ignore-revs [codespell] ignore codespell in git blame 2023-12-15 12:35:03 +00: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/2024.1 2024-03-19 15:30:13 +00:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.pre-commit-config.yaml pre-commit: Bump linter versions 2023-12-20 18:33:33 +00:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Fix disk_formats in ceph job tempest config 2024-07-02 18:54:59 -07:00
bindep.txt Fix bindep for Debian bookworm 2023-08-13 09:16:27 +02:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00:00
HACKING.rst [codespell] start fixing all the typos 2023-10-03 00:51:35 +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 HyperV: Remove extra specs of HyperV driver 2024-02-13 20:25:22 +00:00
requirements.txt Merge "Packed virtqueue support was added." 2023-11-30 12:12:03 +00:00
setup.cfg Merge "Update python classifier in setup.cfg" 2024-03-15 10:01:27 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt pre-commit: Add mypy 2023-12-20 18:31:47 +00:00
tox.ini [stable-only] Update TOX_CONSTRAINTS_FILE for stable/2024.1 2024-03-19 15:30:51 +00: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), 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: