yahoo-eng-team team mailing list archive

[Arkady Shtempler <1778715@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

### Prerequisites ###
1) VM server is up and running on Nova node
2) Port 80 is added to security groups
3) HTTPD on VM is up and running
4) “Big File” (~100MB) is located in “/var/log/html”
For more details see: https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/wiki/Neutron/QoS


### Scenario ###
1) Create QoS policy with:
openstack network qos policy create bw-limiter

2) Create a rule for your QoS policy with:
openstack network qos rule create --type bandwidth-limit --max-kbps 3000 --max-burst-kbits 2400 --egress bw-limiter

3) Set QoS to floating Ip of your host using:
openstack port set --qos-policy bw-limiter vm1_port

4) Make sure that you see QoS is set to your “Floating IP” using 
openstack floating ip show <Floating_IP>
“qos_policy_id ” should be valid ID and not None

5) Initiate HTTP traffic using WGET tool from your undercloud host to VM with:
wget http://<Floating_IP>/big.txt


### Actual Result ###
In spite of the fact that configuration is done and QoS is set to “Floating IP”, actually traffic is not limited to ~3000kbps as expected.

--2018-06-26 06:10:02--  http://10.0.0.220/big.txt
Connecting to 10.0.0.220:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857801 (100M) [text/plain]
Saving to: ‘big.txt.16’

100%[========================================================>]
104,857,801  185MB/s   in 0.5s

2018-06-26 06:10:03 (185 MB/s) - ‘big.txt.16’ saved
[104857801/104857801]

Actual BW is 185MB/s instead of expected ~3000kbps

Note:
Neutron controller logs attached.

** Affects: neutron
     Importance: Undecided
         Status: Invalid


** Tags: qos

** Attachment added: "neutron.tar.gz"
   https://bugs.launchpad.net/bugs/1778715/+attachment/5156768/+files/neutron.tar.gz

** Tags added: qos

** 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/1778715

Title:
  QoS is set to Floating IP – but actually, on network level, BW
  limitation is not activated

Status in neutron:
  Invalid

Bug description:
  ### Prerequisites ###
  1) VM server is up and running on Nova node
  2) Port 80 is added to security groups
  3) HTTPD on VM is up and running
  4) “Big File” (~100MB) is located in “/var/log/html”
  For more details see: https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/wiki/Neutron/QoS


  ### Scenario ###
  1) Create QoS policy with:
  openstack network qos policy create bw-limiter

  2) Create a rule for your QoS policy with:
  openstack network qos rule create --type bandwidth-limit --max-kbps 3000 --max-burst-kbits 2400 --egress bw-limiter

  3) Set QoS to floating Ip of your host using:
  openstack port set --qos-policy bw-limiter vm1_port

  4) Make sure that you see QoS is set to your “Floating IP” using 
  openstack floating ip show <Floating_IP>
  “qos_policy_id ” should be valid ID and not None

  5) Initiate HTTP traffic using WGET tool from your undercloud host to VM with:
  wget http://<Floating_IP>/big.txt

  
  ### Actual Result ###
  In spite of the fact that configuration is done and QoS is set to “Floating IP”, actually traffic is not limited to ~3000kbps as expected.

  --2018-06-26 06:10:02--  http://10.0.0.220/big.txt
  Connecting to 10.0.0.220:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 104857801 (100M) [text/plain]
  Saving to: ‘big.txt.16’

  100%[========================================================>]
  104,857,801  185MB/s   in 0.5s

  2018-06-26 06:10:03 (185 MB/s) - ‘big.txt.16’ saved
  [104857801/104857801]

  Actual BW is 185MB/s instead of expected ~3000kbps

  Note:
  Neutron controller logs attached.

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