yahoo-eng-team team mailing list archive

[Chris Friesen <chris.friesen@xxxxxxxxxxxxx>]

Public bug reported:

The nova code implicitly assumes that all vCPUs are realtime in
nova.virt.hardware.vcpus_realtime_topology(), and then it appends the
user-specified mask.

This only makes sense if the user-specified cpu_realtime_mask is an
exclusion mask, but this isn't documented anywhere.

It would make more sense to simply use the mask as passed-in from the
end-user.

In order to preserve the current behaviour we should probably special-
case the scenario where the passed-in cpu_realtime_mask starts with a
"^" (indicating an exclusion).

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: compute

** Description changed:

  The nova code implicitly assumes that all vCPUs are realtime in
- nova.virt.hardware.vcpus_realtime_topology().
+ nova.virt.hardware.vcpus_realtime_topology(), and then it appends the
+ user-specified mask.
  
- This only makes sense if the cpu_realtime_mask is an exclusion mask, but
- this isn't documented anywhere.
+ This only makes sense if the user-specified cpu_realtime_mask is an
+ exclusion mask, but this isn't documented anywhere.
  
  It would make more sense to simply use the mask as passed-in from the
  end-user.
  
  In order to preserve the current behaviour we should probably special-
  case the scenario where the passed-in cpu_realtime_mask starts with a
  "^" (indicating an exclusion).

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

Title:
  cpu_realtime_mask handling is not intuitive

Status in OpenStack Compute (nova):
  New

Bug description:
  The nova code implicitly assumes that all vCPUs are realtime in
  nova.virt.hardware.vcpus_realtime_topology(), and then it appends the
  user-specified mask.

  This only makes sense if the user-specified cpu_realtime_mask is an
  exclusion mask, but this isn't documented anywhere.

  It would make more sense to simply use the mask as passed-in from the
  end-user.

  In order to preserve the current behaviour we should probably special-
  case the scenario where the passed-in cpu_realtime_mask starts with a
  "^" (indicating an exclusion).

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