Features/cron-to-systemd-time-units

From FedoraProject

< Features
Revision as of 10:05, 6 January 2014 by Johannbg (Talk | contribs)

Jump to: navigation, search

Contents

cron-to-systemd-time-units

Summary

Introducing new systemd documentation feature along with various units cleanups.

Owner

Current status

  • Targeted release: Fedora 21
  • Last updated:
  • Percentage of completion: 21

Detailed Description

Benefit to Fedora

Adding the Documentation Field will bring more informational status output to our users base which links to the relevant man pages for the daemon/service.

EnvironmentalFiles that reside in /etc/sysconfig directory are Fedora specific which makes those unit not upstream feasible and work against the de-balkanization of the Linux platform.

If it's truly necessary for those environment files to be continued to be used which is rather exception than a rule since users/administrator should be using How_do I customize a unit file when altering daemon/service startup, they should be placed in a subdir directly in /etc with the name of the package/subsystem and the environment file reference point to that instead.


Scope

  • Adjust packaging guidelines to fix dependency in cron packages Package Cron Files DONE
  • Fix spec files in packages that are not applicable for migration Tracker bug
  • Review and migrate if applicable cron jobs shipped in packages that already depend on systemd

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 service starts cleanly after install
    • check if the service stops cleanly after and install
    • Check if the service reloads cleanly correctly if applicable
    • Check if the service status output contains reference to the relevant man pages
  • 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

Other than the added informative documentation field in the units status output the user should not notice any change.

Dependencies

No external dependency

Contingency Plan

Continue to ship the cron jobs as is

Documentation

  • It's recommended that documentation for relevant applications that contained and used EnvironmentFile reference points users to How_do I customize a unit file use instead when altering daemon/service startup.

Release Notes

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

Comments and Discussion