[ovs-dev] Always generate port status on port config change (EXT-338) in OpenFlow 1.5.
Ben Pfaff
blp at ovn.org
Wed Oct 12 15:57:51 UTC 2016
On Wed, Oct 12, 2016 at 05:52:13PM +0530, varsha agarwal wrote:
> It's my great pleasure to participate in the OpenVSwitch Community.
>
> I would like to work on "Always generate port status on port config
> change (EXT-338)" and contribute for the same.
>
> If anybody has already started and working on this do please let me
> know, to avoid duplication of work.
This was implemented in 2014.
commit 2a6f78e0fae96b07b5f328ee071652f4a525b16f
Author: Ben Pfaff <blp at nicira.com>
Date: Wed Feb 26 11:12:57 2014 -0800
ofproto: Send port status message for port-mods, right away.
Until now, when it processes OFPT_PORT_MOD message, Open vSwitch has waited
for ports to notify it that their status has changed before it sends a
port status update to controllers.
Also, Open vSwitch never sent port config updates at all for port
modifications other than OFPPC_PORT_DOWN. I guess that this is a relic
from the era when there was only one controller, since presumably the
controller already knew that it changed the port configuration. But in the
multi-controller world, it makes sense to send such port status updates,
and I couldn't quickly find anything in OF1.3 or OF1.4 that said they
shouldn't be sent.
EXT-338.
Signed-off-by: Ben Pfaff <blp at nicira.com>
Reported-by: Kmindg G <kmindg at gmail.com>
commit ebeae5db715dd4a33a6918765505b5695f938fce
Author: Jean Tourrilhes <jean.tourrilhes at hp.com>
Date: Wed Jun 18 18:05:44 2014 -0700
tests: Check that port status MODIFY messages are generated.
ONF-JIRA: EXT-338
Signed-off-by: Jean Tourrilhes <jt at hpl.hp.com>
More information about the dev
mailing list