Public bug reported: The aim of this bug is just to document known issue when using L2 population and OVS agent. L2 population is needed, for example, when using tunnel protocol and DVR.
If the OVS agent (compute node) is overloaded (too many ports VS one single threaded OVS agent), the polling cycle takes too much time (several minutes). During the processing time, the L2 population interruptions can delay even more the polling cycle conclusion. Although it is important to attend to the L2 population requests, it is more important to finish the port bindings first. Any additional processing, like attending to the L2 population requests, should be done at the end of the OVS agent polling cycle. ** Affects: neutron Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1905271 Title: [OVS] Polling cycle continuously interrupted by L2 population (when enabled) Status in neutron: New Bug description: The aim of this bug is just to document known issue when using L2 population and OVS agent. L2 population is needed, for example, when using tunnel protocol and DVR. If the OVS agent (compute node) is overloaded (too many ports VS one single threaded OVS agent), the polling cycle takes too much time (several minutes). During the processing time, the L2 population interruptions can delay even more the polling cycle conclusion. Although it is important to attend to the L2 population requests, it is more important to finish the port bindings first. Any additional processing, like attending to the L2 population requests, should be done at the end of the OVS agent polling cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1905271/+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