openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
55,151 Commits 10 Branches 95 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
73f1fda7e9
Go to file
Eric Fried 73f1fda7e9 Bump min for oslo.service & .privsep to fix SIGHUP 
The combined fixes for the two related bugs resolve the problem where
SIGHUP breaks the nova-compute service. Bump the minimum requirements
for oslo.privsep and oslo.service to make sure these fixes are in place,
and add a reno to advertise resolution of the issue.

This also bumps oslo.utils to match the lower constraint from
oslo.service.

Change-Id: I39ead744b21a4423352a88573f327273e4d09630
Related-Bug: #1794708
Related-Bug: #1715374
2019-09-05 18:16:43 -05:00
api-guide/source Remove 'hw:cpu_policy', 'hw:mem_page_size' extra specs from API samples 2019-08-27 17:00:46 +01:00
api-ref/source Specify availability_zone to unshelve 2019-08-27 12:57:10 -04:00
devstack Merge "Add nova-multi-cell job" 2019-04-30 21:18:42 +00:00
doc Merge "Switch some GitHub URLs to point to opendev.org" 2019-08-29 13:52:07 +00:00
etc/nova Cleanup no longer required filters and add a release note. 2019-02-27 20:45:16 +00:00
gate Add cold migrate and resize to nova-grenade-multinode 2019-08-30 15:35:46 -04:00
nova Merge "re-calculate provider mapping during migration" 2019-09-04 01:00:07 +00:00
playbooks Rename the nova-grenade-live-migration job to nova-grenade-multinode 2019-08-30 15:35:46 -04:00
releasenotes Bump min for oslo.service & .privsep to fix SIGHUP 2019-09-05 18:16:43 -05:00
roles/run-post-test-hook Convert nova-next to a zuul v3 job 2019-07-23 11:32:35 -04:00
tools Replace git.openstack.org URLs with opendev.org URLs 2019-04-24 13:59:57 +08:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Delete the placement code 2019-04-28 20:06:15 +00: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
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Add cold migrate and resize to nova-grenade-multinode 2019-08-30 15:35:46 -04:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt bindep: Remove dead markers 2019-07-18 11:27:13 +01:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Remove descriptions of nonexistent hacking rules 2019-08-26 14:55:51 +09:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
lower-constraints.txt Bump min for oslo.service & .privsep to fix SIGHUP 2019-09-05 18:16:43 -05:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
README.rst Update api-ref location 2019-07-22 19:17:28 +02:00
requirements.txt Bump min for oslo.service & .privsep to fix SIGHUP 2019-09-05 18:16:43 -05:00
setup.cfg Remove nova-consoleauth 2019-07-05 15:04:47 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Tests: autospecs all the mock.patch usages 2019-08-19 09:43:10 -05:00
tox.ini Merge "tox: Keeping going with docs" 2019-08-07 20:39:56 +00:00

README.rst

Team and repository tags

image

OpenStack Nova

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