Bug 2196912
| Summary: | Missing and confusing help texts for CPU number calculations | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Container Native Virtualization (CNV) | Reporter: | Hilda Stastna <hstastna> | ||||
| Component: | User Experience | Assignee: | Hilda Stastna <hstastna> | ||||
| Status: | VERIFIED --- | QA Contact: | Guohua Ouyang <gouyang> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.13.0 | CC: | apinnick, gouyang, yfrimanm | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.14.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | Type: | Bug | |||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Hilda Stastna
2023-05-10 18:50:59 UTC
I would vote for avoiding "This resource" terminology. I think users would expect something more concrete and easy to understand, so I like the first suggestion much better ("This Template has..."... or "This VirtualMachineInstance has..."). It's also more aligned with what we have for this bug https://bugzilla.redhat.com/show_bug.cgi?id=2172390#c16
(In reply to Yifat Menchik from comment #5) > I would vote for avoiding "This resource" terminology. I think users would > expect something more concrete and easy to understand, so I like the first > suggestion much better ("This Template has..."... or "This > VirtualMachineInstance has..."). It's also more aligned with what we have > for this bug https://bugzilla.redhat.com/show_bug.cgi?id=2172390#c16 Makes sense, just it would make the code more complicated, as we use the same component for VMs, Templates, etc.. @apinnick can you please advise? Thank you. (In reply to Yifat Menchik from comment #7) > @apinnick can you please advise? Thank you. I also prefer the first option, to have the help text say "Template" or "VirtualMachineInstance" instead of "Resource". Can the component detect its context so that the correct resource name would appear? (In reply to Avital Pinnick from comment #8) > (In reply to Yifat Menchik from comment #7) > > @apinnick can you please advise? Thank you. > > I also prefer the first option, to have the help text say "Template" or > "VirtualMachineInstance" instead of "Resource". Can the component detect its > context so that the correct resource name would appear? I don't know yet. But it should be doable somehow. Hi Avital,
and what would you suggest for VirtualMachineTemplate resource help text? Which option is better?
'The VirtualMachineTemplate has {{sockets}} sockets, {{threads}} threads, and {{cores}} cores.'
or
'The Template has {{sockets}} sockets, {{threads}} threads, and {{cores}} cores.'
Thanks.
Hi Avital,
another, 3rd option for templates help text could also be:
'The template has {{sockets}} sockets, {{threads}} threads, and {{cores}} cores.'
- see the small 't' for template.
(In reply to Hilda Stastna from comment #11) > Hi Avital, > > another, 3rd option for templates help text could also be: > 'The template has {{sockets}} sockets, {{threads}} threads, and {{cores}} > cores.' > - see the small 't' for template. LGTM verified on kubevirt-console-plugin-rhel9:v4.14.0-2121 |