feat(neutron): make our VXLAN type driver unique #663
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cardoe
force-pushed
the
update-vxlan-type
branch
3 times, most recently
from
3ed9091 to
8d7e6e7
Compare
|
Do not merge until the |
cardoe
force-pushed
the
update-vxlan-type
branch
3 times, most recently
from
f92d5b1 to
4365960
Compare
Instead of standing in for the VXLAN type driver directly, have it be its own thing that will be ignored by mechanisms that consume it. The reason is that the existing VXLAN type driver is treated and consumed as a L3VNI while we need L2VNI.
If we use VXLAN as the encapsulation type then OVN sets the max ID to 4095. This is then enforced on all networks in the change openstack/neutron@ef0ec21186d93e and users have reported this limitation in https://bugs.launchpad.net/neutron/+bug/1951517 Since we're not looking for OVN to establish VXLAN tunnels for us at this time we can really ignore this because OVN ignores any ports and segments without a physical_network setting. OpenStack enforces that VXLAN type does not have a physical_network set so these won't be created in OVN.
cardoe
force-pushed
the
update-vxlan-type
branch
from
4365960 to
0ea3f31
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of standing in for the VXLAN type driver directly, have it be its own thing that will be ignored by mechanisms that consume it. The reason is that the existing VXLAN type driver is treated and consumed as a L3VNI while we need L2VNI.