| 2019-09-13 07:52:22 |
Lucian Petrut |
description |
The ovsdb monitor used by Neutron ignores modified ports. For this reason, port changes will not be handled.
One particular case comes from ofport changes. On Windows, depending on the OVS version, the ofport can change after VM reboots. The neutron ovs agent will have to update the flows in this situation, which it does, but only when "minimize_polling" is disabled.
The neutron ovsdb monitor should propagate the events received for modified ports. Those can either be part of the "added" device list or have a separate one for modified ports. |
The ovsdb monitor used by Neutron ignores modified ports. For this reason, some port changes will not be handled.
One particular case comes from ofport changes. On Windows, depending on the OVS version, the ofport can change after VM reboots. The neutron ovs agent will have to update the flows in this situation, which it does, but only when "minimize_polling" is disabled.
The neutron ovsdb monitor should propagate the events received for modified ports. Those can either be part of the "added" device list or have a separate one for modified ports. |
|
