Hi,
Dnia czwartek, 16 stycznia 2025 22:26:35 czas środkowoeuropejski standardowy Nick Jones pisze:
> Thanks Mohammed. I'm super out of the loop on governance, structure etc.
> so what would that look like in practice - would that give us a plugin that
> could be referenced, and it'd be maintained with its own set of tests etc.,
> presumably copied over / out from the existing Neutron codebase?
There is a guide how you can create new project https://docs.opendev.org/opendev/infra-manual/latest/creators.html. Basically, as Mohammed said, you (or someone else interested in it) would need to create new project like x/networking-linuxbridge and copy all existing linuxbridge related code to that new repo. Such project will still be using opendev infrastructure so you can run e.g. some of the neutron jobs in the project's CI, etc.
For the projects in the x/ namespace you can do your releases whenever you need/want to. Such projects are not under the OpenStack Release Team government.
>
> --
>
> -Nick
>
>
> On 16 Jan 2025 at 21:08:48, Mohammed Naser <mnaser@vexxhost.com> wrote:
>
> > I think the best way to go about this would be if someone cares enough to
> > maintain it for them to create networking-linuxbridge in the same way that
> > networking-ovn existed before and they can continue to maintain it there
> > (possibly under the x namespace).
> >
> > This will remove the burden of continuing to maintain it and those who
> > want to continue to run and maintain it can do it there.
> >
> > ------------------------------
> > *From:* Nick Jones <nick@dischord.org>
> > *Sent:* January 16, 2025 4:04 PM
> > *To:* Brian Haley <haleyb.dev@gmail.com>
> > *Cc:* openstack-discuss@lists.openstack.org <
> > openstack-discuss@lists.openstack.org>
> > *Subject:* Re: [neutron][upgrades] Linuxbridge driver removal and
> > migration
> >
> > You don't often get email from nick@dischord.org. Learn why this is
> > important <https://aka.ms/LearnAboutSenderIdentification>
> > Playing devil's advocate slightly, and as an operator who has had one eye
> > on migration (with no good answers really since it's quite a jump -
> > although I appreciate the efforts that have gone in to showing that it can
> > be done in principal), what would be entailed to reinstate the LinuxBridge
> > driver? It's been rock solid in my case, and its simplicity is really
> > appreciated.
> >
> > --
> >
> > -Nick
> >
> >
> > On 14 Jan 2025 at 19:40:26, Brian Haley <haleyb.dev@gmail.com> wrote:
> >
> > Hi Stackers,
> >
> > In 2022, during the Zed cycle, the Neutron team took a step at marking
> > some items as experimental. One of those was the Linuxbridge driver. The
> > reason was due to it being unmaintained for a number of cycles, and no
> > one was able to take on its ownership. The implication of this decision
> > was that it was consider deprecated, even if not given an official
> > warning message.
> >
> > In doing this, all gate jobs were moved into the experimental queue,
> > feature-parity with other drivers was deemed unnecessary, and bug fixing
> > was considered best-effort. Since then, both major distros have stopped
> > supporting new deployments using Linuxbridge, and have been mainly
> > focused on OVN.
> >
> > So what does this mean? We (the neutron cores) have come to the
> > conclusion that it is time to take the next step and remove the code
> > from the tree [1]. After 5 cycles of being considered experimental
> > without any investment it just makes sense. We plan on doing this in the
> > current Epoxy cycle.
> >
> > We realize that there are still deployments using Linuxbridge, and
> > hopefully they have been looking at migration strategies since we
> > originally marked the code experimental. This email is another push to
> > the user community to start looking at this, especially if you are
> > planning any new deployments. There has been at least one migration
> > guide written at [2] (thanks Jim!), and at this point I would encourage
> > those still using Linuxbridge to look at it and start asking any
> > questions they have so we have the chance to make it better and can make
> > that process easier.
> >
> > Thanks for reading,
> >
> > -Brian, Neutron PTL
> >
> > [0] https://review.opendev.org/c/openstack/neutron/+/845181
> > [1] https://review.opendev.org/c/openstack/neutron/+/927216
> > [2] https://www.jimmdenton.com/migrating-lxb-to-ovn/
> >
> >
>
--
Slawek Kaplonski
Principal Software Engineer
Red Hat