yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #82887
[Bug 1882233] [NEW] Libvirt driver always reports 'memory_mb_used' of 0
Public bug reported:
The nova-compute service periodically logs a summary of the free RAM,
disk and vCPUs as reported by the hypervisor. For example:
Hypervisor/Node resource view: name=vtpm-f31.novalocal free_ram=7960MB
free_disk=11.379043579101562GB free_vcpus=7 pci_devices=[{...}]
On a recent deployment using the libvirt driver, it's observed that the
'free_ram' value never changes despite instances being created and
destroyed. This is because the 'get_memory_mb_used' function in
'nova.virt.libvirt.host' always returns 0 unless the host platform -
reported by 'sys.platform' is either 'linux2' or 'linux3'. Since Python
3.3, the major version is not included in this return value since it was
misleading.
This is low priority because the value only appears to be used for
logging purposes and the values stored in e.g. the 'ComputeNode' object
and reported to placement are calculated based on config options and
number of instances on the node. We may wish to stop reporting this
information instead.
[1] https://stackoverflow.com/a/10429736/613428
** Affects: nova
Importance: Low
Assignee: Stephen Finucane (stephenfinucane)
Status: Confirmed
** Changed in: nova
Importance: Undecided => Low
** Changed in: nova
Status: New => Confirmed
** Changed in: nova
Assignee: (unassigned) => Stephen Finucane (stephenfinucane)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1882233
Title:
Libvirt driver always reports 'memory_mb_used' of 0
Status in OpenStack Compute (nova):
Confirmed
Bug description:
The nova-compute service periodically logs a summary of the free RAM,
disk and vCPUs as reported by the hypervisor. For example:
Hypervisor/Node resource view: name=vtpm-f31.novalocal
free_ram=7960MB free_disk=11.379043579101562GB free_vcpus=7
pci_devices=[{...}]
On a recent deployment using the libvirt driver, it's observed that
the 'free_ram' value never changes despite instances being created and
destroyed. This is because the 'get_memory_mb_used' function in
'nova.virt.libvirt.host' always returns 0 unless the host platform -
reported by 'sys.platform' is either 'linux2' or 'linux3'. Since
Python 3.3, the major version is not included in this return value
since it was misleading.
This is low priority because the value only appears to be used for
logging purposes and the values stored in e.g. the 'ComputeNode'
object and reported to placement are calculated based on config
options and number of instances on the node. We may wish to stop
reporting this information instead.
[1] https://stackoverflow.com/a/10429736/613428
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1882233/+subscriptions
Follow ups