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.
This PR adds support for VLAN tagging of overlay provider networks.
Provider VLANs
New option vlan in network provider configuration:
Overlay provider network VLAN tags are attached by OVN to all egress traffic from the VMs. This is accomplished by configuring the tag to the logical switch port of the external router port that connects from the project network to the provider network.
Bridge VLANs and IP mode
The bridge adapter is not affected by the provider's VLAN setting. The default configuration for an overlay adapter also doesn't enable the bridge adapter for network communications.
For scenarios where we have few (or only one) network adapters, the bridge can now be configured to be enabled for DHCP by default. For this case, we now also have the option to configure a VLAN for the bridge adapter:
See also #144 for static address configuration support.