Ben,
I still see a problem in my tests on master with localnet ports getting
deleted unnecessarily - Here is a log of a run.. I added some logs
to try to narrow down the problem.
2016-03-08T22:10:30.768Z|1|vlog|INFO|opened log file
/home/ovs/ovs/tests/testsuite.dir/2025/hv/ovn-controller.lo
thanks !, I will make these updates in the next version
From: Justin Pettit
To: Ramu Ramamurthy
Cc: dev@openvswitch.org, Badri Ramaswamy/Santa Clara/IBM@IBMUS
Date: 02/11/2016 11:22 PM
Subject:Re: [ovs-dev] [PATCH v3] ovn-controller: Assign zone-id
consistently
Sent by:
Currently, conntrack zone-id is assigned to lport by ovn-controller,
but the ovn-controller does not record this map (lport->zoneid)
So, after ovn-controller restart, zone-ids may get set
inconsistently on lports, resulting in possible hits to
already established connections.
Currently, conntrack zone-id is assigned to lport by ovn-controller,
but the ovn-controller does not remember what was earlier assigned
to the same lport (possibly in an earlier run across restart).
So, after ovn-controller restart, the zone-ids may get set
inconsistently on lports, resulting in
Overview:
We are running openstack kilo with neutron OVS using intel 10G adapters (br
kx4 dual-port, 82599es).
neutron OVS is using vxlan tunnels. We are using RHEL 7.1 (which uses the 3.x
kernel).
Openvswitch kernel module is from upstream (3.x) and ovs is 2.3.0 based.
Problem:
We find
