F41 Change Proposal: Remove ifcfg support in NetworkManager (system-wide)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Wiki - https://fedoraproject.org/wiki/Changes/RemoveIfcfgSupportInNM
Discussion Thread -

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.


== Summary ==

Remove support for connection profiles stored in ifcfg format in NetworkManager.

== Owner ==
* Name: [[User:bengal| Beniamino Galvani]], [[User:ffmancera| Fernando
Fernández Mancera]], [[User:Till| Till Maas]]
* Email: <bgalvani@xxxxxxxxxx>, <ferferna@xxxxxxxxxx>, <till@xxxxxxxxxxxxxxxxx>


== Detailed Description ==

NetworkManager supports different formats to persist connection
profiles to disk. The two formats currently in use in Fedora are
''keyfile'' and ''ifcfg''.

[https://networkmanager.dev/docs/api/latest/nm-settings-keyfile.html
Keyfile] is the native and preferred format. It supports all the
connection types and all the features.
[https://networkmanager.dev/docs/api/latest/nm-settings-ifcfg-rh.html
Ifcfg] is compatible with the old network-scripts. It only supports a
limited set of connection types, and it is
[https://lists.freedesktop.org/archives/networkmanager/2023-May/000103.html
deprecated] upstream.

This change proposal aims at removing NetworkManager support for ifcfg
files in Fedora. This is the last step of a process started several
releases ago:
* in Fedora 33, the default connection format was changed from ifcfg to keyfile;
* in Fedora 36, the plugin that handles ifcfg files was shipped in a
separate package and was not included in new installations;
* since Fedora 39, the NetworkManager daemon automatically migrates
ifcfg files to the keyfile format.

== Benefit to Fedora ==

Since ifcfg support is going to be removed upstream, it must also be
removed in Fedora. Keyfile is a valid and better replacement.

== Scope ==

* Proposal owners: drop the following packages:
** `NetworkManager-initscripts-ifcfg-rh` containing the ifcfg plugin
** `NetworkManager-dispatcher-routing-rules` containing a dispatcher
script to apply routing rules in ifcfg format
** `NetworkManager-initscripts-updown` containing alternative
ifup/ifdown scripts compatible with initscripts commands, using
NetworkManager.
* Other developers: N/A
* Release engineering: N/A
* Policies and guidelines: N/A
* Trademark approval: N/A

== Upgrade/compatibility impact ==

At this point no users should have connection profiles stored in ifcfg
format, as NetworkManager is automatically migrating them to keyfile
since Fedora 39.

According to [https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline
documentation] , system upgrades are supported only over 2 releases at
most (e.g. from 38 to 40); therefore, users upgrading to Fedora 41
must come from Fedora 39 or 40, which have the migration enabled.

If some users disabled the migration, they might still have ifcfg
files in `/etc/sysconfig/network-scripts`. A “readme-ifcfg-rh.txt”
file there warns users that the format is deprecated and is going to
be removed.

== How To Test ==
* Try to install the NetworkManager-initscripts-ifcfg-rh package
* The package is not available.

== User Experience ==

See the “Upgrade/compatibility impact” section.

== Dependencies ==
None

== Contingency Plan ==

* Contingency mechanism: Revert the change, try again the next Fedora release.
* Contingency deadline: Beta freeze
* Blocks release? no

== Documentation ==
No documentation change required.

== Release Notes ==
The change needs to be mentioned in the Release Notes.


-- 
Aoife Moloney

Fedora Operations Architect

Fedora Project

Matrix: @amoloney:fedora.im

IRC: amoloney
--
_______________________________________________
devel-announce mailing list -- devel-announce@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-announce-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux