Chris Behrens 04d9fb4067 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-05-29 17:48:19 -04:00
..
sqlalchemy	Don't delete sys_meta on instance delete	2013-05-29 17:48:19 -04:00
__init__.py	rename node_name to host	2010-08-31 16:48:41 -07:00
api.py	Merge "Add update method of security group name and description"	2013-05-29 00:11:02 +00:00
base.py	Use oslo-config-2013.1b4	2013-02-19 21:16:32 -08:00
migration.py	Compact pre-Grizzly database migrations.	2012-11-19 10:45:31 -05:00