Bug 2175990 - Improve the default instanceType dialog
Summary: Improve the default instanceType dialog
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.14.0
Assignee: Hilda Stastna
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-07 03:43 UTC by Guohua Ouyang
Modified: 2023-11-08 14:05 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 14:05:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Select instanceType (213.01 KB, image/png)
2023-03-07 03:43 UTC, Guohua Ouyang
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 1232 0 None open Bug 2175990: Improve Default InstanceType field in Edit modal 2023-03-31 20:11:54 UTC
Red Hat Issue Tracker CNV-26593 0 None None None 2023-03-07 03:45:24 UTC
Red Hat Product Errata RHSA-2023:6817 0 None None None 2023-11-08 14:05:20 UTC

Description Guohua Ouyang 2023-03-07 03:43:36 UTC
Created attachment 1948602 [details]
Select instanceType

Description of problem:
Below are the items were discussed to improve the dialog "Select instanceType" in the add volume modal:
1. remove the badge "VMCI", same for preference dialog above
2. add descriptive text to each and need to increase the dialog size to do so
3. remove "highperformance" and "server", don't know why they're in the list
4. sort the "Size" dropdown list


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Yifat Menchik 2023-03-07 14:36:04 UTC
1. "Remove the badge VMCI" - AFAIU from @fdeutsch there can be two types of badges here, so differentiation is required. TMO we can use grouping in the dropdown menu to separate the two types.

Comment 2 Hilda Stastna 2023-03-07 18:13:01 UTC
Guohua,

3. "highperformance" and "server" InstanceTypes are there because we fetch them from the server, same as the other ones. That's something we cannot influence in the UI. Maybe later there will be even more of them?...
4. not reproducible in 4.13, sorted already some time ago

Comment 3 Guohua Ouyang 2023-03-08 00:56:00 UTC
(In reply to Hilda Stastna from comment #2)
> Guohua,
> 
> 3. "highperformance" and "server" InstanceTypes are there because we fetch
> them from the server, same as the other ones. That's something we cannot
> influence in the UI. Maybe later there will be even more of them?...
yes, it's from the backend. From comment #1, it seems it have two groups, maybe one for VMCI and one for these.

> 4. not reproducible in 4.13, sorted already some time ago

Look at it again, it should not be sorted by alphabetically but by the actual size, eg: large -> xlarge -> 2xlarge

Comment 4 Hilda Stastna 2023-03-31 15:55:17 UTC
Note that the problems mentioned in the Description are no longer present in Add volume modal.
Also note that there is no any design that would support removing "VMCP" badge from Preference drop down, see:
https://docs.google.com/document/d/1HTF6_H2WDXwlVy7RnrHH28dzFlhNIa15Hhpeoyg2R0Q/edit#
This is the default behavior in our UI as the badge represents the type of the resource being displayed.
You can see it in other drop downs across whole UI.

For Default InstanceType drop down removing "VMCI" badge is appropriate,
because there is a special design for this drop down's content in the design doc added above.

However, the problems from Description of this bug are still present in "Edit volume metadata" modal,
accessible from Bootable volumes list, so we need to fix the described problems only there.

Doc for Edit volume metadata dialog:
https://docs.google.com/document/d/15Cv54978AZKeukkurvkFN1YEx_kBsm_3XcmLey_cgZY/edit#heading=h.tj7met9j9m0q

Comment 5 Guohua Ouyang 2023-04-28 03:19:46 UTC
verified on kubevirt-console-plugin-rhel9-container-v4.14.0-1047

Comment 8 errata-xmlrpc 2023-11-08 14:05:04 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Virtualization 4.14.0 Images security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:6817


Note You need to log in before you can comment on or make changes to this bug.