yahoo-eng-team team mailing list archive

[OpenStack Infra <1402502@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/142302
Committed: https://git.openstack.org/cgit/openstack/openstack-manuals/commit/?id=ea465673461d99f44491afb7f29852acd2a637e1
Submitter: Jenkins
Branch:    master

commit ea465673461d99f44491afb7f29852acd2a637e1
Author: liyingjun <liyingjun1988@xxxxxxxxx>
Date:   Wed Dec 17 09:52:22 2014 +0800

    Suspending instance will not update resource usage
    
    As reported in the bug, "memory and vCPUs NOT become available to
    create other instances when suspending instance". So update the
    description for ' Suspend and resume an instance'.
    
    Change-Id: I4c11c73fe9ba42e77c86cefe4360ce2496e810e1
    Closes-bug: #1402502


** Changed in: openstack-manuals
       Status: In Progress => Fix Released

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

Title:
  Resource usage will not be updated when suspending instance

Status in OpenStack Compute (Nova):
  Opinion
Status in OpenStack Manuals:
  Fix Released

Bug description:
  Suspending instance will not update resource usage.

  Instance suspending should move all contents in the ram to hard disk.
  Then vcpu and used memory should be decreased and hard disk useage should be increased.
  However it didn't happen.

  This will lead to trouble in the following scenario:
  When the memory of all compute nodes are exhaust, to create a new instance, it's useless to suspend some alive instances, but have to delete them.

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