Features/SysVtoSystemd

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Created page with '{{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 rea...')
 
(Owner)
 
(31 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.'''}}
+
= SysV to Systemd =
 
+
{{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 }}
+
 
+
 
+
<!-- All fields on this form are required to be accepted by FESCo.
+
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
+
 
+
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
+
 
+
= Feature Name <!-- The name of your feature --> =
+
  
 
== Summary ==
 
== Summary ==
<!-- A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release. -->
+
 
 +
Continue porting from sysVinit init scripts to systemd unit file.
  
 
== Owner ==
 
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
 
* Name: [[User:FASAcountName| Your Name]]
 
  
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
+
* Name: [[User:Johannbg| Jóhann B. Guðmundsson]]
* Email: <your email address so we can contact you, invite you to meetings, etc.>
+
* Email: johannbg AT gmail DOT com
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
+
* Targeted release: [[Releases/Fedora 21 | Fedora 21 ]]  
* Last updated: (DATE)
+
* Last updated: 2014-01-06
* Percentage of completion: XX%
+
* Percentage of completion: 80
 
+
* Progress Tracker [https://bugzilla.redhat.com/show_bug.cgi?id=713562 Bug.]
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
+
  
 
== Detailed Description ==
 
== Detailed Description ==
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+
 
 +
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 ==
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
+
 
 +
See previous feature page concerning systemd for the benefits this will bring to Fedora which can be found [[systemd|here]].
  
 
== Scope ==
 
== Scope ==
<!-- What work do the 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?-->
+
 
 +
* 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
 +
* 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 [[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 ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature 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 feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
+
*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
  
A good "how to test" should answer these four questions:
+
*Enable the service then restart
 
+
**check if the shutdown process happened cleanly with the service enabled
0. What special hardware / data / etc. is needed (if any)?
+
**check if the service started cleanly at startup
1. How do I prepare my system to test this feature? What packages
+
need to be installed, config files edited, etc.?
+
2. What specific actions do I perform to check that the feature is
+
working like it's supposed to?
+
3. What are the expected results of those actions?
+
-->
+
  
 
== User Experience ==
 
== User Experience ==
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
+
 
 +
Native systemd service configuration files are much easier to understand and configure compared to sysvinit scripts and the bootup process should get faster.
  
 
== Dependencies ==
 
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature 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 feature)? -->
+
 
 +
Depends on present of systemd being installed which is the case for Fedora 15 and onwards.
  
 
== 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 "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->
+
 
 +
Continue to ship the old sysvinit init script.  
  
 
== Documentation ==
 
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
+
 
*
+
* 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]].
 +
 
 +
* 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 ==
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
*
 
  
== Comments and Discussion ==
+
There shouldn't be anything we need to specifically say other than highlighting the change as we have done for previous releases.
* 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 -->
+
  
 +
== Comments and Discussion ==
 +
* 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:FeatureReadyForWrangler]
 +
<!-- [[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 -->

Latest revision as of 12:16, 6 January 2014

Contents

[edit] SysV to Systemd

[edit] Summary

Continue porting from sysVinit init scripts to systemd unit file.

[edit] Owner

[edit] Current status

  • Targeted release: Fedora 21
  • Last updated: 2014-01-06
  • Percentage of completion: 80
  • Progress Tracker Bug.

[edit] 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.

[edit] Benefit to Fedora

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

[edit] 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.

[edit] 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

[edit] 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.

[edit] Dependencies

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

[edit] Contingency Plan

Continue to ship the old sysvinit init script.

[edit] 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.

[edit] Release Notes

There shouldn't be anything we need to specifically say other than highlighting the change as we have done for previous releases.

[edit] Comments and Discussion

[Category:FeatureReadyForWrangler]