yahoo-eng-team team mailing list archive

[Tetsuro Nakamura <nakamura.tetsuro@xxxxxxxxxxxxx>]

Public bug reported:

Description
===========

As described in [1], Hyper-V driver supports NUMA placement policies.
But it doesn't support cpu pinning policy[2].
So the host should be excluded in NUMATopologyFilter if the end user try to build a VM with cpu pinning policy.

[1] https://docs.openstack.org/nova/latest/admin/cpu-topologies.html#customizing-instance-numa-placement-policies
[2] https://docs.openstack.org/nova/latest/admin/cpu-topologies.html#customizing-instance-cpu-pinning-policies

Environment & Steps to reproduce
==================

1. Install OpenStack with Hyper-V driver (with NUMATopologyFilter set in nova.conf)
2. Try to Build a VM with "cpu_policy=dedicated".

Expected & Actual result
===============

Expected: No valid host error
Actual: <TBD: Unverified. Presumably, it would go into some unexpected error. Now this bug is reported because the bug is expected from the codes in NUMATopologyFilter and official documents>

Logs & Configs
==============

<TBD: Unverified. Presumably, it would go into some unexpected error.
Now this bug is reported because the bug is expected from the codes in
NUMATopologyFilter and official documents>

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

Title:
  NUMATopologyFilter doesn't exclude Hyper-V when cpu pinning specified.

Status in OpenStack Compute (nova):
  New

Bug description:
  Description
  ===========

  As described in [1], Hyper-V driver supports NUMA placement policies.
  But it doesn't support cpu pinning policy[2].
  So the host should be excluded in NUMATopologyFilter if the end user try to build a VM with cpu pinning policy.

  [1] https://docs.openstack.org/nova/latest/admin/cpu-topologies.html#customizing-instance-numa-placement-policies
  [2] https://docs.openstack.org/nova/latest/admin/cpu-topologies.html#customizing-instance-cpu-pinning-policies

  Environment & Steps to reproduce
  ==================

  1. Install OpenStack with Hyper-V driver (with NUMATopologyFilter set in nova.conf)
  2. Try to Build a VM with "cpu_policy=dedicated".

  Expected & Actual result
  ===============

  Expected: No valid host error
  Actual: <TBD: Unverified. Presumably, it would go into some unexpected error. Now this bug is reported because the bug is expected from the codes in NUMATopologyFilter and official documents>

  Logs & Configs
  ==============

  <TBD: Unverified. Presumably, it would go into some unexpected error.
  Now this bug is reported because the bug is expected from the codes in
  NUMATopologyFilter and official documents>

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