Created attachment 933815 [details] vm allocation with ux and graphic problems Description of problem: -Allocation area is to crowded -Different UX for: Adding disk from Grid VM > sub tab disks and Adding Disks from New VM Dialogue > left tab Allocation -Lots of graphics style problems. -The Solution Screen shot also solves bug:1048976 Solution: 1. Storage Allocation and Disks Allocation can have a separate left tab 2. Use same Disk dialogue as in the grid new disk. 3. Use Expand/Collapse section like in ‘run once’/virt 4. Use same font as other system font - CPU shares, CPU pinning... 5. Same font header as other headers - Memory allocation 6. Left grey Background, enlarge till the bottom. 7. Add lock/unlock icon to Instance Type as well -> this is very important since it comes to show that all properties are locked with instance type. 8. Align locked/unlock icons symbol
Created attachment 933816 [details] vm allocation fix
Set to virt to drive as most items there seem to be virt-related. Naturally, the storage team will collaborate on storage items as needed. Michal - do we want to clone a separate BZ for the disks left tab?
Eldan, These suggestions look great. A few comments after looking closer: 1) Would you please make the new way that the user can get help on a field a bit stronger visually? It's hard to notice that this is an option in the current design. 2) The fields that you show in the new design for a disk should be reflected based on what the user can actually change in this case. For example, currently the user can't change the disk size since it's based on the source disk that it was cloned from. The new design should be accurate with respect to all fields to avoid any confusion in implementation. Thanks, Liz
since fields is this sub tab are SLA and storage, moving to SLA to handle this one
As I understood from storage developers, according to the selected above, the fields are going to be enable/disabled or not relevant. I'm adding just a disabled "disk space" field to emphasise that the structure should be like in "New Disk" but areas in the form can be disabled. Regarding dotted underline to show help - made the changes. In case u need a css example: <div style="border-bottom: 2px dotted #000; display: inline;" title="I love Deep Purple">I <3 #36013f.</div>
Created attachment 937619 [details] new vm
*** Bug 1105887 has been marked as a duplicate of this bug. ***
the 39489 fixes the 7th point from the Comment 1
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
Eldan, Can you explain exactly what need to be changed in (4) "Use same font as other system font - CPU shares, CPU pinning..." To which system font you mean?
Doron - is it going into 3.6.0?
*** Bug 1282386 has been marked as a duplicate of this bug. ***
(In reply to Yaniv Kaul from comment #11) > Doron - is it going into 3.6.0? No. Target updated (and this should be evaluated if 4.0 has significant UI changes).
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
I'd argue that the order of the allocation should be different. Everyone will do something with the storage allocation - the rest is really optional (CPU - many will not touch). Y.
Doron - please triage or CLOSE-WONTFIX.
Closing old issues based on capacity. Please re-open if relevant and needed.