Dan Smith d9c696acf8 Make evacuate leave a record for the source compute host to process ... This makes the evacuate process leave a record in the database about the evacuation, and from what host it was being performed. Now, the compute manager will use that breadcrumb trail to decide whether it should delete locally-running instances, instead of just the hostname mismatch. Since this does a query by migration_type, I added a unit test to the test_db_api module to prove this actually works. DocImpact: Deprecates the workarounds/destroy_after_evacuate config option Related to blueprint robustify-evacuation Closes-Bug: #1471887 Change-Id: I972c224dfb954a9f06e221c9235ee6e4889c2619		2015-07-06 15:40:07 -07:00
..
functional	Merge "Add microversion to allow server search option ip6 for non-admin"	2015-06-26 23:58:33 +00:00
unit	Make evacuate leave a record for the source compute host to process	2015-07-06 15:40:07 -07:00
__init__.py	move all tests to nova/tests/unit	2014-11-12 15:31:08 -05:00
fixtures.py	Block subtractive operations in migrations for Kilo and beyond	2015-06-30 19:56:43 -07:00