Features/SysVtoSystemd

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(User Experience)
(Edited last updated date)
(24 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section.  They are invisible when viewing this page.  To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
 
 
{{admon/important | Set a Page Watch| Make sure you click ''watch'' on your new page so that you are notified of changes to it by others, including the Feature Wrangler}}
 
 
{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}
 
 
 
= SysV to Systemd =
 
= SysV to Systemd =
  
Line 17: Line 11:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/Fedora 16 | Fedora 16 ]]  
+
* Targeted release: [[Releases/Fedora 18 | Fedora 18 ]]  
* Last updated:  
+
* Last updated: 2012-06-05
* Percentage of completion: 0
+
* Percentage of completion: 60
 +
* Progress Tracker [https://bugzilla.redhat.com/show_bug.cgi?id=713562 Bug.]
  
 
== Detailed Description ==
 
== Detailed Description ==
  
coordination to ensure the best user experience. The best case is that all services which have shipped with system v init scripts in the past are upgraded to have systemd unit files in one Fedora release. The next best thing would be for individual services to transition to unit files only in the lead up to a new release. Today the FPC passed a clarification to have a warning about the latter put into the guidelines. This ticket is to find out what can be done about the former. Could we have a FES ticket to get people to work on this for F16? Is there another way to coordinate this?
+
Coordinating feature regarding conversion of sysvinit init scripts to native systemd service files to ensure the best user experience.  
 +
 
 +
The best outcome is that we manage to convert all services from sysvinit scripts to native systemd unit files preferable in one Fedora release Fedora 17.
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
Line 31: Line 28:
 
== Scope ==
 
== Scope ==
  
 +
* Review all service files that got provided and potentially shipped in F15 and make sure they meet the packaging guidelines. The list of those packages can be found [[User:Johannbg/QA/Systemd/compatability|here]]. 
 
* Create a wiki page containing all package we ship that contain sysvinit init scripts
 
* Create a wiki page containing all package we ship that contain sysvinit init scripts
* Identify which packages contain sysvinit init scripts that are hardware activated socket activated and dbus activated  
+
* Identify which packages contain sysvinit init scripts that are hardware activated, socket activated and dbus activated  
* Divide that page into four section regular service activation, hardware activated on, socket activated ones and dbus activated ones.  
+
* Divide that page into four sections: regular service activation, hardware activated ones, socket activated ones and dbus activated ones.  
* Developers will need to convert the old sysvinit init script to native systemd one and or review and use ones that have been provided to them then package and ship
+
* Developers will need to convert the old sysvinit init scripts to native systemd ones and/or review and use ones that have been provided to them and package them as per packaging guidelines which can be found [[Packaging:Guidelines:Systemd | here]] with sample scriptlet snippet which can be found [[Packaging:ScriptletSnippets#Systemd|here]] no later then beta for inclusions in the release.
 
+
 
+
  
 
== How To Test ==
 
== How To Test ==
Line 65: Line 61:
 
== Documentation ==
 
== Documentation ==
  
* It's recommended that documentation is updated to reflect usage of the native systemd commands instead of service and chkconfig commands note that service and chkconfig commands are backwards compatible up to a certain extent.  
+
* It's recommended that documentation is updated to reflect usage of the native systemd commands instead of service and chkconfig commands although that service and chkconfig commands will continue to work and are backwards compatible up to a certain extent.  
  
 
* An example usage of systemd commands usage compared to service and chkconfig ones can be found [[SysVinit_to_Systemd_Cheatsheet | here]].
 
* An example usage of systemd commands usage compared to service and chkconfig ones can be found [[SysVinit_to_Systemd_Cheatsheet | here]].
  
* Some documentation regarding starting and stopping some service might need to be updated since the sysvinit init script ight have been split into more then one service file note that should not be the general case.
+
* Some documentation regarding starting and stopping some service might need to be updated since the sysvinit init script might have been split into more then one service files. Note that should not be the general case.
  
 
== Release Notes ==
 
== Release Notes ==
Line 76: Line 72:
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
* See [[Talk:Features/YourFeatureName]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
+
* See [[Talk:Features/SysVtoSystemd]]  <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
 
+
  
[[Category:FeaturePageIncomplete]]
+
[[Category:FeatureAcceptedF18]]
 +
<!-- [[Category:FeatureAcceptedF17]] --
 
<!-- When your feature page is completed and ready for review -->
 
<!-- When your feature page is completed and ready for review -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Revision as of 11:56, 20 June 2012

Contents

SysV to Systemd

Summary

Porting from sysVinit init scripts to systemd unit file.

Owner

Current status

  • Targeted release: Fedora 18
  • Last updated: 2012-06-05
  • Percentage of completion: 60
  • Progress Tracker Bug.

Detailed Description

Coordinating feature regarding conversion of sysvinit init scripts to native systemd service files to ensure the best user experience.

The best outcome is that we manage to convert all services from sysvinit scripts to native systemd unit files preferable in one Fedora release Fedora 17.

Benefit to Fedora

See previous feature page concerning systemd for the benefits this will bring to Fedora which can be found here.

Scope

  • Review all service files that got provided and potentially shipped in F15 and make sure they meet the packaging guidelines. The list of those packages can be found here.
  • Create a wiki page containing all package we ship that contain sysvinit init scripts
  • Identify which packages contain sysvinit init scripts that are hardware activated, socket activated and dbus activated
  • Divide that page into four sections: regular service activation, hardware activated ones, socket activated ones and dbus activated ones.
  • Developers will need to convert the old sysvinit init scripts to native systemd ones and/or review and use ones that have been provided to them and package them as per packaging guidelines which can be found here with sample scriptlet snippet which can be found here no later then beta for inclusions in the release.

How To Test

  • Install/update to the package that contains the new native systemd unit file.
    • Check if the update process happened cleanly
    • Check if the old sysvinit init script did get removed after install
    • Check if the service starts cleanly after install
    • check if the service stops cleanly after and install
    • Check if the service reloads cleanly correctly if applicable
  • Enable the service then restart
    • check if the shutdown process happened cleanly with the service enabled
    • check if the service started cleanly at startup

User Experience

Native systemd service configuration files are much easier to understand and configure compared to sysvinit scripts and the bootup process should get faster.

Dependencies

Depends on present of systemd being installed which is the case for Fedora 15 and onwards.

Contingency Plan

Continue to ship the old sysvinit init script.

Documentation

  • It's recommended that documentation is updated to reflect usage of the native systemd commands instead of service and chkconfig commands although that service and chkconfig commands will continue to work and are backwards compatible up to a certain extent.
  • An example usage of systemd commands usage compared to service and chkconfig ones can be found here.
  • Some documentation regarding starting and stopping some service might need to be updated since the sysvinit init script might have been split into more then one service files. Note that should not be the general case.

Release Notes

There shouldn't be anything we need to specifically say other than highlighting the change.

Comments and Discussion