| 2016-06-17 14:21:22 |
Ilya Shakhat |
bug |
|
|
added bug |
| 2016-06-17 14:21:30 |
Ilya Shakhat |
mos: milestone |
|
9.0 |
|
| 2016-06-17 14:21:42 |
Ilya Shakhat |
mos: assignee |
|
MOS Neutron (mos-neutron) |
|
| 2016-06-17 14:21:50 |
Ilya Shakhat |
mos: importance |
Undecided |
Critical |
|
| 2016-06-17 14:24:32 |
Alexander Ignatov |
mos: status |
New |
Confirmed |
|
| 2016-06-17 14:32:55 |
Ilya Shakhat |
description |
Shaker north-south scenario (openstack/perf_l3_north_south) measures throughput between 2 instances located in different networks plugged into different routers. The source instance has private address only, the destination is accessed via floating IP. Measured throughput is around 10s of kilobytes instead of Gbs.
Description of the environment: MOS 9, RC2, Neutron ML2, VxLAN, DVR, 6-nodes cluster.
The same can be reproduced manually with iperf3. The throughput between instance with fip and another instance with fip is good.
Steps to reproduce: run Shaker openstack/perf_l3_north_south scenario
Expected results: the throughput should be at least Gb for 1Gb interface
Actual result:
ubuntu@shaker-aompes-master-1:~$ iperf3 -c 172.20.157.25
Connecting to host 172.20.157.25, port 5201
[ 4] local 10.1.0.6 port 57555 connected to 172.20.157.25 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 54.6 KBytes 447 Kbits/sec 2 1.37 KBytes
[ 4] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 8 9.56 KBytes
[ 4] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 0 9.56 KBytes
Reproducibility: always
Workaround: n/a
Impact: barely no network connection from instance |
Shaker north-south scenario (openstack/perf_l3_north_south) measures throughput between 2 instances located in different networks plugged into different routers. The source instance has private address only, the destination is accessed via floating IP. Measured throughput is around 10s of kilobytes instead of Gbs.
Description of the environment: MOS 9, ISO 415, Neutron ML2, VxLAN, DVR, 6-nodes cluster.
The same can be reproduced manually with iperf3. The throughput between instance with fip and another instance with fip is good.
Steps to reproduce: run Shaker openstack/perf_l3_north_south scenario
Expected results: the throughput should be at least Gb for 1Gb interface
Actual result:
ubuntu@shaker-aompes-master-1:~$ iperf3 -c 172.20.157.25
Connecting to host 172.20.157.25, port 5201
[ 4] local 10.1.0.6 port 57555 connected to 172.20.157.25 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 54.6 KBytes 447 Kbits/sec 2 1.37 KBytes
[ 4] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 8 9.56 KBytes
[ 4] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 0 9.56 KBytes
Reproducibility: always
Workaround: n/a
Impact: barely no network connection from instance |
|
| 2016-06-17 15:02:34 |
Dina Belova |
tags |
|
area-neutron |
|
| 2016-06-17 15:17:33 |
Timur Nurlygayanov |
nominated for series |
|
mos/9.0.x |
|
| 2016-06-17 15:17:33 |
Timur Nurlygayanov |
bug task added |
|
mos/9.0.x |
|
| 2016-06-17 15:17:33 |
Timur Nurlygayanov |
nominated for series |
|
mos/10.0.x |
|
| 2016-06-17 15:17:33 |
Timur Nurlygayanov |
bug task added |
|
mos/10.0.x |
|
| 2016-06-17 15:17:40 |
Timur Nurlygayanov |
mos/10.0.x: status |
New |
Confirmed |
|
| 2016-06-17 15:17:42 |
Timur Nurlygayanov |
mos/10.0.x: importance |
Undecided |
Critical |
|
| 2016-06-17 15:17:49 |
Timur Nurlygayanov |
mos/10.0.x: assignee |
|
MOS Neutron (mos-neutron) |
|
| 2016-06-17 15:17:51 |
Timur Nurlygayanov |
mos/10.0.x: milestone |
|
10.0 |
|
| 2016-06-17 16:03:45 |
Ilya Shakhat |
description |
Shaker north-south scenario (openstack/perf_l3_north_south) measures throughput between 2 instances located in different networks plugged into different routers. The source instance has private address only, the destination is accessed via floating IP. Measured throughput is around 10s of kilobytes instead of Gbs.
Description of the environment: MOS 9, ISO 415, Neutron ML2, VxLAN, DVR, 6-nodes cluster.
The same can be reproduced manually with iperf3. The throughput between instance with fip and another instance with fip is good.
Steps to reproduce: run Shaker openstack/perf_l3_north_south scenario
Expected results: the throughput should be at least Gb for 1Gb interface
Actual result:
ubuntu@shaker-aompes-master-1:~$ iperf3 -c 172.20.157.25
Connecting to host 172.20.157.25, port 5201
[ 4] local 10.1.0.6 port 57555 connected to 172.20.157.25 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 54.6 KBytes 447 Kbits/sec 2 1.37 KBytes
[ 4] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 8 9.56 KBytes
[ 4] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 0 9.56 KBytes
Reproducibility: always
Workaround: n/a
Impact: barely no network connection from instance |
Shaker north-south scenario (openstack/perf_l3_north_south) measures throughput between 2 instances located in different networks plugged into different routers. The source instance has private address only, the destination is accessed via floating IP. Measured throughput is around 10s of kilobytes instead of Gbs.
Description of the environment: MOS 9, ISO 415 and ISO 481, Neutron ML2, VxLAN, DVR, 6-nodes cluster. However it was not present on ISO 401 deployed on KVM.
The same can be reproduced manually with iperf3. The throughput between instance with fip and another instance with fip is good.
Steps to reproduce: run Shaker openstack/perf_l3_north_south scenario
Expected results: the throughput should be at least Gb for 1Gb interface
Actual result:
ubuntu@shaker-aompes-master-1:~$ iperf3 -c 172.20.157.25
Connecting to host 172.20.157.25, port 5201
[ 4] local 10.1.0.6 port 57555 connected to 172.20.157.25 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 54.6 KBytes 447 Kbits/sec 2 1.37 KBytes
[ 4] 1.00-2.00 sec 0.00 Bytes 0.00 bits/sec 8 9.56 KBytes
[ 4] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 0 9.56 KBytes
Reproducibility: always
Workaround: n/a
Impact: barely no network connection from instance |
|
| 2016-06-17 18:36:02 |
Alexander Ignatov |
mos/10.0.x: status |
Confirmed |
Incomplete |
|
| 2016-06-17 18:36:06 |
Alexander Ignatov |
mos/9.0.x: status |
Confirmed |
Incomplete |
|
| 2016-06-17 18:36:14 |
Alexander Ignatov |
mos/9.0.x: milestone |
9.0 |
9.0-updates |
|
| 2016-06-17 19:02:11 |
Alexander Ignatov |
mos/9.0.x: assignee |
MOS Neutron (mos-neutron) |
Kevin Benton (kevinbenton) |
|
| 2016-06-18 08:01:57 |
Alexander Ignatov |
mos/9.0.x: importance |
Critical |
High |
|
| 2016-06-18 08:01:59 |
Alexander Ignatov |
mos/10.0.x: importance |
Critical |
High |
|
| 2016-06-22 12:24:25 |
Sergey Matov |
attachment added |
|
attachments.tar.gz https://bugs.launchpad.net/mos/+bug/1593752/+attachment/4688449/+files/attachments.tar.gz |
|
| 2016-06-22 12:56:37 |
Alexander Ignatov |
mos/9.0.x: status |
Incomplete |
Confirmed |
|
| 2016-06-22 12:56:39 |
Alexander Ignatov |
mos/10.0.x: status |
Incomplete |
Confirmed |
|
| 2016-06-22 12:56:53 |
Alexander Ignatov |
mos/9.0.x: assignee |
Kevin Benton (kevinbenton) |
MOS Neutron (mos-neutron) |
|
| 2016-06-22 14:22:27 |
Alexander Ignatov |
tags |
area-neutron |
area-neutron release-notes |
|
| 2016-07-06 13:12:43 |
Alexander Ignatov |
mos/9.x: assignee |
MOS Neutron (mos-neutron) |
Alexander Adamov (aadamov) |
|
| 2016-08-25 08:31:53 |
Alexander Adamov |
mos/9.x: status |
Confirmed |
Fix Committed |
|
| 2016-08-25 08:32:04 |
Alexander Adamov |
tags |
area-neutron release-notes |
area-neutron release-notes-done |
|
| 2016-09-02 15:08:22 |
Timur Nurlygayanov |
mos/9.x: status |
Fix Committed |
Fix Released |
|
