one other thing to not is that the curent linux bridge supprot in os-vif is only still present because linux bridge is still intree in neutron. we had planned ot delete https://github.com/openstack/os-vif/tree/master/vif_plug_linux_bridge if neutron ever removed it so if we were to move the neutron part out of tree we probably should do the same with that. which may require some nova changes too On 17/01/2025 14:22, Jeremy Stanley wrote:
On 2025-01-17 09:06:24 +0100 (+0100), Sławek Kapłoński wrote: [...]
create new project like x/networking-linuxbridge [...] For the projects in the x/ namespace [...]
Well, into some new dedicated namespace anyway. Don't use x/ for anything new, that was the dumping ground for projects whose maintainers never responded to let us know what new namespace they wanted to use.
not in all cases. for some of the stackforage project there was not alternative namespace at the time that made sense i.e. they could not move to openstack as they were not an offial delviery of any openstack project team. so they stayed in x becasue it did nto make sense to make one off namespace for things liek devstack plugins that only existed for devoplment/testing that why https://opendev.org/x/networking-ovs-dpdk and https://opendev.org/x/devstack-plugin-libvirt-qemu are in the x namespace. they were not allowed ot move to the openstack one.
When creating the project, decide on a namespace to group its repositories together in.