When vif_type="tap" (such as when using calico),
attempting to create an instance using an image that has
the property hw_vif_multiqueue_enabled=True fails, because
the interface is always being created without multiqueue
flags.
This change checks if the property is defined and passes
the multiqueue parameter to create the tap interface
accordingly.
In case the multiqueue parameter is passed but the
vif_model is not virtio (or unspecified), the old
behavior is maintained.
Reviewed: https:/ /review. opendev. org/748533 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=84cfc8e9ab1 396ec17abcfc964 6c7d40f1d966ae
Committed: https:/
Submitter: Zuul
Branch: master
commit 84cfc8e9ab1396e c17abcfc9646c7d 40f1d966ae
Author: Rodrigo Barbieri <email address hidden>
Date: Thu Aug 27 17:20:19 2020 -0300
Allow tap interface with multiqueue
When vif_type="tap" (such as when using calico), multiqueue_ enabled= True fails, because
attempting to create an instance using an image that has
the property hw_vif_
the interface is always being created without multiqueue
flags.
This change checks if the property is defined and passes
the multiqueue parameter to create the tap interface
accordingly.
In case the multiqueue parameter is passed but the
vif_model is not virtio (or unspecified), the old
behavior is maintained.
Change-Id: I0307c43dcd0cac e1620d2ac759256 51d4ee2e96c
Closes-bug: #1893263