Comment 4 for bug 1023768

After a discussion with John Griffith we managed to reach a consensus of understanding about what I was getting at.

Basically my concern is that the provider location info is maintained only in the volumes table meaning that an entry in the snapshots table is potentially useless unless we keep the associated entry in the volumes table around.

This means that even when a back end supports deleting a volume that has associated snapshots right we can't actually delete the entry from the volumes table - we are required to keep the relevant entry around in volumes table, and at best we can mark it as deleted, leading to a bloating of the volumes table.

John suggested that my concerns may actually line up with the work being done by Chris McGowan from Piston Cloud in the area of "Making a snapshot just a special case of Volume".

Fergal.