OpenStack Compute (Nova)
Go to file
Chris Behrens 8c136a8ee4 Don't delete sys_meta on instance delete
Unfortunately, we require to access instance_system_metadata to get
data (specifically at least instance_type data) for instances that have
been deleted.

There's 2 cases where this is true:

1) nova-api supports showing deleting instances when you specify a
'changes-since' param.
2) The _usage_audit_log periodic task pulls all instances during the
audit period, which includes instances that have been deleted during
that period.

This reverts commit 17bca43895, which was
attempting to fix a bug where we leave instance_system_metadata entries
undeleted from the DB.  There's not an easy way to query for the deleted
sys_meta data in an efficient manner, and leaving the entries undeleted is
the lesser of the 2 evils for now.

Fixes bug 1185190

Change-Id: I898f0546c49126dcc56a4237120082f95dc82304
(cherry picked from commit 4885aa2870)
2013-06-01 06:01:35 +00:00
bin Merge "Raise rather than generating millions of IPs." into stable/grizzly 2013-05-02 18:33:41 +00:00
contrib Enable N302: Import modules only 2013-01-25 12:11:54 -05:00
doc Wrong proxy port in nova.conf for Spice proxy 2013-05-02 10:28:12 +02:00
etc/nova Remove insecure default for signing_dir option. 2013-05-08 11:44:05 -04:00
nova Don't delete sys_meta on instance delete 2013-06-01 06:01:35 +00:00
plugins/xenserver Merge "xenapi: Adding logging for migration plugin" 2013-03-19 16:27:03 +00:00
smoketests Removed print stmts in test cases 2013-01-29 12:55:14 -05:00
tools import and install gettext in vm_vdi_cleaner.py 2013-05-01 09:49:38 -04:00
.coveragerc Update .coveragerc 2013-02-06 16:47:06 +02:00
.gitignore add .idea folder to .gitignore pycharm creates this folder 2013-03-07 17:00:22 -06:00
.gitreview Set defaultbranch in .gitreview to stable/grizzly 2013-04-11 16:29:53 +01:00
.mailmap Add the missing replacement text in devref doc. 2012-12-14 09:47:32 +08:00
.testr.conf Invert test stream capture logic for debugging. 2013-01-07 11:03:30 -08:00
CONTRIBUTING.rst Add a CONTRIBUTING file. 2012-11-21 17:04:48 -05:00
HACKING.rst docs should indicate proper git commit limit 2013-03-04 13:23:45 -07:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MANIFEST.in Finish AUTHORS transition. 2012-07-05 09:11:37 -05:00
README.rst Rename VMWare to VMware 2013-03-04 21:46:23 -08:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
openstack-common.conf Sync nova with oslo DB exception cleanup. 2013-02-25 21:32:59 +00:00
pylintrc Don't warn about C0111 (No docstrings) 2011-03-16 15:28:09 -07:00
run_tests.sh Merge "Use a fake coverage module instead of real one." 2013-02-27 00:40:07 +00:00
setup.cfg Use testr to run nova unittests. 2012-12-14 14:22:20 -08:00
setup.py Bump stable/grizzly next version to 2013.1.2 2013-05-09 23:36:57 +02:00
tox.ini Update tox.ini to support RHEL 6.x. 2013-03-07 11:25:25 -05:00

README.rst

OpenStack Nova README

OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.

OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.

Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.

To keep updated with new developments in the OpenStack project follow @openstack on Twitter.

To learn how to deploy OpenStack Nova, consult the documentation available online at:

http://docs.openstack.org

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:

http://bugs.launchpad.net/nova

Developers wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:

http://github.com/openstack/nova

Developers should also join the discussion on the mailing list, at:

https://lists.launchpad.net/openstack/

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:

http://nova.openstack.org/

For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.

-- End of broadcast