Comment 9 for bug 1008866

I have to handle one latest issue of this patch before I push it into "world". I try to find solution with any DB table/entry update, unfortunately it still not correctly works without updating "iscsi_targets" table.

So current solution expect this:
1/ all volume.(id)s on nova-volume on one hostX != snapshot.(id)s on the same hostX
2/ created snapshot.id < max(volume.id)
That is caused due to using/mixing "iscsi_targets.volume_id" with both "volume.id"/"snapshot.id". This workaround woks for my use case but can cause unxepected problems in some other situations.

I have seen some blueprints about changing volume_id, snapshot_id to UUID which is uniq across whole stack, so I thing this migration to UUID will solve all problems of this issue.