John Griffith e3d7f8c7de Detect and fix issues caused by vol ID migration ... The migration from volume ID to UUID neglected to update the provider_location field on the volume. As a result the iqn and volume name no long match and existing volumes are no longer able to be attached after an upgrade (essex -> folsom and then nova-vol->cinder). This patch adds a method to the volume driver that will check for the mismatch of volume name in the iqn during service start up. If detected it will update the provider_location field in the database to include the new ID. Also it will create a symlink to the device backing file that also has the correct naming convention. Note: We don't disturb an connections that are currently attached. For this case we add a check in manager.detach and do any provider_location cleanup that's needed at that time. This ensures that connections persist on restarts of tgtd and reboot. Change-Id: Ib41ebdc849ebc31a9225bdc4902209c5a23da104 Fixes: bug 1065702		2012-10-30 07:06:10 -06:00
..
api-metadata.filters	Provide rootwrap filters for nova-api-metadata	2012-07-24 17:03:13 +02:00
compute.filters	Use lvs instead of os.listdir in _cleanup_lvm	2012-09-06 04:11:14 +04:00
network.filters	Migrate existing routes from flat_interface	2012-06-25 13:17:23 -07:00
volume.filters	Detect and fix issues caused by vol ID migration	2012-10-30 07:06:10 -06:00