[ovs-discuss] ovsdb idl seq no updates during port add.

[David Evans]

Sweet. I¡¯ll give it a try.
Thanks.

Dave.

On 4/16/15, 11:00 AM, "Ben Pfaff" <blp at nicira.com> wrote:

>On Thu, Apr 16, 2015 at 10:46:44AM -0500, David Evans wrote:
>> I get a bridge_reconfigure caused by the  if (ovsdb_idl_get_seqno(idl)
>>!=
>> idl_seqnoŠ at line 2956 of bridge.c which in turn makes the datapath id
>>to
>> be unregistered.
>> Then the bridge automatically assigns a new data path id and sends out a
>> message to it©ös open flow controller (Ryu)
>> 
>> Trouble is, later the data path id©ös for those ports added before the
>> reconfigure are now out of date so my data path id©ös for the ports will
>> now be invalid
>> This trouble cascades further if I am still in the middle of adding
>>ports
>> and flows ¡© after the unregister happens via open flow, the data path
>> cannot be located so I have to throw some exceptions..
>> And then eventually we get a new data path id registration arrive over
>> open flow.
>> 
>> How do I :
>> A) Stop the reconfigure from happening
>> Or
>> B) Get new data path id©ös for the ports previously attached so when I
>>add
>> flows via open flow commands they apply to known new data path id.
>> Or
>> C) handle the un-register / re register action gracefully via open flow
>> controller
>
>It sounds like the problem here is that OVS by default uses the smallest
>MAC address of any port on the bridge as the datapath-id.  The easy way
>to keep the datapath-id from changing would be to set your own datapath
>id using other-config:datapath-id in the Bridge table.