Comment 5 for bug 1289931

Thats the point isn't it? Such enforcement doesn't belong in the Cinder level, any incompatibility should be up to the driver level. The mere fact that it didnt need to be there and still was being held to until now shows its not necessary at that level.

It shouldn't matter if the backend storage is usb sticks, floppy drives, sparse images, sans, etc Cinder should remain simply iscsi to iscsi and again any such enforcement to incompatibility should be at the driver level who will have more insight into the actual storage medium and process. By enforcing this, you are in fact forcing a compatibility matrix mentioned above.

At the very least it should be an option to disable / enable.