Back to bug 2128701
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Bernard Cafarelli | 2022-09-21 12:45:06 UTC | Link ID | Red Hat Bugzilla 2100403 | |
| Red Hat One Jira (issues.redhat.com) | 2022-09-21 13:07:55 UTC | Link ID | Red Hat Issue Tracker OSP-18846 | |
| Alex Stupnikov | 2022-09-22 08:42:53 UTC | CC | astupnik | |
| Miguel Lavalle | 2022-09-26 14:03:31 UTC | Keywords | Triaged | |
| CC | mlavalle | |||
| Assignee | rhos-maint | gregraka | ||
| Miguel Lavalle | 2022-09-26 14:03:53 UTC | Priority | unspecified | high |
| Bernard Cafarelli | 2022-09-26 14:42:36 UTC | Doc Text | The ML2/OVS mechanism driver is deprecated since 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 17.1. + 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. | |
| Doc Type | If docs needed, set a value | Deprecated Functionality | ||
| Greg Rakauskas | 2022-09-26 14:44:14 UTC | Target Milestone | --- | ga |
| Doc Text | The ML2/OVS mechanism driver is deprecated since 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 17.1. + 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 since 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 17.1. + 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. | ||
| Assignee | gregraka | bcafarel | ||
| Greg Rakauskas | 2022-09-26 14:44:42 UTC | Depends On | 2100403 | |
| CC | gregraka | |||
| Bernard Cafarelli | 2022-09-26 14:45:39 UTC | Status | NEW | ASSIGNED |
| RHEL Program Management | 2022-09-26 14:45:48 UTC | Target Release | --- | 17.1 |
| Jenny-Anne Lynch | 2023-06-15 16:11:24 UTC | Doc Text | The ML2/OVS mechanism driver is deprecated since 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 17.1. + 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 since Red Hat OpenStack Platform (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 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 17.1. + 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. |
| CC | jelynch | |||
| Bernard Cafarelli | 2023-07-05 12:50:35 UTC | Resolution | --- | CURRENTRELEASE |
| Status | ASSIGNED | CLOSED | ||
| Last Closed | 2023-07-05 12:50:35 UTC | |||
| James Smith | 2023-07-05 13:45:10 UTC | CC | jamsmith | |
| Doc Text | The ML2/OVS mechanism driver is deprecated since Red Hat OpenStack Platform (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 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 17.1. + 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 since Red Hat OpenStack Platform (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 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 17.1. + 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 See link:https://access.redhat.com/solutions/2186261[How to open a proactive case for a planned activity on Red Hat OpenStack Platform?]. |
||
| Ian Frangs | 2023-08-03 15:46:23 UTC | Flags | needinfo?(bcafarel) | |
| Bernard Cafarelli | 2023-08-08 12:52:53 UTC | Flags | needinfo?(bcafarel) | |
| Andy Stillman | 2023-08-11 20:13:41 UTC | Doc Text | The ML2/OVS mechanism driver is deprecated since Red Hat OpenStack Platform (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 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 17.1. + 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 See link:https://access.redhat.com/solutions/2186261[How to open a proactive case for a planned activity on Red Hat OpenStack Platform?]. | The ML2/OVS mechanism driver is deprecated since 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 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 17.1. + 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 See link:https://access.redhat.com/solutions/2186261[How to open a proactive case for a planned activity on Red Hat OpenStack Platform?]. |
| Andy Stillman | 2023-08-14 22:13:36 UTC | Doc Text | The ML2/OVS mechanism driver is deprecated since 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 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 17.1. + 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 See link:https://access.redhat.com/solutions/2186261[How to open a proactive case for a planned activity on Red Hat OpenStack Platform?]. | The ML2/OVS mechanism driver is deprecated since 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 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 17.1. + 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?]. |
Back to bug 2128701