Persist jumbo frame (MTU 9000) configuration and allow customizable bond name in HNV

When Hybrid Network Virtualisation provisions a bond interface, two persistent issues affect day-to-day operations most:

1. The MTU (jumbo frame) setting is not retained after any major changes on the network.

The bond name is auto-generated (e.g., bond4182d769) with no option to define a meaningful, predictable name.

Issue 1 - MTU (jumbo frame) configuration is not persisted

After any major changes on the network, the MTU 9000 setting is lost and must be manually reapplied, followed by a NetworkManager restart to bring the setting back into effect:

nmcli connection modify bond4182d769 802-3-ethernet.mtu 9000systemctl restart NetworkManager

While the reapplication can be automated via Ansible, a NetworkManager restart is still required, and on a productive LPAR, restarting the network is a disruptive operation that cannot always be executed without a maintenance window.

Issue 2 - Bond name cannot be customized

The bond name assigned by HNV is auto-generated and UUID-based (e.g., bond4182d769). Attempts to rename it always fail: after any reboot or reprovisioning event, HNV recreates the bond using a new random name, discarding the change entirely. There is currently no workaround.

Requested improvements:

Persist the MTU setting - if jumbo frames (MTU 9000) are configured, that value should be written durably to the HNV managed connection profile and survive any major network changes. This is the primary request.

Customizable bond name - allow operators to define a meaningful bond name at provisioning time (e.g., bond-hnv-mgmt, bondDB) instead of receiving a UUID-based auto-generated name that cannot be changed.

Business impact:

• MTU drift causes silent performance degradation on storage and high-throughput workloads with no immediate error signal.

Unpredictable bond names break automation tools (e.g., Ansible playbooks) that reference the interface by name, requiring constant updates or workarounds. When multiple HNV bonds are present on the same LPAR, a custom name per bond would also allow clear identification of each one.

Both issues require recurring manual remediation, introducing human error and slowing down deployment and recovery workflows.