Back to bug 2128697
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Bernard Cafarelli | 2022-09-21 12:41:15 UTC | Link ID | Red Hat Bugzilla 2100403 | |
| Bernard Cafarelli | 2022-09-21 12:42:56 UTC | Doc Text | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. Support will be available for the deprecated ML2/OVS mechanism driver through the RHOSP 17.0 and 17.1 releases. During this time, ML2/OVS driver is in maintenance mode, getting bugfixes and normal support, and most new feature development will only happen in the ML2/OVN mechanism driver. In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. | |
| Doc Type | If docs needed, set a value | Deprecated Functionality | ||
| Bernard Cafarelli | 2022-09-21 12:44:33 UTC | Blocks | 2128701 | |
| Bernard Cafarelli | 2022-09-21 12:46:29 UTC | CC | jamsmith | |
| Bernard Cafarelli | 2022-09-21 12:47:26 UTC | Priority | unspecified | high |
| Status | NEW | ASSIGNED | ||
| Assignee | rhos-maint | bcafarel | ||
| Keywords | Triaged | |||
| Red Hat One Jira (issues.redhat.com) | 2022-09-21 13:06:49 UTC | Link ID | Red Hat Issue Tracker OSP-18845 | |
| James Smith | 2022-09-21 14:33:13 UTC | Doc Text | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. Support will be available for the deprecated ML2/OVS mechanism driver through the RHOSP 17.0 and 17.1 releases. During this time, ML2/OVS driver is in maintenance mode, getting bugfixes and normal support, and most new feature development will only happen in the ML2/OVN mechanism driver. In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. + Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. + Support will be available for the deprecated ML2/OVS mechanism driver through the RHOSP 17.0 and 17.1 releases. During this time, ML2/OVS driver remains in maintenance mode, getting bugfixes and normal support, and most new feature development will only happen in the ML2/OVN mechanism driver. + In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. |
| CC | gurpsing, mbracho, pgrist | |||
| Flags | needinfo?(mbracho) needinfo?(gurpsing) needinfo?(pgrist) | |||
| Paul Grist | 2022-09-21 16:45:26 UTC | Flags | needinfo?(pgrist) | needinfo?(dalvarez) |
| CC | dalvarez | |||
| James Smith | 2022-09-21 18:22:25 UTC | Doc Text | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. + Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. + Support will be available for the deprecated ML2/OVS mechanism driver through the RHOSP 17.0 and 17.1 releases. During this time, ML2/OVS driver remains in maintenance mode, getting bugfixes and normal support, and most new feature development will only happen in the ML2/OVN mechanism driver. + In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. + Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. For instance, starting with RHOSP 15, ML2/OVN became the default mechanism driver. + Support will be available for the deprecated ML2/OVS mechanism driver through the RHOSP 17 releases. During this time, ML2/OVS driver remains in maintenance mode, getting bugfixes and normal support, and most new feature development will only happen in the ML2/OVN mechanism driver. + In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. + If your existing Red Hat OpenStack Platform (RHOSP) deployment uses the ML2/OVS mechanism driver, start now to evaluate a plan to migrate to the mechanism driver. Migration is supported in RHOSP 16.2 and will be supported in RHOSP 17.1. Migration tools are available in RHOSP 17.0 for test purposes only. + Red Hat requires that you file a proactive support case before attempting a migration from ML2/OVS to ML2/OVN. Red Hat does not support migrations without the proactive support case. See How to submit a Proactive Case. |
| Alex Stupnikov | 2022-09-22 08:42:07 UTC | CC | astupnik | |
| James Smith | 2022-09-22 19:20:32 UTC | Doc Text | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. + Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. For instance, starting with RHOSP 15, ML2/OVN became the default mechanism driver. + Support will be available for the deprecated ML2/OVS mechanism driver through the RHOSP 17 releases. During this time, ML2/OVS driver remains in maintenance mode, getting bugfixes and normal support, and most new feature development will only happen in the ML2/OVN mechanism driver. + In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. + If your existing Red Hat OpenStack Platform (RHOSP) deployment uses the ML2/OVS mechanism driver, start now to evaluate a plan to migrate to the mechanism driver. Migration is supported in RHOSP 16.2 and will be supported in RHOSP 17.1. Migration tools are available in RHOSP 17.0 for test purposes only. + Red Hat requires that you file a proactive support case before attempting a migration from ML2/OVS to ML2/OVN. Red Hat does not support migrations without the proactive support case. See How to submit a Proactive Case. | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. + Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. For instance, starting with RHOSP 15, ML2/OVN became the default mechanism driver. + Support is available for the deprecated ML2/OVS mechanism driver through the RHOSP 17 releases. During this time, ML2/OVS driver remains in maintenance mode, receiving bugfixes and normal support, and most new feature development happens in the ML2/OVN mechanism driver. + In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. + If your existing Red Hat OpenStack Platform (RHOSP) deployment uses the ML2/OVS mechanism driver, start now to evaluate a plan to migrate to the mechanism driver. Migration is supported in RHOSP 16.2 and will be supported in RHOSP 17.1. Migration tools are available in RHOSP 17.0 for test purposes only. + Red Hat requires that you file a proactive support case before attempting a migration from ML2/OVS to ML2/OVN. Red Hat does not support migrations without the proactive support case. See How to submit a Proactive Case. |
| James Smith | 2022-09-22 19:21:18 UTC | Doc Text | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. + Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. For instance, starting with RHOSP 15, ML2/OVN became the default mechanism driver. + Support is available for the deprecated ML2/OVS mechanism driver through the RHOSP 17 releases. During this time, ML2/OVS driver remains in maintenance mode, receiving bugfixes and normal support, and most new feature development happens in the ML2/OVN mechanism driver. + In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. + If your existing Red Hat OpenStack Platform (RHOSP) deployment uses the ML2/OVS mechanism driver, start now to evaluate a plan to migrate to the mechanism driver. Migration is supported in RHOSP 16.2 and will be supported in RHOSP 17.1. Migration tools are available in RHOSP 17.0 for test purposes only. + Red Hat requires that you file a proactive support case before attempting a migration from ML2/OVS to ML2/OVN. Red Hat does not support migrations without the proactive support case. See How to submit a Proactive Case. | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. + Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. For instance, starting with RHOSP 15, ML2/OVN became the default mechanism driver. + Support is available for the deprecated ML2/OVS mechanism driver through the RHOSP 17 releases. During this time, the ML2/OVS driver remains in maintenance mode, receiving bug fixes and normal support, and most new feature development happens in the ML2/OVN mechanism driver. + In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. + If your existing Red Hat OpenStack Platform (RHOSP) deployment uses the ML2/OVS mechanism driver, start now to evaluate a plan to migrate to the mechanism driver. Migration is supported in RHOSP 16.2 and will be supported in RHOSP 17.1. Migration tools are available in RHOSP 17.0 for test purposes only. + Red Hat requires that you file a proactive support case before attempting a migration from ML2/OVS to ML2/OVN. Red Hat does not support migrations without the proactive support case. See How to submit a Proactive Case. |
| Gurpreet Singh | 2022-09-22 20:41:09 UTC | Flags | needinfo?(gurpsing) | needinfo- |
| Greg Rakauskas | 2022-09-26 14:45:22 UTC | Depends On | 2100403 | |
| Greg Rakauskas | 2022-09-26 14:45:48 UTC | Target Milestone | --- | ga |
| Target Release | --- | 17.0 | ||
| CC | gregraka | |||
| Greg Rakauskas | 2023-04-13 22:16:04 UTC | Doc Text | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. + Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. For instance, starting with RHOSP 15, ML2/OVN became the default mechanism driver. + Support is available for the deprecated ML2/OVS mechanism driver through the RHOSP 17 releases. During this time, the ML2/OVS driver remains in maintenance mode, receiving bug fixes and normal support, and most new feature development happens in the ML2/OVN mechanism driver. + In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. + If your existing Red Hat OpenStack Platform (RHOSP) deployment uses the ML2/OVS mechanism driver, start now to evaluate a plan to migrate to the mechanism driver. Migration is supported in RHOSP 16.2 and will be supported in RHOSP 17.1. Migration tools are available in RHOSP 17.0 for test purposes only. + Red Hat requires that you file a proactive support case before attempting a migration from ML2/OVS to ML2/OVN. Red Hat does not support migrations without the proactive support case. See How to submit a Proactive Case. | The ML2/OVS mechanism driver is deprecated in RHOSP 17.0. + Over several releases, Red Hat is replacing ML2/OVS with ML2/OVN. For instance, starting with RHOSP 15, ML2/OVN became the default mechanism driver. + Support is available for the deprecated ML2/OVS mechanism driver through the RHOSP 17 releases. During this time, the ML2/OVS driver remains in maintenance mode, receiving bug fixes and normal support, and most new feature development happens in the ML2/OVN mechanism driver. + In RHOSP 18.0, Red Hat plans to completely remove the ML2/OVS mechanism driver and stop supporting it. + If your existing Red Hat OpenStack Platform (RHOSP) deployment uses the ML2/OVS mechanism driver, start now to evaluate a plan to migrate to the mechanism driver. Migration is supported in RHOSP 16.2 and will be supported in RHOSP 17.1. Migration tools are available in RHOSP 17.0 for test purposes only. + Red Hat requires that you file a proactive support case before attempting a migration from ML2/OVS to ML2/OVN. Red Hat does not support migrations without the proactive support case. See link:https://access.redhat.com/solutions/2186261[How to open a proactive case for a planned activity on Red Hat OpenStack Platform?]. |
| Red Hat Bugzilla | 2023-08-16 08:27:42 UTC | CC | mbracho |
Back to bug 2128697