yahoo-eng-team team mailing list archive

[Stephen Gordon <sgordon@xxxxxxxxxx>]

Public bug reported:

When retrieving the vCPU total via the Nova API the returned value does
not account for cpu_allocation_ratio changes. As a result external
consumers, such as Horizon and the command line client, can reflect over
utilization when a cpu_allocation_ratio > 1 is in use even when the
number of vCPUs available has not been exhausted.

For example:

If compute node has 8 cores, and overcommit is 16, that means 128 vCPUs
are available from the schedulers point of view. The API call will
however continue to return 8.

Obviously it's probably not possible to change the vCPU total behaviour
in the current field, but it would be nice for external consumers to be
able to determine (possibly via an additional field or extension) how
many vCPUs the host is actually exposing for scheduling.

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

Title:
  get_vcpu_total does not account for cpu_allocation_ratio

Status in OpenStack Compute (Nova):
  New

Bug description:
  When retrieving the vCPU total via the Nova API the returned value
  does not account for cpu_allocation_ratio changes. As a result
  external consumers, such as Horizon and the command line client, can
  reflect over utilization when a cpu_allocation_ratio > 1 is in use
  even when the number of vCPUs available has not been exhausted.

  For example:

  If compute node has 8 cores, and overcommit is 16, that means 128
  vCPUs are available from the schedulers point of view. The API call
  will however continue to return 8.

  Obviously it's probably not possible to change the vCPU total
  behaviour in the current field, but it would be nice for external
  consumers to be able to determine (possibly via an additional field or
  extension) how many vCPUs the host is actually exposing for
  scheduling.

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