[ovs-dev] [PATCH v3] ovn-controller: Assign zone-id consistently

Russell Bryant russell at ovn.org
Fri Feb 12 17:49:27 UTC 2016


On 02/12/2016 12:31 PM, Russell Bryant wrote:
> On 02/11/2016 08:18 PM, Ramu Ramamurthy wrote:
>> Currently, ovn-controller does not record the
>> lport->zoneid map, and so, after ovn-controller restart,
>> zone-ids may get set inconsistently on lports, resulting
>> in possible hits to already established connections.
>>
>> Set zone-id as an external-id of the interface record,
>> and recover the zone-id from that record
>>
>> Reported-by: Russell Bryant <russell at ovn.org>
>> Reported-at: https://bugs.launchpad.net/networking-ovn/+bug/1538696
>> Signed-off-by: Ramu Ramamurthy <ramu.ramamurthy at us.ibm.com>
> 
> This looks good and seems to be working for me.  I found one very minor
> issue that I didn't notice the first time through.

and actually, take a look at Justin's feedback here just in case you
didn't receive the emails (I didn't receive them).

	http://openvswitch.org/pipermail/dev/2016-February/066119.html

	http://openvswitch.org/pipermail/dev/2016-February/066121.html

I believe they make my comment irrelevant.

-- 
Russell Bryant



More information about the dev mailing list