On Fri, Jan 19, 2024 at 6:13 AM Dumitru Ceara wrote:
>
> On 1/11/24 16:32, num...@ovn.org wrote:
> > From: Numan Siddique
> >
> > Since northd tracked data has the changed lb data, northd
> > engine handler for lflow engine now handles the lb changes
> > incrementally. All the lflows generated
On Thu, Jan 25, 2024 at 1:25 AM Han Zhou wrote:
>
> On Thu, Jan 11, 2024 at 7:33 AM wrote:
> >
> > From: Numan Siddique
> >
> > Since northd tracked data has the changed lb data, northd
> > engine handler for lflow engine now handles the lb changes
> > incrementally. All the lflows generated
On Thu, Jan 11, 2024 at 7:33 AM wrote:
>
> From: Numan Siddique
>
> Since northd tracked data has the changed lb data, northd
> engine handler for lflow engine now handles the lb changes
> incrementally. All the lflows generated for each lb is
> stored in the ovn_lb_datapaths->lflow_ref and
On 1/11/24 16:32, num...@ovn.org wrote:
> From: Numan Siddique
>
> Since northd tracked data has the changed lb data, northd
> engine handler for lflow engine now handles the lb changes
> incrementally. All the lflows generated for each lb is
The first sentence is a bit confusing. What about
From: Numan Siddique
Since northd tracked data has the changed lb data, northd
engine handler for lflow engine now handles the lb changes
incrementally. All the lflows generated for each lb is
stored in the ovn_lb_datapaths->lflow_ref and this is used
similar to how we handle ovn_port changes.
