Improve bond and VLAN naming consistency during migration from NethSecurity 7 #1479
Description
Description
When migrating from NethSecurity 7 to NethSecurity 8, the naming of bond devices and VLANs on top of bonds is not consistent with a clean NethSecurity 8 installation.
This inconsistency leads to a non-uniform UI visualization, longer and less readable bond names, and may potentially impact HA behavior.
Why this is an issue
In a clean NethSecurity 8 installation, bond and VLAN device names follow a shorter and more consistent naming scheme.
During migration from NethSecurity 7, additional prefixes are introduced, resulting in different device names for functionally identical configurations.
This causes:
- Non-uniform visualization in the UI
- Less readable and longer bond and VLAN names
- Possible side effects on components that rely on interface naming consistency, including HA
Technical details
During migration, VLAN devices on top of a bond are created with an extra bond- prefix in the name field.
Example during migration:
config device 'vlan20'
option type '8021q'
option vid '20'
option ifname 'bond-bond0'
option name 'bond-bond0.20'
In a clean installation, the same VLAN is created without the additional prefix in the name field:
config device 'fjfhksdfui'
option type '8021q'
option vid '20'
option ifname 'bond-bond0'
option name 'bond0.20'
The difference is limited to the name field, but it propagates to the UI and possibly to other subsystems.
Proposed solution
Align the migration logic with the naming convention used in clean NethSecurity 8 installations by:
- Removing the extra
bond-prefix from VLAN device names created during migration - Ensuring that bond and VLAN names match those generated by a fresh installation
This would provide consistent naming across all setups and improve UI uniformity.
Devices as displayed after a migration
in a fresh installation they would have been just bond0.xx
Components
NethSecurity 8.7.1