Bug 1640210 - TripleO - Switch the default network backend to ML2/OVN
Summary: TripleO - Switch the default network backend to ML2/OVN
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 15.0 (Stein)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Upstream M2
: 15.0 (Stein)
Assignee: Daniel Alvarez Sanchez
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks: 1752587 1769187
TreeView+ depends on / blocked
 
Reported: 2018-10-17 14:36 UTC by Daniel Alvarez Sanchez
Modified: 2019-11-06 05:17 UTC (History)
8 users (show)

Fixed In Version: openstack-tripleo-heat-templates-10.3.1-0.20190318140159.cbe8724.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-09-21 11:19:11 UTC
Target Upstream Version:
dalvarez: needinfo-

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 593056 0 'None' 'MERGED' 'Switch default neutron ML2 mechanism driver to OVN' 2019-11-15 10:56:15 UTC
Red Hat Product Errata RHEA-2019:2811 0 None None None 2019-09-21 11:19:30 UTC

Description Daniel Alvarez Sanchez 2018-10-17 14:36:27 UTC 
The goal of this BZ is to track the replacement of the default Neutron backend from ML2/OVS to ML2/OVN starting as of OSP 15.

Fresh deployments would get OVN by default while upgrades from earlier OSP versions should remain in ML2/OVS if they were already using it.

Documentation shall be written to highlight the gaps and limitations of ML2/OVN vs ML2/OVS as of today.
Comment 9 Eran Kuris 2019-05-15 13:48:01 UTC 
openstack-tripleo-heat-templates-10.5.1-0.20190509160423.4dac4dc.el8ost.noarch
OpenStack/15.0-RHEL-8/RHOS_TRUNK-15.0-RHEL-8-20190509.n.1

Fix verified
Comment 12 errata-xmlrpc 2019-09-21 11:19:11 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2019:2811
Note You need to log in before you can comment on or make changes to this bug.