[ovs-dev] [PATCH branch-2.13 0/2] Release patches for v2.13.1.

William Tu u9012063 at gmail.com
Tue Aug 4 15:31:10 UTC 2020


On Tue, Aug 4, 2020 at 7:24 AM Ilya Maximets <i.maximets at ovn.org> wrote:
>
> On 8/4/20 3:19 PM, William Tu wrote:
> > On Mon, Aug 3, 2020 at 2:23 PM Ilya Maximets <i.maximets at ovn.org> wrote:
> >>
> >> On 7/30/20 12:44 AM, Ilya Maximets wrote:
> >>>
> >>> Ilya Maximets (2):
> >>>   Set release date for 2.13.1.
> >>>   Prepare for 2.13.2.
> >>>
> >>>  NEWS             | 14 +++++++++-----
> >>>  configure.ac     |  2 +-
> >>>  debian/changelog |  8 +++++++-
> >>>  3 files changed, 17 insertions(+), 7 deletions(-)
> >>>
> >>
> >> Kind reminder.
> >>
> >> These patches and patches for older branches still needs review.
> >> If anyone has a spare time slot, please take a look.
> >>
> > Thanks for working on this, this is a lot of work!
> >
> > I've reviewed all and acked.
>
> Thanks!
>
> > We also need to create a tarball for each release and update website.
> > https://www.openvswitch.org/download/
> > I can help if you haven't done it yet.
>
> I'm going to apply and backport following small patch first:
> https://patchwork.ozlabs.org/project/openvswitch/patch/20200804015456.4047-1-hepeng.0320@bytedance.com/
>
> Right after that I'll push release patches and tags.
> I also have a script to generate tarballs, so I'll prepare them and the
> website pull request once releases tagged.
>
> Maybe we need to return to the question about just having a link to
> tarballs generated by github at some point?

Yes, I think that would be easier.

>
> >
> >> I have run unit and system tests on all release branches (that wasn't
> >> simple, but more on this later).  2.13.1 also passed through ovn-k8s
> >> and OpenStack CI systems.
> >>
> >
> > Yes, I believe there are lots of issues when running system tests.
> > It would be great to have some public CI running system tests.
> > Previously I was using Github Actions, I'm curious about how you do it.
>
> For now, I just prepared a small script and a VM image to build and test.
> And actually system tests are not that bad, at least kernel ones.  Some
> tests are not skipped while should be on older branches, but it's not
> a big deal.  For now, I had to look at all the failures manually.
> Userspace testsuite is not that good.  Basically, we cleaned it up
> somewhere between 2.10-2.12.  So, on older branches it's a mess.
>
> Harder case is that older branches requires python2 to build and also
> requires /usr/bin/python to point to python2.  This is an issue if you're
> trying to build OVS on some modern distros that doesn't have python2, or
> have it but uses python3 by default or doesn't have simple 'python'
> symlink at all.  I had to switch from fedora to rhel just to build.
> The second build issue is that some older branches doesn't build with
> openssl >= 1.1.0.  This is tricky.  We will need to decide what to do
> with that later.  I will send a follow-up email about older branches
> and what options we have.
>
Thanks for sharing the experience.
William


More information about the dev mailing list