Features/SysVtoSystemd

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
Line 17: Line 17:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/Fedora <number> | Fedora <number> ]]  
+
* Targeted release: [[Releases/Fedora 16 | Fedora 16 ]]  
 
* Last updated:  
 
* Last updated:  
 
* Percentage of completion: 0
 
* Percentage of completion: 0
Line 26: Line 26:
  
 
== 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?-->
+
 
 +
* 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 section regular service activation, hardware activated on, 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
 +
 
 +
 
  
 
== 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.
  
A good "how to test" should answer these four questions:
+
*Check if the old sysvinit init script did get removed after install
  
0. What special hardware / data / etc. is needed (if any)?
+
*Check if the service starts cleanly after install
1. How do I prepare my system to test this feature? What packages
+
*check if the service stops cleanly after and install
need to be installed, config files edited, etc.?
+
*Enable the service, restart check if service was enabled after restart
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
  
 
== 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 note that service and chkconfig commands 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 might have changed as in an service might have been split into more then one service file need updating thou 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. -->
+
There shouldn't be anything we need to specifically say other than highlighting the change.
*
+
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==

Revision as of 20:12, 18 May 2011

Important.png
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.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.
Important.png
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
Note.png
All sections of this template are required for review by FESCo. If any sections are empty it will not be reviewed

Contents

SysV to Systemd

Summary

Porting from sysVinit init scripts to systemd unit file.

Owner

Current status

  • Targeted release: Fedora 16
  • Last updated:
  • Percentage of completion: 0

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?

Benefit to Fedora

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

Scope

  • 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 section regular service activation, hardware activated on, 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


How To Test

  • Install/update to the package that contains the new native systemd unit file.
  • 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
  • Enable the service, restart check if service was enabled after restart

User Experience

Native systemd service configuration files are much easier to understand and configure compared to sysvinit scripts

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 note that service and chkconfig commands 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 might have changed as in an service might have been split into more then one service file need updating thou 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