yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Confirmed => Expired

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

Title:
  VMwareVCDriver and VMwareESXDriver doesn't update memory, disk and cpu
  usage to account for externally allocated VMs

Status in OpenStack Compute (nova):
  Expired

Bug description:
  The ESX driver doesn't account for resources that have been allocated
  without nova-compute. When nova-compute first launches, it polls the
  esx hypervisor for available resources and initializes the
  disk/memory/vcpu usage metrics with incorrect values (assumes all
  resources are available). Which can result in over allocation errors
  when provisioning new virtual machines.

  How to reproduce:
  1. Create a virtual machine on the ESX hypervisor(using vsphere client)
  2. Launch Nova
  3. Check the "Hypervisor Summary" page on the dashboard
  4. Notice that the disk/memory/vcpu usage doesn't reflect the virtual machine's(from step 1) allocated resources

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