Matt Riedemann 9b121e3c37 Cleanup comments around claim_resources method ... This removes some old comments about how things worked prior to Pike where the ResourceTracker would "heal" allocations on the compute node during the periodic update_available_resource task. That code was removed via change I39d93dbf8552605e34b9f146e3613e6af62a1774 (Rocky) and change If272365e58a583e2831a15a5c2abad2d77921729 (Stein). There are also old comments in here about not using claim_resources during forced live migrate and evacuate and instead call the scheduler with a hint to skip filters, but that hasn't happened yet so the "In Queens" portion is just removed since it's misleading (and somewhat embarrassing at this point that it's not fixed yet). Finally, the NOTE above claim_resources() which says it's only called in two places is updated since it's actually called in three places since it's also used in the forced evacuate destination case. A follow up change will deal with the TODO about erroring out in the final else case in claim_resources_on_destination(). Change-Id: I1822ac911ed8dbbb482fd4c13591d86b0c518321		2019-03-19 09:46:25 -04:00
..
__init__.py	Removed copyright from empty files	2014-02-27 14:27:54 +02:00
base.py	Create class hierarchy for tasks in conductor	2015-07-30 17:35:56 +03:00
live_migrate.py	Cleanup comments around claim_resources method	2019-03-19 09:46:25 -04:00
migrate.py	Transfer port.resource_request to the scheduler	2019-02-07 20:06:49 -05:00