yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

This came up in discussion here:

https://review.openstack.org/#/c/416521/58/nova/compute/api.py@1904

There is a flavor extra spec called "hw_video:ram_max_mb" which is used
in the compute API code to count against a project's ram usage in
addition to the memory_mb in the flavor being used to create the
instance.

The hw_video:ram_max_mb flavor extra spec is only then used in the
libvirt driver, but not anywhere else.

The issue is that when doing claims in the resource tracker and
reporting allocations for the compute node resource provider to the
placement service, we don't account for the hw_video:ram_max_mb value in
addition to the flavor.memory_mb value, so we're really taking up more
MEMORY_MB inventory capacity on the compute node than what's reported to
Placement, which is a problem, probably. :)

This is a latent bug since that flavor extra spec was introduced.

** 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/1704012

Title:
  hw_video:ram_max_mb is tracked for quota but not compute node resource
  provider allocations

Status in OpenStack Compute (nova):
  New

Bug description:
  This came up in discussion here:

  https://review.openstack.org/#/c/416521/58/nova/compute/api.py@1904

  There is a flavor extra spec called "hw_video:ram_max_mb" which is
  used in the compute API code to count against a project's ram usage in
  addition to the memory_mb in the flavor being used to create the
  instance.

  The hw_video:ram_max_mb flavor extra spec is only then used in the
  libvirt driver, but not anywhere else.

  The issue is that when doing claims in the resource tracker and
  reporting allocations for the compute node resource provider to the
  placement service, we don't account for the hw_video:ram_max_mb value
  in addition to the flavor.memory_mb value, so we're really taking up
  more MEMORY_MB inventory capacity on the compute node than what's
  reported to Placement, which is a problem, probably. :)

  This is a latent bug since that flavor extra spec was introduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1704012/+subscriptions