On 02/15/2016 08:18 PM, ramu wrote:
>
> Unfortunately, I thought of another issue that complicates this whole
> approach. A single interface does not necessarily map to a single
> logical port and zone ID. We support sub-ports, initially aimed at
> modelling containers in VMs. T
>
>
> Unfortunately, I thought of another issue that complicates this whole
> approach. A single interface does not necessarily map to a single
> logical port and zone ID. We support sub-ports, initially aimed at
> modelling containers in VMs. That means we need to track N different
> zone IDs o
On 02/15/2016 03:46 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
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 t
