Public bug reported: When testing the bandwidth limit QoS tests for migration, it is needed to check where the server VM and the receiver VM are located.
Since [1][2], the QoS min and max BW rules for LSPs in LS that have associated a physical network (and a localnet port) are defined in the LSP.options dictionary. The QoS values are set in the localnet port interface using "tc" commands. If the "iperf3" is done between VMs in the same compute node, this traffic won't cross the localnet port and the QoS rules won't be applied. When the VMs are migrated, before executing the BW limit tests, it will be needed to check the current location of both VMs. This patch is similar to [3]. [1]https://review.opendev.org/c/openstack/neutron/+/934418 [2]https://github.com/ovn-org/ovn/commit/87514ac04271e87c3ad011599378d22ab6bed43c [3]https://bugs.launchpad.net/neutron/+bug/2099755 ** Affects: neutron Importance: High Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) Status: New ** Changed in: neutron Assignee: (unassigned) => Rodolfo Alonso (rodolfo-alonso-hernandez) ** Changed in: neutron Importance: Undecided => High -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/2107368 Title: [whitebox-neutron-tempest-plugin] QoS BW limit tests should check the compute of sender and receiver Status in neutron: New Bug description: When testing the bandwidth limit QoS tests for migration, it is needed to check where the server VM and the receiver VM are located. Since [1][2], the QoS min and max BW rules for LSPs in LS that have associated a physical network (and a localnet port) are defined in the LSP.options dictionary. The QoS values are set in the localnet port interface using "tc" commands. If the "iperf3" is done between VMs in the same compute node, this traffic won't cross the localnet port and the QoS rules won't be applied. When the VMs are migrated, before executing the BW limit tests, it will be needed to check the current location of both VMs. This patch is similar to [3]. [1]https://review.opendev.org/c/openstack/neutron/+/934418 [2]https://github.com/ovn-org/ovn/commit/87514ac04271e87c3ad011599378d22ab6bed43c [3]https://bugs.launchpad.net/neutron/+bug/2099755 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2107368/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
