Re: [ovs-dev] - ovn-controller: Assign zone-ids consistently

2016-02-23 Thread Ben Pfaff
I see that now. I believe that some of my comments are still applicable. I'll re-send them for v5. On Mon, Feb 22, 2016 at 07:49:01PM -0500, Russell Bryant wrote: > Hi, Ben. I know we've had a lot of mailing list problems so you may have > missed some of the follow-up to this patch. It's up to

Re: [ovs-dev] - ovn-controller: Assign zone-ids consistently

2016-02-22 Thread Russell Bryant
Hi, Ben. I know we've had a lot of mailing list problems so you may have missed some of the follow-up to this patch. It's up to v5. I believe another revision is coming to address saving zone IDs for container-in-vm and localnet ports. http://openvswitch.org/pipermail/dev/2016-February/066179.h

Re: [ovs-dev] - ovn-controller: Assign zone-ids consistently

2016-02-22 Thread Ben Pfaff
On Mon, Feb 08, 2016 at 10:12:50PM +, Suryanarayan Ramamurthy wrote: > 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-co