Current text: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/administration_guide/chap-logical_networks#sect-Explanation_of_Settings_and_Controls_in_the_New_Logical_Network_and_Edit_Logical_Network_Windows
The text does not reflect that in case the network's name is either long or contains non-ASCII character, the bridge name on the host will differ (to patch linux bridge ascii/15 char limitation)
more information can be found at https://www.ovirt.org/develop/release-management/features/network/unrestricted-network-names/
(The new "vdsm_name" (the on-host identifier) will match "name", if "name" doesn't exceed IFNAMSIZ and only contains ASCII characters (to ease debugging and backwards compatibility). Otherwise, the new "vdsm_name" is to be auto-generated by Engine according to a pattern
where XXXXXXXXXXXXX are 13 hexadecimal characters extracted from the UUID of the network.)
While the 15 character limitation does appear in the 4.1 guide, in the 4.2 guide I see it mentioned in two different places.
Can you please confirm whether the limitation should be removed from both places?
1. In 18.104.22.168 Configuring Hosts for an OVN Tunnel Network
The VDSM_Network_Name is limited to 15 characters.
2. In 22.214.171.124. Connecting an OVN Network to a Physical Network
it says "The physical network’s name must not be longer than 15 characters, or contain special characters. "
Leon, following our conversation, i decided to focus only on the 4.1 documentation.
I see that it says "The logical network name is limited to 15 characters for Manager version 4.1.5 and earlier."
Meaning that it does not apply to 4.1.6 onwards.
Therefore, there doesn't seem to be anything to fix. The 4.2 documentation is already correct. I would like to close this bug.
yes, logical network names are not restricted to 15 characters post 4.1.5
(In reply to Leon Goldberg from comment #3)
> yes, logical network names are not restricted to 15 characters post 4.1.5
So can you confirm that there is nothing to fix? The issue already seems to be correctly documented.
What's missing is that if a user uses a name that exceeds 15 characters and/or contains non-ascii characters, the name on the host will differ from the name in engine -- this should be documented
The updated information, together with documentation about new mapping tool, is available in the Customer Portal: