Description of problem:
On an iSCSI storage domain a lun can be connected through multiple targets, each target from a different IP.
Today, once we add an iSCSI storage domain all the targets that were connected from the host will be used part of the storage domain definition in the DB (storage_server_connections table).
The user should have the ability to choose the targets that he/she desire to use for that LUN, same it is being done today for LUNs
We should add checkboxes for each target of each LUN.
Once the user will connect to another target which is being used by the same LUN the user will hace the ability to choose to connect from both targets of only one of them.
IMHO connected targets should not be disconnected for an existing storage domain so those should be marged as greyed out.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create an iSCSI storage domain with once connected target and one LUN
2. Edit the iSCSI storage and try to connect to another target which is used for the same LUN
The host is connected to this new target although the storage domain is only configured in the engine with one target
The user should be able to choose which target to be used for his/her storage domain.
Created attachment 1240945 [details]
Created attachment 1240946 [details]
iSCSI targets - UX suggested solution
Closing old RFEs.
If relevant, please re-open and explain why.
As always- patches are welcomed!
This is blocking bug #1387083, which affects storage HA.
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.
Switching the RFE to downstream since, it has lots of customer interest.
Going through customer cases, there is another one, that points to another related bz#1172354.