-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Migrate os-net-config from ifcfg to NMstate Support
-
8
-
False
-
-
False
-
Not Selected
-
Proposed
-
Proposed
-
To Do
-
OSPRH-9594 - Migration of nmstate provider from existing ifcfg based deployments
-
Proposed
-
Proposed
-
100% To Do, 0% In Progress, 0% Done
-
-
-
Important
With the deprecation of network init-scripts (including ifcfg files in /etc/sysconfig/network-scripts) in favor of NetworkManager, os-net-config must transition from ifcfg to NetworkManager-based implementations. This migration will involve implementing support for NetworkManager interfaces, such as nmcli, NMstate, or Ansible Networking, to replace ifcfg functionality. The goal is to achieve feature parity and seamless configuration management across all supported interface types.
Current State:
Currently, os-net-config configures all interfaces using ifcfg files and includes a script to set up SR-IOV virtual functions at boot. Additionally, os-net-config supports ethtool and ovs-vsctl commands to configure OVS settings.
Objective:
To transition os-net-config to NetworkManager, implementing support through NMstate or another NetworkManager interface to meet feature parity across all interface types currently supported by os-net-config.
Expected Outcome:
- Full migration to NetworkManager-based implementation (NMstate or similar).
Supported Device Types to Verify:
- OVS bridge/bonds, linux bonds, SR-IOV, NIC Partitioning and DPDK bridges/ports, ethernet interfaces, vlans on OVS bridges/Linux bonds/ethernet interface
Acceptance Criteria:
- Feature Parity: Verify that NMstate/NetworkManager supports all interface types and configurations currently managed by os-net-config.
- Automation and CI Integration: Ensure CI pipelines are updated to support NetworkManager/NMstate configurations with automated tests for validation.
- SR-IOV Compatibility: Confirm if the existing SR-IOV configuration script is necessary or if NetworkManager can manage SR-IOV VFs independently.
- Documentation: Update documentation to reflect the migration steps, configurations, and known limitations or considerations.