yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #27199
[Bug 1414432] [NEW] nova hypervisor-stats shows wrong disk usage with ceph backend
Public bug reported:
While using ceph as backend , each compute node reports its disk usage
with total backend pool disk usage, this makes sense to caculate
incoming resource request like booting a new instance or migrating
instance to this compute node.
SEE
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L4334
but while get hypervisor-stats, we sum all the compute nodes's disk usage, that doesn't make sense for ceph backend.
That will show that disk usage = {actual disk usage} * {number of compuet node}
https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L648
what will handle this case ?
take average value of disk usage of each compute node instead while
using ceph ?
** Affects: nova
Importance: Undecided
Status: New
--
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/1414432
Title:
nova hypervisor-stats shows wrong disk usage with ceph backend
Status in OpenStack Compute (Nova):
New
Bug description:
While using ceph as backend , each compute node reports its disk usage
with total backend pool disk usage, this makes sense to caculate
incoming resource request like booting a new instance or migrating
instance to this compute node.
SEE
https://github.com/openstack/nova/blob/master/nova/virt/libvirt/driver.py#L4334
but while get hypervisor-stats, we sum all the compute nodes's disk usage, that doesn't make sense for ceph backend.
That will show that disk usage = {actual disk usage} * {number of compuet node}
https://github.com/openstack/nova/blob/master/nova/db/sqlalchemy/api.py#L648
what will handle this case ?
take average value of disk usage of each compute node instead while
using ceph ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1414432/+subscriptions
Follow ups
References