network-verification fails with more than 500 VLANs
Bug #1397140 reported by
Łukasz Oleś
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Łukasz Oleś | ||
6.0.x |
Fix Committed
|
High
|
Łukasz Oleś | ||
6.1.x |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
When environment is configured to use neutron + vlan, user may set in "Neutron L2 settings" very big VLAN range. Even 4000 VLANs.
For such big amount of VLANs network verification will fail because of timeouts.
To fix this we need to increase timeouts in astute and in network_checker. Timeout values should be calcualated including VLANs and network interfaces number.
Places to change:
https:/
https:/
Currently 'duration' value is not sent, so protocol should be changed to include this value.
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
assignee: | Fuel Python Team (fuel-python) → Fuel Astute Team (fuel-astute) |
summary: |
- network-verification fail with more than 500 VLANs + network-verification fails with more than 500 VLANs |
tags: | added: scale |
tags: | added: module-astute |
tags: | added: release-notes |
tags: | added: on-verification |
tags: | added: wontfix-feature |
To post a comment you must log in.
Timeouts can be increased and it will probably fix problem for some time, but it is not really the solution.
Previously it worked fine with big number of vlans, like 4000. So i guess there was large number of nodes also,
and network checker failed because of large amount of traffic parsing.
We need to search for ways of decreasing amount of effective traffic or paralellizing parsing process.
One more thought that i had is to use lldp for basic network verification, but it requires design