yahoo-eng-team team mailing list archive

[OpenStack Infra <1462957@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/516635
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=0124d57275a17544f796edb244a9406487efa29d
Submitter: Zuul
Branch:    master

commit 0124d57275a17544f796edb244a9406487efa29d
Author: Radoslav Gerganov <rgerganov@xxxxxxxxxx>
Date:   Tue Oct 31 11:22:46 2017 +0200

    VMware: expose max vCPUs and max memory per ESX host
    
    Expose maximum vCPUs and maximum memory from single ESX host in the
    vCenter cluster. This will be used for implementing get_inventory() in
    the follow up patch.
    
    Partial-Bug: #1462957
    
    Change-Id: I28e19d46a737ac253718c7c66837bd71b064b0b9


** Changed in: nova
       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/1462957

Title:
  VMware driver cannot report non-contiguous resources to the scheduler

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  A VMware hypervisor can have various types of non-contiguous resource.
  This includes:

  * CPUs and memory, assuming a cluster has more than 1 member.
  * Storage space, if a (VMware) host has more than 1 datastore.

  Focussing on the latter, if a host has 5 datastores, each with 50GB of
  free space, we currently report the largest contiguous free space to
  the hypervisor: 50GB. This means that the scheduler knows it can
  allocate an instance with a 50GB block device, but until the host
  stats are updated it will not allow subsequent instances to be
  scheduled there. We could alternatively report 250GB of free space,
  but would risk the scheduler repeatedly sending us a request for an
  instance with a 100GB block device, which we cannot fulfil. Without
  the ability to represent non-contiguous resources we are left choosing
  between 2 suboptimal choices.

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