The metrics shown under Hypervisor overview are shown incorrect

Bug #1691039 reported by sreeteja
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nova-dpm
New
Medium
Unassigned

Bug Description

This regarding the openstack hypervisor show <HOST NAME>
so this is expected to display the host metrics like memory used and maximum memory limit..
but it is not doing so here
https://github.com/openstack/nova-dpm/blob/cb0074b90e432ffcb3c971576cfda65d84d855dc/nova_dpm/virt/dpm/host.py#L53
it is just taking this as max_memory and not checking if this is been less than memory_used
https://github.com/openstack/nova-dpm/blob/cb0074b90e432ffcb3c971576cfda65d84d855dc/nova_dpm/virt/dpm/host.py#L113
so it is showing something like 2.5GB used out of 2GB
MAy be I think we should add some lines which chcks these condition and then display the hypervisor stats

sreeteja (sreeteja)
summary: - The metrics shown under Hypervisor overview are shown incorrectly
+ The metrics shown under Hypervisor overview are shown incorrect
Revision history for this message
Andreas Scheuring (andreas-scheuring) wrote :

The question is: where does the 2.5 gig come from?

- memory rounding?
- some magic calculation?

2.5G = ?
2GB = max_memory?

Revision history for this message
sreeteja (sreeteja) wrote :

It is from local.conf
max_memory = 4000

In my current system this is the value and I see the same thing in hypervisor statics.
Earlier I think it was 3000 it is in mb

sreeteja (sreeteja)
Changed in nova-dpm:
importance: Undecided → Medium
sreeteja (sreeteja)
Changed in nova-dpm:
importance: Medium → Wishlist
importance: Wishlist → Medium
sreeteja (sreeteja)
description: updated
Revision history for this message
sreeteja (sreeteja) wrote :
Revision history for this message
sreeteja (sreeteja) wrote :
Revision history for this message
sreeteja (sreeteja) wrote :
Revision history for this message
Andreas Scheuring (andreas-scheuring) wrote :

Wasn't the issue here that there was this reserved_host_memory_mb variable set to some value?

Revision history for this message
sreeteja (sreeteja) wrote :

May be you are right at this time of bug the reserved_host_memory_mb parameter change that is been added to over conf file has not been taken...

Apart from that as I mentioned in last comments the screenshots may be those can be resolved once the other bug gets fixed

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.