yahoo-eng-team team mailing list archive

[melanie witt <1686380@xxxxxxxxxxxxxxxxxx>]

In Pike, quotas were re-architected in how they count usage of instance
RAM and video RAM is no longer counted as usage, so there is no longer a
mismatch between the RAM usage allocated vs released.

** Changed in: nova
       Status: In Progress => Invalid

-- 
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/1686380

Title:
  the resize of the instance does not change the memory quota usage for
  vram

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Description
  ===========

  When creating an instance, the memory quota is used to contain video
  ram.

  For an instance resize, the difference between the old flavor and the
  new flavor will be check, and update the quota usage, but if the old
  flavor and the new flavor define a different video ram in extra_specs,
  it will cause the memory quota to be incorrect.

  If a flavor defines 512MB of RAM and 64MB of video RAM, creating an
  instance will take up 576MB of memory quota, when resize this instance
  to a flavor defined 1024MB of RAM but 0MB of video RAM, it will take
  up 1088MB of memory quota, not 1024MB, and this 64MB memory quota
  usage will never be released.

  This bug as same as https://launchpad.net/bugs/1681989 , but this for
  resize and that for delete.

  Steps to reproduce
  ==================

  1.create a flavor A,include 64MB video ram and 512MB ram.
  2.use flavor A create a instance.
  3.use "nova limits" should show used 576MB quota of ram.
  4.create a flavor B,have no video ram and 1024 ram.
  5.resize instance to B
  6.use "nova limits",it shows used 1088MB quota of ram,but it should be 1024MB.

  Environment
  ===========
  devstack(master) on Ubuntu 16.04
  devstack(newton) on CentOS 7.3

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