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

[Tetsuro Nakamura]

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>

[Sylvain Bauza (sylvain-bauza)]

Looks like more a feature (at least an enhancement) about discussing how the filter should accept any compute node for the specific CPU pinning policy.

FWIW, I'd love to see what is the actual result before setting that bug report as a Wishlist.

[Tetsuro Nakamura (tetsuro0907)]

@sbauza
Thanks. Anyway,this is expected to be fixed in https://review.openstack.org/#/c/531049/

[Launchpad Janitor (janitor)]

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]