yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #88041
[Bug 1956476] Re: [OVN] Disallow multiple physnets per bridge
Reviewed: https://review.opendev.org/c/openstack/neutron/+/823568
Committed: https://opendev.org/openstack/neutron/commit/55afd9bc923f55bc8f621316a080ad4271182ebc
Submitter: "Zuul (22348)"
Branch: master
commit 55afd9bc923f55bc8f621316a080ad4271182ebc
Author: Rodolfo Alonso Hernandez <ralonsoh@xxxxxxxxxx>
Date: Thu Dec 23 11:00:09 2021 +0000
[OVN] Allow only one physical network per bridge
Same as in other ML2 plugins (OVS, Linux Bridge), OVN mechanism driver
should allow only one physical network per bridge. The rule "one
network, one bridge" should be present in OVN too.
By allowing only one physical network per bridge, Neutron prevents
having two networks with subnets with the same CIDR in the same bridge.
Currently is possible and this CIDR clash is not prevented (shouldn't be
by the API). This architectural limitation prevents this situation.
This limitation is already present in deployment tools as TripleO.
Closes-Bug: #1956476
Change-Id: I74a2ca9a344a93219deb94d60247478ee3200659
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1956476
Title:
[OVN] Disallow multiple physnets per bridge
Status in neutron:
Fix Released
Bug description:
Related bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1993681
Patch [1] allowed to have multiple physical networks per bridge.
Although this could be feasible in OVN, the ML2 OVN mechanism driver
should not allow it. The OVN mech driver should have the same
behaviour as OVS or LB.
In the related bugzilla there are some steps to reproduce a configuration that leads to a subnet CIDR range conflict, when both networks are in the same bridge, that is not prohibited by Neutron. Steps to Reproduce:
1. Create two physical networks mapped to the same physical network
2. Enable both two physical networks as flat network providers
3. Create a flat network and a subnet with range 10.0.0.0/24 on the first physical network
3. Create another flat network and a subnet with range 10.0.0.0/24 on the second physical network
[1]https://github.com/openstack/networking-
ovn/commit/a4781fd0f9c59603638b41069a175547a24c4b1c
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1956476/+subscriptions
References