openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
54,132 Commits 9 Branches 81 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
melanie witt 0ae53f2bf0 Revert "Fix target_cell usage for scatter_gather_cells" 
This reverts commit 3cc3cc453d.

We had determined that this commit had not actually fixed any bug or
issue with:

  TypeError: Can't upgrade a READER transaction to a WRITER
             mid-transaction

and the real fix was change Id24dea7465bafc1f6f58c4a121c4ffb35b7a634a.

This reverts the unnecessary commit in order to simplify the code and
it's possible that targeting the context before spawning a thread will
result in decreased cell cache lock contention once the threads are
spawned.

Related-Bug: #1722404

 Conflicts:
	nova/context.py

NOTE(melwitt): The conflict is due to change
I861b223ee46b0f0a31f646a4b45f8a02410253cf which is new since the
original commit had landed.

Change-Id: I3890d14d8679b96cfebcd735f3b03ec808730b5c
 		2019-05-08 02:46:50 +00:00
api-guide/source Documentation for bandwidth support 2019-03-18 11:24:56 +01:00
api-ref/source Remove '/os-cells' REST APIs 2019-04-16 18:26:13 +01:00
devstack Merge "Add nova-multi-cell job" 2019-04-30 21:18:42 +00:00
doc Merge "Delete the placement code" 2019-05-04 09:16:41 +00:00
etc/nova Replace git.openstack.org URLs with opendev.org URLs 2019-04-24 13:59:57 +08:00
gate Pass --nic when creating servers in evacuate integration test script 2019-04-01 09:58:01 -04:00
nova Revert "Fix target_cell usage for scatter_gather_cells" 2019-05-08 02:46:50 +00:00
playbooks/legacy OpenDev Migration Patch 2019-04-19 19:45:52 +00:00
releasenotes Merge "Delete the placement code" 2019-05-04 09:16:41 +00: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 Make nova-tox-functional-py36 reusable 2019-05-04 10:50:56 -06:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Hacking N362: Don't abbrev/alias privsep import 2019-04-04 20:42:43 +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 Docs: modernise links 2018-03-24 20:27:11 +08:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Merge "Bindep does not catch missing libpcre3-dev on Ubuntu" 2018-02-14 07:31:09 +00:00
lower-constraints.txt Merge "Add image type capability flags and trait conversions" 2019-05-04 20:32:15 +00:00
requirements.txt Merge "Add image type capability flags and trait conversions" 2019-05-04 20:32:15 +00:00
setup.cfg Delete the placement code 2019-04-28 20:06:15 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Bump to hacking 1.1.0 2019-04-12 16:23:49 +01:00
tox.ini Delete the placement code 2019-04-28 20:06:15 +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: