Bug 990612
Summary: | network from external network provider shouldn't be displayed in setupNetwork. | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Meni Yakove <myakove> |
Component: | ovirt-engine-webadmin-portal | Assignee: | Lior Vernia <lvernia> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Meni Yakove <myakove> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.3.0 | CC: | acathrow, bazulay, danken, ecohen, iheim, masayag, myakove, Rhev-m-bugs, yeylon |
Target Milestone: | --- | ||
Target Release: | 3.3.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | network | ||
Fixed In Version: | is18 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1019461 |
Description
Meni Yakove
2013-07-31 14:35:35 UTC
Why shouldn't they be shown there? Because it clutters the GUI? I personally like to have plenty of information on dialog boxes... You can't attach external networks to interface in setupNetworks so they don't belong there if you can't use them. Well I find seeing all networks useful (e.g. for telling me which network names are already taken), as long as it is clear which networks are native and which are provided. But let's let someone with GUI knowhow think about it. Well, I see both your points. Meni is correct that it is confusing to have networks that shouldn't be statically attached to NICs in a dialog that is used to statically attach networks to NICs. Dan is correct that it would be useful to see external networks, because it would help a user keep in mind that he may want to leave NICs free for these networks that might be attached dynamically. So, may I offer two alternatives for a solution that will accommodate both views? 1. Somehow mark external networks, either by a different color or some icon. AND / OR 2. Show an error message when external networks are dragged unto NICs (rather than allow the user to press OK and only then get an error - that probably should have been done anyway). Best solution is to probably have both. Sound good? (In reply to Lior Vernia from comment #4) > > Best solution is to probably have both. Sound good? Yes. For the benefit of the color-blind, I vote for "alien" icon Having talked to a designer about this, the proposed solution is to have the external networks listed under a different category on the right-hand-side of the dialog with an explanation, to gray them out and to make them undraggable. rhevm-3.3.0-0.25.beta1.el6ev.noarch Closing - RHEV 3.3 Released Closing - RHEV 3.3 Released |