[neutron][upgrades] Linuxbridge driver removal and migration
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/
I’ll “pour one out” for our friend, LinuxBridge. It served us well for many, many, years - but the future looks much brighter with OVN! Thanks for the heads up! -- James Denton Principal Architect Rackspace Private Cloud - OpenStack james.denton@rackspace.com From: Brian Haley <haleyb.dev@gmail.com> Date: Tuesday, January 14, 2025 at 1:40 PM To: openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org> Subject: [neutron][upgrades] Linuxbridge driver removal and migration CAUTION: This message originated externally, please use caution when clicking on links or opening attachments! 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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F845181&data=05%7C02%7Cjames.denton%40rackspace.com%7C6b4a0414dd644beebe7008dd34d35711%7C570057f473ef41c8bcbb08db2fc15c2b%7C0%7C0%7C638724804492149410%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=iMcDJmj2HAtgPtVXvX%2Fr3h%2BhT9ksobJGAKoblCnJI8Q%3D&reserved=0<https://review.opendev.org/c/openstack/neutron/+/845181> [1] https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F927216&data=05%7C02%7Cjames.denton%40rackspace.com%7C6b4a0414dd644beebe7008dd34d35711%7C570057f473ef41c8bcbb08db2fc15c2b%7C0%7C0%7C638724804496789930%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=enekNidXn82OGnyBFDcrqMSOxNPzbZFIzDCo22WWEUw%3D&reserved=0<https://review.opendev.org/c/openstack/neutron/+/927216> [2] https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.jimmdenton.com%2Fmigrating-lxb-to-ovn%2F&data=05%7C02%7Cjames.denton%40rackspace.com%7C6b4a0414dd644beebe7008dd34d35711%7C570057f473ef41c8bcbb08db2fc15c2b%7C0%7C0%7C638724804496808486%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=iP4PnCPlnSHC1%2FO6XHMKVgVflse1rP4jt0X%2BcCjTI7A%3D&reserved=0<https://www.jimmdenton.com/migrating-lxb-to-ovn/>
Yep, end of an era. However, this spells good news as we focus down on OVN. Out of curiosity, I couldn’t see a feature matrix for OVN support like that of cinder drivers matrix. Do we have one stashed somewhere in the documentation? Thanks, Karl. Karl Kloppenborg Chief Technology Officer m: +61 437 239 565 resetdata.com<https://resetdata.com/> [cid:reset_69557fc2-1d63-4932-b5fd-93bd4f39ca7b.png] ResetData supports Mandatory Client Related Financial Disclosures – Scope 3 Emissions Reporting For more information on the phasing of these requirements for business please visit; https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-state.pdf<https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-state.pdf> This email transmission is intended only for the addressee / person responsible for delivery of the message to such person and may contain confidential or privileged information. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you, nor may you use, review, disclose, disseminate or copy any information contained in or attached to it. Whilst this email has been checked for viruses, the sender does not warrant that any attachments are free from viruses or other defects. You assume all liability for any loss, damage or other consequences which may arise from opening or using the attachments. If you received this e-mail in error please delete it and any attachments and kindly notify us by immediately sending an email to contact@resetdata.com.au<mailto:contact@resetdata.com.au> From: James Denton <james.denton@rackspace.com> Date: Wednesday, 15 January 2025 at 7:09 am To: Brian Haley <haleyb.dev@gmail.com>, 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 james.denton@rackspace.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> I’ll “pour one out” for our friend, LinuxBridge. It served us well for many, many, years - but the future looks much brighter with OVN! Thanks for the heads up! -- James Denton Principal Architect Rackspace Private Cloud - OpenStack james.denton@rackspace.com From: Brian Haley <haleyb.dev@gmail.com> Date: Tuesday, January 14, 2025 at 1:40 PM To: openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org> Subject: [neutron][upgrades] Linuxbridge driver removal and migration CAUTION: This message originated externally, please use caution when clicking on links or opening attachments! 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<https://review.opendev.org/c/openstack/neutron/+/845181> [1] https://review.opendev.org/c/openstack/neutron/+/927216<https://review.opendev.org/c/openstack/neutron/+/927216> [2] https://www.jimmdenton.com/migrating-lxb-to-ovn/<https://www.jimmdenton.com/migrating-lxb-to-ovn/>
There's a "gaps" document here: https://docs.openstack.org/neutron/latest/ovn/gaps.html that contrasts ml2/ovn against ml2/ovs. Though it's probably not exactly a matrix but may give some idea. (Note: ml2/ovn is not just "gaps"; it also brings new features, though these are not listed on the "gaps" page, since it was not the goal of the page to put light on benefits of the driver.) On Tue, Jan 14, 2025 at 4:20 PM Karl Kloppenborg < kkloppenborg@resetdata.com.au> wrote:
Yep, end of an era.
However, this spells good news as we focus down on OVN.
Out of curiosity, I couldn’t see a feature matrix for OVN support like that of cinder drivers matrix.
Do we have one stashed somewhere in the documentation?
Thanks, Karl.
Karl Kloppenborg
Chief Technology Officer
m: *+61 437 239 565* *resetdata.com <https://resetdata.com/>*
[image: reset.png]
*ResetData supports Mandatory Client Related Financial Disclosures – Scope 3 Emissions Reporting*For more information on the phasing of these requirements for business please visit; *https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-stat... <https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-state.pdf>*
This email transmission is intended only for the addressee / person responsible for delivery of the message to such person and may contain confidential or privileged information. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you, nor may you use, review, disclose, disseminate or copy any information contained in or attached to it. Whilst this email has been checked for viruses, the sender does not warrant that any attachments are free from viruses or other defects. You assume all liability for any loss, damage or other consequences which may arise from opening or using the attachments. If you received this e-mail in error please delete it and any attachments and kindly notify us by immediately sending an email to *contact@resetdata.com.au <contact@resetdata.com.au>*
*From: *James Denton <james.denton@rackspace.com> *Date: *Wednesday, 15 January 2025 at 7:09 am *To: *Brian Haley <haleyb.dev@gmail.com>, 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 james.denton@rackspace.com. Learn why this is important <https://aka.ms/LearnAboutSenderIdentification>
I’ll “pour one out” for our friend, LinuxBridge. It served us well for many, many, years - but the future looks much brighter with OVN!
Thanks for the heads up!
--
James Denton
Principal Architect
Rackspace Private Cloud - OpenStack
james.denton@rackspace.com
*From: *Brian Haley <haleyb.dev@gmail.com> *Date: *Tuesday, January 14, 2025 at 1:40 PM *To: *openstack-discuss@lists.openstack.org < openstack-discuss@lists.openstack.org> *Subject: *[neutron][upgrades] Linuxbridge driver removal and migration
CAUTION: This message originated externally, please use caution when clicking on links or opening attachments!
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://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F845181&data=05%7C02%7Cjames.denton%40rackspace.com%7C6b4a0414dd644beebe7008dd34d35711%7C570057f473ef41c8bcbb08db2fc15c2b%7C0%7C0%7C638724804492149410%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=iMcDJmj2HAtgPtVXvX%2Fr3h%2BhT9ksobJGAKoblCnJI8Q%3D&reserved=0 <https://review.opendev.org/c/openstack/neutron/+/845181> [1] https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.opendev.org%2Fc%2Fopenstack%2Fneutron%2F%2B%2F927216&data=05%7C02%7Cjames.denton%40rackspace.com%7C6b4a0414dd644beebe7008dd34d35711%7C570057f473ef41c8bcbb08db2fc15c2b%7C0%7C0%7C638724804496789930%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=enekNidXn82OGnyBFDcrqMSOxNPzbZFIzDCo22WWEUw%3D&reserved=0 <https://review.opendev.org/c/openstack/neutron/+/927216> [2] https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.jimmdenton.com%2Fmigrating-lxb-to-ovn%2F&data=05%7C02%7Cjames.denton%40rackspace.com%7C6b4a0414dd644beebe7008dd34d35711%7C570057f473ef41c8bcbb08db2fc15c2b%7C0%7C0%7C638724804496808486%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=iP4PnCPlnSHC1%2FO6XHMKVgVflse1rP4jt0X%2BcCjTI7A%3D&reserved=0 <https://www.jimmdenton.com/migrating-lxb-to-ovn/>
participants (4)
-
Brian Haley
-
Ihar Hrachyshka
-
James Denton
-
Karl Kloppenborg