Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1172604

Summary: [RFE] - Improve iSCSI bonding UI and UX
Product: Red Hat Enterprise Virtualization Manager Reporter: Laura Novich <lnovich>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED NOTABUG QA Contact: Raz Tamir <ratamir>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.0CC: amureini, ehildesh, jhradile, lpeer, lsurette, rbalakri, Rhev-m-bugs, scohen, srevivo, tnisan, ykaul, ylavi
Target Milestone: ---Keywords: FutureFeature, Improvement, UserExperience
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-11-26 12:33:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Laura Novich 2014-12-10 12:56:42 UTC
Description of problem:
After consulting with many, and reading the bzs that are related to this issue, it is apparent that work needs to be done on how customers are to implement this version. 
The current method is bulky complicated and involves several steps which have several points of failure.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
I propose the UI should be changed to a wizard. The rationale is based on this:

Customers will implement iSCSI multithread either with one or more initiators and with one or more or even no dedicated iSCSI domains, or any combination thereof, making it hard to channel the customer into how to confure the feature. If there was a  wizard that can look at the customer's setup and direct them accordingly, it would be a much more user friendly experience.

Additional info:
information is based on 
https://bugzilla.redhat.com/show_bug.cgi?id=1160040 
https://bugzilla.redhat.com/show_bug.cgi?id=1112861#c3
https://bugzilla.redhat.com/show_bug.cgi?id=1094002#c5

Comment 2 Yaniv Lavi 2015-04-28 07:46:51 UTC
Will not make it to 3.6, pushing to future.

Comment 3 Yaniv Lavi 2016-01-11 15:36:16 UTC
Can we have someone review how we can improve here for the UX aspect?

Comment 4 Einav Cohen 2016-01-11 15:41:31 UTC
(In reply to Yaniv Dary from comment #3)
> Can we have someone review how we can improve here for the UX aspect?

adding Eldan/Serena.

Comment 5 Eldan Hildesheim 2016-01-12 13:01:37 UTC
Hi,
I spoke with Allon Mureinik, Yaniv Kaul and other workers in oVirt including IT.
Few things:
-Seems like the process can start from the Storage Tab - which is much more logic.
-Instead of gathering Targets, we should perhaps show the domains.

Scenario:
The user will select a number of domains.
The user will select a number of networks.
A new connection will be shown in the table according the steps above.
 
(Off course, we should tell the user that other Domains in the same Target group, will be assign as well).

We should add a notification in the network level that part of them participate in such a connection.

IMPORTANT:
2 issues to consider:
-Datacenter level will probably be removed in 4.0
-Are we going to have a new type of Network: Storage network?

I propose to get final decisions regarding those 2 issues and only then continue, since all the UX can change dramatically.

Comment 6 Yaniv Lavi 2016-01-13 09:11:03 UTC
(In reply to Eldan Hildesheim from comment #5)
> Hi,
> I spoke with Allon Mureinik, Yaniv Kaul and other workers in oVirt including
> IT.
> Few things:
> -Seems like the process can start from the Storage Tab - which is much more
> logic.
> -Instead of gathering Targets, we should perhaps show the domains.
> 
> Scenario:
> The user will select a number of domains.
> The user will select a number of networks.
> A new connection will be shown in the table according the steps above.
>  
> (Off course, we should tell the user that other Domains in the same Target
> group, will be assign as well).
> 
> We should add a notification in the network level that part of them
> participate in such a connection.
> 
> IMPORTANT:
> 2 issues to consider:
> -Datacenter level will probably be removed in 4.0

Not likely to happen in 4.0.

> -Are we going to have a new type of Network: Storage network?

Not likely to happen in 4.0.

> 
> I propose to get final decisions regarding those 2 issues and only then
> continue, since all the UX can change dramatically.

Comment 8 Yaniv Lavi 2016-01-31 14:41:47 UTC
I would create a design with this with dc removal in mind, but without storage network.

Comment 9 Yaniv Lavi 2017-11-26 12:33:53 UTC
Eldan looked into this and didn't see much room for improvement. Closing until more clear improvements are opened.

Comment 10 Red Hat Bugzilla 2023-09-14 02:52:11 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days