Description of problem: The MTU field in network window, Breaks the window layout. it doesn't look so good. Because in the new version added the custom field, it now breaking the layout. Version-Release number of selected component (if applicable): oVirt Engine Version: 3.5.0-0.0.master.20140804172041.git23b558e.el6 How reproducible: always Steps to Reproduce: 1. Create new network or edit exist one. 2. 3. Actual results: MTU field Breaking the layout with the additional custom field. Expected results: Should look straight. Additional info:
*** Bug 1127575 has been marked as a duplicate of this bug. ***
Since Bug 1127575 was closed, adding UserExperience here...
Eldan - can you please help out here? more details in the duplicate bug 1127587 - just sitting with the relevant network developer and closing this in a short loop makes sense here. thanks.
(In reply to Einav Cohen from comment #3) > Eldan - can you please help out here? more details in the duplicate bug > 1127587 - just sitting with the relevant network developer and closing this > in a short loop makes sense here. thanks. correction: duplicate bug for reference is Bug 1127575. thanks.
Eldan: Clarification: Take a look at attachment 924778 [details]: You can see that the entire "Network Parameters" section is looking quite messy. In particular, it seems that the 'MTU' field (http://i.imgur.com/sMpA6IC.png) is root cause for the messy look & feel (i.e. the "Enable VLAN Tagging", "VM Network" and "Network Label" fields are pretty-much OK, but the "MTU" field (with the two radio buttons, one of them containing a text-box, etc.) seems to mess up the entire layout. So we need to tweak the layout for this section so that it will look better; I guess that it can involve changing only the "MTU" field layout, or maybe tweaking all of the fields in the "Network Parameters" section so that it will look reasonable - not sure, I am leaving this up to you, the UXD expert :) I suggest working with Alona (BZ assignee) in a short loop to fix this issue (again, I assume it will only require very few tweaks) - it would probably be more efficient than going back and forth with Liz and I on the solution. can you please do that? thanks.
Created attachment 928723 [details] edit logical network
(In reply to Eldan Hildesheim from comment #6) > Created attachment 928723 [details] > edit logical network Thanks, Eldan; I am missing in your suggestion the text-box for entering a Custom MTU (see http://i.imgur.com/sMpA6IC.png - note the text-box within the "Custom" radio-button) - where will it be in your design?
Created attachment 932549 [details] arranged layout
verified on Red Hat Enterprise Virtualization Manager Version: 3.5.0-0.11.beta.el6ev the reason for the new MTU radiobutton is that defualt MTU is now configurable for the engine engine-config -s "DefaultMtu=1500"
oVirt 3.5 has been released and should include the fix for this issue.