Bug 1613702 - [RFE][UI] - Add out-of-sync icon indication for the cluster entity
Summary: [RFE][UI] - Add out-of-sync icon indication for the cluster entity
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.2.5.1
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ovirt-4.3.6
: 4.3.6.1
Assignee: eraviv
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-08 08:02 UTC by Michael Burman
Modified: 2019-09-26 19:43 UTC (History)
4 users (show)

Fixed In Version: ovirt-engine-4.3.6.1
Clone Of:
Environment:
Last Closed: 2019-09-26 19:43:27 UTC
oVirt Team: Network
Embargoed:
pm-rhel: ovirt-4.3+
mtessun: planning_ack+
pm-rhel: devel_ack+
pm-rhel: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 101102 0 'None' MERGED engine: out of sync indication on cluster main view 2021-01-21 18:29:30 UTC
oVirt gerrit 101435 0 'None' MERGED engine: out of sync indication on cluster main view 2021-01-21 18:29:30 UTC
oVirt gerrit 101994 0 'None' MERGED engine: cluster out of sync indication restructuring 2021-01-21 18:30:11 UTC
oVirt gerrit 102435 0 'None' MERGED engine: cluster out of sync indication restructuring 2021-01-21 18:29:30 UTC

Description Michael Burman 2018-08-08 08:02:39 UTC
Description of problem:
[UI] Add out-of-sync icon indication for the cluster entity

Currently we are working on a new option to sync networks on hosts across the cluster. The only indication is a new button that will be enabled if networks are out-of-sync in the cluster.
I would like to add an icon on the cluster entity in the main Clusters tab with out-of-sync indication

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

Comment 1 eraviv 2019-06-17 06:09:30 UTC
Michael,
I need some details about how you would like this notification to be implemented


1. Notify only in cluster list per cluster line?
2. Were would you like the notification and what kind? 
- Add message to text when hovering over the '!' in the cluster line? what text?
- Add icon next to '!' or elsewhere in the line?
3. Which icon?

Thanks

Comment 2 Michael Burman 2019-06-17 06:21:58 UTC
(In reply to eraviv from comment #1)
> Michael,
> I need some details about how you would like this notification to be
> implemented
> 
> 
> 1. Notify only in cluster list per cluster line?
> 2. Were would you like the notification and what kind? 
> - Add message to text when hovering over the '!' in the cluster line? what
> text?
> - Add icon next to '!' or elsewhere in the line?
> 3. Which icon?
> 
> Thanks

Hi Eitan,

- We can add an 'out-of-sync' column header(or 'status' header for example) of it self entity with the 'out-of-sync' icon only, not '!' please. 
- There is plenty of space in Clusters main area and we can add a new column or use the empty column which i have no idea what it meant to be. It located between name and comment, an empty column that can be used to add the out-of-sync icon.
- In the bottom line, if not possible to add new column or use the empty one, i would accept having the out-of-sync icon next to the cluster's name per cluster line. 
- Please don't use the '!' icon, it useless. Please use the chain icon or the native out-of-sync icon. Using them is enough from my point of view and no text is needed. Please make sure to sync with me before applying any changes. 
Thanks,

Comment 3 Michael Burman 2019-08-11 06:47:17 UTC
Verified on - 4.3.6.1-0.1.el7

A new out-of-sync icon indication was added to the Clusters main view, in the status column. The icon is a red icon chain. Also a tootip was added to the icon, indicating which hosts are out-of-sync in the cluster.

Comment 4 Sandro Bonazzola 2019-09-26 19:43:27 UTC
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 release, it has been closed with a resolution of CURRENT RELEASE.

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


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