yahoo-eng-team team mailing list archive

[LIU Yulong <yulong@xxxxxxxxxxxxx>]

Duplicated to the bug:
https://bugs.launchpad.net/neutron/+bug/1777598
Please backport this:
https://review.openstack.org/#/c/576418/

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1785189

Title:
  Floatingip and router bandwidth speed limit failure

Status in neutron:
  Invalid

Bug description:
  Environment version: centos7.4
  Neutron version: newton

  I have added these L3 QoS patches into newton branch:
  https://review.openstack.org/#/c/453458/
  https://review.openstack.org/#/c/424466/
  https://review.openstack.org/#/c/521079/

  But I don't think these patch is useful. For large bandwidths, the
  speed limit does not work at all.As long as the router speed limit,
  floatingip speed limit, scp file has been falling from 2Mbps, and
  finally interrupted. The iperf test is extremely unstable, sometimes
  10 Mbps, sometimes 0bps.

  For example,The rate limit rule of the router is limited to 1 Gbps, router netns is iperf client,
  controller code is iperf server. Here is test result:

  [root@node-1 ~]# ip netns exec qrouter-bf800d13-9ce6-4aa7-9259-fab54ec5ac05 tc -s -p filter show dev qg-d2e58140-fa
  filter parent 1: protocol ip pref 1 u32 
  filter parent 1: protocol ip pref 1 u32 fh 800: ht divisor 1 
  filter parent 1: protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid :1  (rule hit 7557 success 7525)
    match IP src 172.18.0.133/32 (success 7525 ) 
   police 0x15a rate 1024Mbit burst 100Mb mtu 2Kb action drop overhead 0b 
  ref 1 bind 1

   Sent 12795449 bytes 8549 pkts (dropped 969, overlimits 969)

  iperf tests:
  [root@node-1 ~]# ip netns exec qrouter-bf800d13-9ce6-4aa7-9259-fab54ec5ac05 iperf3 -c 172.18.0.4 -i 1
  Connecting to host 172.18.0.4, port 5201
  [  4] local 172.18.0.133 port 51674 connected to 172.18.0.4 port 5201
  [ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
  [  4]   0.00-1.00   sec   119 KBytes   972 Kbits/sec   18   2.83 KBytes       
  [  4]   1.00-2.00   sec  0.00 Bytes  0.00 bits/sec    5   2.83 KBytes       
  [  4]   2.00-3.00   sec  0.00 Bytes  0.00 bits/sec    5   2.83 KBytes       
  [  4]   3.00-4.00   sec  0.00 Bytes  0.00 bits/sec    5   2.83 KBytes       
  [  4]   4.00-5.00   sec  0.00 Bytes  0.00 bits/sec    5   2.83 KBytes       
  [  4]   5.00-6.00   sec  63.6 KBytes   522 Kbits/sec   37   2.83 KBytes       
  [  4]   6.00-7.00   sec  1.64 MBytes  13.7 Mbits/sec  336   4.24 KBytes       
  [  4]   7.00-8.00   sec  1.34 MBytes  11.2 Mbits/sec  279   2.83 KBytes       
  [  4]   8.00-9.00   sec  1.96 MBytes  16.5 Mbits/sec  406   2.83 KBytes       
  [  4]   9.00-10.00  sec   334 KBytes  2.73 Mbits/sec   75   2.83 KBytes       
  - - - - - - - - - - - - - - - - - - - - - - - - -
  [ ID] Interval           Transfer     Bandwidth       Retr
  [  4]   0.00-10.00  sec  5.44 MBytes  4.56 Mbits/sec  1171             sender
  [  4]   0.00-10.00  sec  5.34 MBytes  4.48 Mbits/sec                  receiver

  iperf Done.

  It is normal to use the command to delete the tc rule and do the
  bandwidth test.

  [root@node-1 ~]# ip netns exec qrouter-bf800d13-9ce6-4aa7-9259-fab54ec5ac05 tc filter del dev qg-d2e58140-fa parent 1: prio 1 handle 800::800 u32
  [root@node-1 ~]# ip netns exec qrouter-bf800d13-9ce6-4aa7-9259-fab54ec5ac05 tc -s -p filter show dev qg-d2e58140-fa
  [root@node-1 ~]# ip netns exec qrouter-bf800d13-9ce6-4aa7-9259-fab54ec5ac05 iperf3 -c 172.18.0.4 -i 1
  Connecting to host 172.18.0.4, port 5201
  [  4] local 172.18.0.133 port 47530 connected to 172.18.0.4 port 5201
  [ ID] Interval           Transfer     Bandwidth       Retr  Cwnd
  [  4]   0.00-1.00   sec  88.2 MBytes   740 Mbits/sec    1    407 KBytes       
  [  4]   1.00-2.00   sec   287 MBytes  2.41 Gbits/sec  354    491 KBytes       
  [  4]   2.00-3.00   sec  1.04 GBytes  8.94 Gbits/sec  1695    932 KBytes       
  [  4]   3.00-4.00   sec  1008 MBytes  8.45 Gbits/sec  4233    475 KBytes       
  [  4]   4.00-5.00   sec  1.03 GBytes  8.85 Gbits/sec  1542    925 KBytes       
  [  4]   5.00-6.00   sec  1008 MBytes  8.45 Gbits/sec  4507    748 KBytes       
  [  4]   6.00-7.00   sec  1.05 GBytes  9.06 Gbits/sec  1550    798 KBytes       
  [  4]   7.00-8.00   sec  1.06 GBytes  9.08 Gbits/sec  1251    933 KBytes       
  [  4]   8.00-9.00   sec  1.02 GBytes  8.77 Gbits/sec  3595    942 KBytes       
  [  4]   9.00-10.00  sec  1024 MBytes  8.59 Gbits/sec  3867    897 KBytes       
  - - - - - - - - - - - - - - - - - - - - - - - - -
  [ ID] Interval           Transfer     Bandwidth       Retr
  [  4]   0.00-10.00  sec  8.54 GBytes  7.33 Gbits/sec  22595             sender
  [  4]   0.00-10.00  sec  8.54 GBytes  7.33 Gbits/sec                  receiver

  iperf Done.

  I am not sure if it is an individual phenomenon or someone else has
  encountered it.

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