Bug 1583520
Summary: | [RFE] Improve affinity labels UI | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Roman Hodain <rhodain> |
Component: | Frontend.WebAdmin | Assignee: | Lucia Jelinkova <ljelinko> |
Status: | CLOSED DEFERRED | QA Contact: | Polina <pagranat> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.2.3.5 | CC: | ahadas, bugs, michal.skrivanek |
Target Milestone: | --- | Keywords: | FutureFeature, UserExperience |
Target Release: | --- | Flags: | pm-rhel:
ovirt-4.5?
rhodain: planning_ack? rhodain: devel_ack? rhodain: testing_ack? |
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: | 2022-04-08 16:47:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Roman Hodain
2018-05-29 07:26:53 UTC
I think the best approach here would be a Toast message with timeout saying something like "You removed the last VM/Host from an affinity label. Do you want to delete the label as well? Yes delete - No please keep it." The new 4.2 UI might even support it. I do not think deleting labels automatically would be a good approach, because we would be forcing the user to certain flows: For example to following would only support one order of actions - delete first VM from a label (implicit label delete) - add a second VM to a label - hmm? The toast flow would support this by just showing a notification the user can ignore. deprecating SLA team usage, moving to Virt (In reply to Roman Hodain from comment #0) > Description of problem: > The management of the affinity labels should be more intuitive. The > management is confusing as the affinity label can be created form the VM tab > or Host tab. But it cannot be removed. This was also reported in https://bugzilla.redhat.com/show_bug.cgi?id=1680503#c9 We think that it would be better to drop the 'remove' button from both VM's and Host's affinity label/group tabs and keep it only in the relevant cluster's tab > When removing the all the rules the > affinity label disappears, but it is not removed. It is not clear that one > has to go to Cluster tab and remove it from there. Looking at 4.4, this seems irrelevant anymore. We are past 4.5.0 feature freeze, please re-target. no updates for a long time, missed 4.5 GA, closing |