openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
56,259 Commits 10 Branches 95 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
26d695876a
Go to file
Matt Riedemann 26d695876a Use graceful_exit=True in ComputeTaskManager.revert_snapshot_based_resize 
This passes graceful_exit=True to the wrap_instance_event decorator
in ComputeTaskManager.revert_snapshot_based_resize so that upon successful
completion of the RevertResizeTask, when the instance is hard destroyed
from the target cell DB (used to create the action/event), a traceback
is not logged for the InstanceActionNotFound exception.

The same event is also finished in the source cell DB upon successful
completion of the RevertResizeTask. Note that there are other ways we
could have done this, e.g. moving the contents of the _execute() method
to another method and then putting that in an EventReporter context with
the source cell context/instance, but this was simpler.

Part of blueprint cross-cell-resize

Change-Id: Ibb32f7c19f5f2ec4811b165b8df748d1b7b0f9e4
2019-12-23 10:10:57 -05:00
api-guide/source api-guide: flesh out the server actions section 2019-12-02 15:13:48 -05:00
api-ref/source api-ref: avoid mushy wording around server.image description 2019-12-13 12:39:01 -05:00
devstack Merge "Find instance in another cell during floating IP re-association" 2019-09-13 15:19:55 +00:00
doc Add cross-cell resize tests for _poll_unconfirmed_resizes 2019-12-23 10:10:57 -05:00
etc/nova Remove unused rootwrap filters 2019-12-04 12:32:49 +01:00
gate Convert legacy nova-live-migration and nova-multinode-grenade to py3 2019-11-14 16:06:02 +00:00
nova Use graceful_exit=True in ComputeTaskManager.revert_snapshot_based_resize 2019-12-23 10:10:57 -05:00
playbooks Enable cross-cell resize in the nova-multi-cell job 2019-12-23 10:10:57 -05:00
releasenotes Add cross-cell resize policy rule and enable in API 2019-12-23 10:10:57 -05:00
roles Enable cross-cell resize in the nova-multi-cell job 2019-12-23 10:10:57 -05:00
tools Keep pre-commit inline with hacking and fix whitespace 2019-12-12 14:56:39 +00: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
.pre-commit-config.yaml Keep pre-commit inline with hacking and fix whitespace 2019-12-12 14:56:39 +00:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Enable cross-cell resize in the nova-multi-cell job 2019-12-23 10:10:57 -05:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Added openssh-client into bindep 2019-10-23 07:21:23 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Merge "Make it easier to run a selection of tests relevant to ongoing work" 2019-11-22 20:58:18 +00:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
lower-constraints.txt Revert "(Temporarily) readd bare support for py27" 2019-12-13 12:45:52 +00:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
README.rst Start README.rst with a better title 2019-11-19 17:29:28 +01:00
requirements.txt Revert "(Temporarily) readd bare support for py27" 2019-12-13 12:45:52 +00:00
setup.cfg Revert "(Temporarily) readd bare support for py27" 2019-12-13 12:45:52 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Revert "(Temporarily) readd bare support for py27" 2019-12-13 12:45:52 +00:00
tox.ini Stop testing Python 2 2019-11-18 10:31:06 +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), 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: