ComputeNode.supported_hv_specs field has hypervisor_type
infomation about which type (e.g. KVM or both KVM and QEMU) of guests
are supported by the hypervisor, but it doesn't supply information
about which virt_type is set to that compute node.
This means that we have no way to know which type of guests are going
to be built in that compute node from the ComputeNode object. This can
cause wrong behavior in scheduler filters using the supported_hv_specs
object, such as ImagePropertiesFilter.
In libvirt driver, this patch adds a filter to exclude supported
hypervisor_types other than the virt_type which has been set by
operator via nova.conf.
Reviewed: https:/ /review. openstack. org/531347 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=eaa766ee209 3c24fd61c61e52f 46bdd9ff9e93d2
Committed: https:/
Submitter: Zuul
Branch: master
commit eaa766ee2093c24 fd61c61e52f46bd d9ff9e93d2
Author: Tetsuro Nakamura <email address hidden>
Date: Fri Jan 5 16:59:29 2018 +0900
[libvirt] Filter hypervisor_type by virt_type
ComputeNode .supported_ hv_specs field has hypervisor_type
infomation about which type (e.g. KVM or both KVM and QEMU) of guests
are supported by the hypervisor, but it doesn't supply information
about which virt_type is set to that compute node.
This means that we have no way to know which type of guests are going Filter.
to be built in that compute node from the ComputeNode object. This can
cause wrong behavior in scheduler filters using the supported_hv_specs
object, such as ImageProperties
In libvirt driver, this patch adds a filter to exclude supported types other than the virt_type which has been set by
hypervisor_
operator via nova.conf.
Partial-Bug: #1195361 cad940bea85a87c 58606314dba
Change-Id: I986fe09f97e4d5