[ovs-dev] [PATCH v3 ovn 0/3] ovn: Fix port-up notification for child ports and handle upgrades.

Numan Siddique numans at ovn.org
Thu Feb 4 14:22:10 UTC 2021


On Thu, Feb 4, 2021 at 7:37 PM Dumitru Ceara <dceara at redhat.com> wrote:
>
> On 2/4/21 2:59 PM, Numan Siddique wrote:
> > On Thu, Feb 4, 2021 at 1:06 AM Dumitru Ceara <dceara at redhat.com> wrote:
> >>
> >> First two patches of the series fix issues related to:
> >> - setting Port_Binding.up for container/virtual ports/
> >> - correctly dealing with upgrades when ovn-controller is upgraded first
> >>    (recommended way).
> >>
> >> The third patch of the series tries to handle out of order upgrades
> >> (ovn-northd before ovn-controller) in order to not avoid declaring
> >> logical switch ports down during the upgrade.
> >
> > Thanks Dumitru for addressing these.
> >
> > I applied the patch series to master.
>
> Thanks Numan!
>
> >
> > Regarding the container ports, I think there is a small scope for improvement
> > as a future patch. With these patches, we set the container port to up even
> > before the ovs flows for them are not installed. I think we install a
> > flow in table 0,
> > table 65 and perhaps  in a few other tables for container ports.
>
> I couldn't find a way to properly implement this because there's no way
> in binding.c to efficiently lookup by interface id a local binding that
> corresponds to a container port because those are stored as "children"
> of regular VIFs.
>
> I'll keep it in mind and send a follow up if I can come up with a solution.

Sure.

Thanks
Numan

>
> >
> > Thanks
> > Numan
> >
>
> Thanks,
> Dumitru
>
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>


More information about the dev mailing list