← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1525209] [NEW] Windows interface polling manager doesn't use ovsdb client monitor

 

Public bug reported:

In Linux the OVS agent uses the class InterfacePollingMinimizer that
notifies the agent when a new port is plugged or unplugged and passes
the related events (port added or deleted). For Windows it uses the
class AlwaysPoll that doesn't notify any specific event, it returns
always true. The OVS agent in Windows is forced to rescan the devices
currently in the machine to infer which were added. This is because the
current Windows implementation of the interface polling manager doesn't
use ovsdb client monitor. Fix this by using ovsdb client monitor also
for Windows and make sure that the events are passed correctly to the
OVS agent.

** Affects: neutron
     Importance: Undecided
     Assignee: Sayali Lunkad (sayalilunkad)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => Sayali Lunkad (sayalilunkad)

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

Title:
  Windows interface polling manager doesn't use ovsdb client monitor

Status in neutron:
  In Progress

Bug description:
  In Linux the OVS agent uses the class InterfacePollingMinimizer that
  notifies the agent when a new port is plugged or unplugged and passes
  the related events (port added or deleted). For Windows it uses the
  class AlwaysPoll that doesn't notify any specific event, it returns
  always true. The OVS agent in Windows is forced to rescan the devices
  currently in the machine to infer which were added. This is because
  the current Windows implementation of the interface polling manager
  doesn't use ovsdb client monitor. Fix this by using ovsdb client
  monitor also for Windows and make sure that the events are passed
  correctly to the OVS agent.

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


Follow ups