From Fedora Project Wiki
mNo edit summary
mNo edit summary
 
(17 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
= Removing network-scripts package =
= Removing network-scripts package =


Line 9: Line 5:
== Summary ==
== Summary ==


We are planning to remove the <code>network-scripts</code> package from Fedora 41. By removing the package, we are also removing support for legacy network scripts that have been deprecated since 2018.
<code>network-scripts</code> package will be removed in Fedora 41. By removing the package, we also remove support for legacy <code>ifup/ifdown</code> network scripts that have been deprecated since 2018.


== Owner ==
== Owner ==


* Name: [[User:jamacku| Jan Macku]]
* Name: [[User:jamacku| Jan Macku]]
* Email: jamacku@redhat.com
* Name: [[User:lnykryn| Lukáš Nykrýn]]
* Name: [[User:lnykryn| Lukáš Nykrýn]]
* Email: lnykryn@redhat.com
 
* Email: [mailto:jamacku@redhat.com jamacku@redhat.com]
* Email: [mailto:lnykryn@redhat.com lnykryn@redhat.com]


== Current status ==
== Current status ==
Line 38: Line 35:
== Detailed Description ==
== Detailed Description ==


We plan to remove the <code>network-scripts</code> package from Fedora 41. It provides legacy <code>ifup</code>/<code>ifdown</code> scripts as well as <code>network.service</code>.
<code>network-scripts</code> will be removed in Fedora 41. It provides legacy <code>ifup</code>/<code>ifdown</code> scripts as well as <code>network.service</code>.


The <code>network-scripts</code> were '''deprecated in 2018''', and since then, upstream has provided only limited support.  
The <code>network-scripts</code> were '''deprecated in 2018''', and since then, upstream has provided only limited support.  
Line 48: Line 45:


== Benefit to Fedora ==
== Benefit to Fedora ==
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
 
      Be sure to include the following areas if relevant:
      If this is a major capability update, what has changed?
          For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
      If this is a new functionality, what capabilities does it bring?
          For example: This change allows package upgrades to be performed automatically and rolled-back at will.
      Does this improve some specific package or set of packages?
          For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
      Does this improve specific Spins or Editions?
          For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
      Does this make the distribution more efficient?
          For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
      Is this an improvement to maintainer processes?
          For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
      Is this an improvement targeted as specific contributors?
          For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.


    When a Change has multiple benefits, it's better to list them all.
We don't deliver software that has been deprecated for many years, unmaintained upstream, and for which we don't have resources to maintain downstream. Additionally, it simplifies networking tasks for users and administrators because NetworkManager will be used more uniformly across Fedora environments.


    Consider these Change pages from previous editions as inspiration:
== Scope ==
    https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
    https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
    https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
    https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
    https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
-->


== Scope ==
* Proposal owners: Removing of <code>network-scripts</code> rpm package.
* Proposal owners:
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: Make sure that dependency on <code>network-scripts</code> package is removed (see [[Changes/NetworkScriptsRemoval#Dependencies| #Dependencies]]).
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: N/A (not needed for this Change)
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->


* Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: N/A (not needed for this Change)
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->


* Trademark approval: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->


* Alignment with Community Initiatives:  
* Alignment with Community Initiatives: N/A (not needed for this Change)
<!-- Does your proposal align with the current Fedora Community Initiatives: https://docs.fedoraproject.org/en-US/project/initiatives/ ? It's okay if it doesn't, but it's something to consider -->


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<code>ifup/ifdown</code> command are no longer available. Use <code>nmcli connection up/down</code> or <code>networkctl up/down</code> instead.


Old <code>ifcfg</code> network configuration should still work thanks to <code>NetworkManager-initscripts-ifcfg-rh</code> package. No migration is needed, but it is recommended to migrate from <code>ifcfg</code> to <code>keyfiles</code> configuration.


== How To Test ==
You can use one of the following articles on how to migrate:
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.


Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
* https://fedoramagazine.org/converting-networkmanager-from-ifcfg-to-keyfiles/
* https://opensource.com/article/22/8/migrate-networkmanager-keyfiles-configuration


A good "how to test" should answer these four questions:
== How To Test ==
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


Networking should work as before the removal of <code>network-scripts</code> package.


== User Experience ==
== User Experience ==
Line 133: Line 94:


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
RPM packages that depends in some form on <code>network-scripts</code>:


* <code>libteam</code> - https://bugzilla.redhat.com/show_bug.cgi?id=2262986
* <code>NetworkManager</code> - https://bugzilla.redhat.com/show_bug.cgi?id=2275295
* <code>openvswitch</code> - https://bugzilla.redhat.com/show_bug.cgi?id=2262982
* <code>ppp</code> - https://bugzilla.redhat.com/show_bug.cgi?id=2262981
Note that this will also affect all users with local custom network-scripts that require functionality from <code>network-scripts</code> package.


== Contingency Plan ==
== Contingency Plan ==


<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism: Since [https://fedoraproject.org/wiki/Changes/dhclient_deprecation dhcp client is no longer maintained] and is going to be deprecated in Fedora, there is currently no contingency mechanism.
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: beta freeze
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Blocks release: No
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Upstream Deprecation notice - https://github.com/fedora-sysv/initscripts/commit/b748244cf9905696baf1bc16e0432f85093414c2
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==

Latest revision as of 11:24, 21 May 2024

Removing network-scripts package

Important.png
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

network-scripts package will be removed in Fedora 41. By removing the package, we also remove support for legacy ifup/ifdown network scripts that have been deprecated since 2018.

Owner

Current status

  • Targeted release: Fedora Linux 41
  • Last updated: 2024-05-21
  • [<will be assigned by the Wrangler> devel thread]
  • FESCo issue: <will be assigned by the Wrangler>
  • Tracker bug: <will be assigned by the Wrangler>
  • Release notes tracker: <will be assigned by the Wrangler>

Detailed Description

network-scripts will be removed in Fedora 41. It provides legacy ifup/ifdown scripts as well as network.service.

The network-scripts were deprecated in 2018, and since then, upstream has provided only limited support.

The main reason for removing network-scripts is that ISC dhcp has not been maintained upstream since the end of 2022. There is plan to remove it upcoming Fedora release. Network scripts heavily depend on the DHCP client, and since Network Scripts are no longer developed, there is no chance of updating them to use an alternative client.

Feedback

Benefit to Fedora

We don't deliver software that has been deprecated for many years, unmaintained upstream, and for which we don't have resources to maintain downstream. Additionally, it simplifies networking tasks for users and administrators because NetworkManager will be used more uniformly across Fedora environments.

Scope

  • Proposal owners: Removing of network-scripts rpm package.
  • Other developers: Make sure that dependency on network-scripts package is removed (see #Dependencies).
  • Release engineering: N/A (not needed for this Change)
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Community Initiatives: N/A (not needed for this Change)

Upgrade/compatibility impact

ifup/ifdown command are no longer available. Use nmcli connection up/down or networkctl up/down instead.

Old ifcfg network configuration should still work thanks to NetworkManager-initscripts-ifcfg-rh package. No migration is needed, but it is recommended to migrate from ifcfg to keyfiles configuration.

You can use one of the following articles on how to migrate:

How To Test

Networking should work as before the removal of network-scripts package.

User Experience

Dependencies

RPM packages that depends in some form on network-scripts:

Note that this will also affect all users with local custom network-scripts that require functionality from network-scripts package.

Contingency Plan

  • Contingency mechanism: Since dhcp client is no longer maintained and is going to be deprecated in Fedora, there is currently no contingency mechanism.
  • Contingency deadline: beta freeze
  • Blocks release: No

Documentation

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/NetworkScriptsRemoval&oldid=710171"