openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
60,231 Commits 9 Branches 84 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Dan Smith 6ff3237149 Bump nova-ceph-multstore timeout 
The recent change(s) to enable a lot more SSHABLE checks puts the
runtime of the ceph job really close to the 2h timeout even when
things are working. Sometimes it times out before it finishes even
though things are progressing. Bump the timeout to avoid that.

Also bump us to 8G swap to match what is set on the parent ceph job
when we upgraded to jammy. We could just unset this, but better to
pin it high in case that job (defined elsewhere) changes. Our job
is the largest ceph job, so it makes sense that it keeps its own
swap level high.

Change-Id: I6cefd87671614d87d92e4675fbc989fc9453c8b9
 		2023-05-10 17:54:38 -07:00
api-guide/source Merge "Fix link to Cyborg device profiles API" 2022-12-20 15:03:28 +00:00
api-ref/source Microversion 2.94: FQDN in hostname 2023-01-17 10:59:37 -05:00
devstack Skip UnshelveToHostMultiNodesTest in nova-multi-cell 2022-08-31 16:52:21 +02:00
doc Merge "add hypervisor version weigher" 2023-05-04 01:29:06 +00:00
etc/nova Add os_vif in nova-config-generator 2022-11-07 16:32:28 +01:00
gate Enable unified limits in the nova-next job 2022-03-04 03:42:14 +00:00
nova Merge "Revert "Debug Nova APIs call failures"" 2023-05-09 23:54:04 +00:00
playbooks Test ceph-multistore with a real image 2022-11-09 11:34:02 -08:00
releasenotes Merge "add hypervisor version weigher" 2023-05-04 01:29:06 +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 Bump nova-ceph-multstore timeout 2023-05-10 17:54:38 -07:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00:00
HACKING.rst Add a hacking rule for the setDaemon method 2022-11-14 13:04:05 +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 Remove the PowerVM driver 2022-08-02 15:31:19 +02:00
bindep.txt Adapt bindep ubuntu-jammy 2022-05-06 08:51:15 +02:00
mypy-files.txt cpu: interfaces for managing state and governor 2023-02-09 07:04:02 +01:00
requirements.txt db: Remove legacy migrations 2023-02-01 17:00:03 +00:00
setup.cfg Update gate jobs as per the 2023.1 cycle testing runtime 2022-11-22 13:44:26 -06: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 Allow running functional-py311 2023-04-05 08:18:55 -07: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 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: