Bug 1122852 - [RFE][Admin Portal][Guest Agent Data] Guest Agent data from 'Network Interfaces' subtab should be moved to separate subtab
Summary: [RFE][Admin Portal][Guest Agent Data] Guest Agent data from 'Network Interfac...
Keywords:
Status: NEW
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-24 08:35 UTC by Jiri Belka
Modified: 2019-04-14 12:45 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-02 11:03:09 UTC
oVirt Team: Virt
ylavi: ovirt-future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Jiri Belka 2014-07-24 08:35:29 UTC
Description of problem:
Guest Agent data in 'Network Interfaces' subtab should be moved to separate subtab. Current visibility is odd:

1. Guest Agent data are not just data related to network interface
2. It seems there's some check done and only 'eth0' is shown because this reported interfaces has equal HW address as interface in Network Interfaces subtab list (what about other interfaces data which GA is able to report?)
3. No data are reported in Admin Portal about disks ad GA Data tab is visible in Network Interfaces subtab
4. Applications should be moved to Guest Agent Data subtab as only GA is able to report them
5. No memory stats are visible in Admin Portal

Separate GA Data subtab would be big benefit:

1. Immediate understanding all data origin from GA in the guest
2. Various data aggregated in one place
3. Specific collected data could be easy displayed/hidden as it would be in one place
4. Easier to maintain - now GA data are spread to many subtabs and it's "design" are ..., not very nice :)

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Michal Skrivanek 2015-06-02 11:03:09 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.

Comment 3 Jiri Belka 2015-06-02 11:33:13 UTC
I still think separate subtab for guest data would be nice.

Comment 4 Michal Skrivanek 2015-11-18 20:49:09 UTC
any preference or desire to change this?

Comment 5 Dan Kenigsberg 2015-12-10 11:51:34 UTC
If I correctly recall, we used to have all guest agent lumped together on the VM tab. We intentionally moved the IP address information to the relevant NIC.

The fact that we do not present guest agent information for internal bridges or bonds is indeed a failure in that old RFE.

If disk usage/total is not presented next to vDisk, we should add it as an RFE.

I believe the the guest-agent-given memUsed data is presented in the main VM tab.

I think that adding another subtab with aggregated guest agent information would be beneficial for presenting in-guest bridges, or in-guest RAID disks.


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