← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1952567] [NEW] [ml2][ovs] ports tag are missing and flood on those

 

Public bug reported:

During some ml2 ovs agent port processing performance test, we noticed
that some ports are missing tag before it really done processing. While
ovs treats those ports without tag as trunk port, so some packets will
be flooded to it. In large scale cloud, if too many port added to the
bridge, the ovs-vswitchd will consume a huge amount of CPU cores if
ports are not bound in a short time.

Another potential problem is openflow security group may not get
processed during the first created event.

Upstream test failures of waiting too long time to ping some cases, may
be related to these problems.

** Affects: neutron
     Importance: High
     Assignee: LIU Yulong (dragon889)
         Status: In Progress

** Changed in: neutron
   Importance: Undecided => High

** Changed in: neutron
       Status: New => In Progress

** Changed in: neutron
     Assignee: (unassigned) => LIU Yulong (dragon889)

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

Title:
  [ml2][ovs] ports tag are missing and flood on those

Status in neutron:
  In Progress

Bug description:
  During some ml2 ovs agent port processing performance test, we noticed
  that some ports are missing tag before it really done processing. While
  ovs treats those ports without tag as trunk port, so some packets will
  be flooded to it. In large scale cloud, if too many port added to the
  bridge, the ovs-vswitchd will consume a huge amount of CPU cores if
  ports are not bound in a short time.

  Another potential problem is openflow security group may not get
  processed during the first created event.

  Upstream test failures of waiting too long time to ping some cases,
  may be related to these problems.

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



Follow ups