Changes/cron-to-systemd-time-units

From FedoraProject

< Changes(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 re...")
 
(Change Proposal Name)
Line 22: Line 22:
 
<!-- 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 -->
 
<!-- 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 -->
  
= Change Proposal Name <!-- The name of your change proposal --> =
+
= cron to systemd time units  =
  
 
== Summary ==
 
== Summary ==
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. -->
+
Fix dependency on crontab in packages containing cron jobs as well as migrate cron jobs that are applicable to native systemd timer units.  
  
 
== Owner ==
 
== Owner ==
<!--
+
 
For change proposals to quality as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
+
* Name: [[User:Johannbg| Jóhann B. Guðmundsson]]
This should link to your home wiki page so we know who you are.
+
* Email: johannbg AT gmail DOT com
-->
+
 
* Name: [[User:FASAcountName| Your Name]]
+
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
+
* Email: <your email address so we can contact you, invite you to meetings, etc.>
+
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
+
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
+
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
+
-->
+
<!--- UNCOMMENT only if this Change aims specific product, working group (Cloud, Workstation, Server, Base, Env & Stacks)
+
* Product:
+
* Responsible WG:
+
-->
+
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]
 
* Last updated: (DATE)
 
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
 
Bugzilla states meaning as usual:
 
NEW -> change proposal is submitted and announced
 
ASSIGNED -> accepted by FESCo with on going development
 
MODIFIED -> change is substantially done and testable
 
ON_QA -> change is code completed and could be tested in the Beta release (optionally by QA)
 
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 
-->
 
* Tracker bug: <will be assigned by the Wrangler>
 
  
== Detailed Description ==
+
* Targeted release: [[Releases/Fedora 21 | Fedora 21 ]]
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+
* Last updated: 04/03/2014
  
== 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 functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
  
== Scope ==
+
== Detailed Description ==
<!-- What work do the developers have to accomplish to complete the change 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?-->
+
  
* Proposal owners:
+
Add dependency on crontab in packages containing cron jobs as well as migrate cron jobs that are applicable to native systemd timer units in packages that already depend on systemd.
<!-- 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: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
== Benefit to Fedora ==
<!-- 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: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
Proper dependency in packages shipping cron jobs. Better systemd integration in the distribution.
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuid required?  If a rel-eng ticket exists, add a link here.  -->
+
[edit]
  
* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
== Scope ==
<!-- 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. -->
+
 
 +
* Adjust packaging guidelines to fix dependency in cron packages [[Packaging/CronFiles| Package Cron Files]] DONE
 +
* Fix spec files in packages that are not applicable for migration [https://bugzilla.redhat.com/show_bug.cgi?id=947037 Fix Cron Dependency Tracking Bug]
 +
* Adjust packaging guidelines to mention migration of cron jobs to timer units for packages that already depend on systemd
 +
* Review and migrate if applicable cron jobs shipped in packages that already depend on systemd [https://bugzilla.redhat.com/show_bug.cgi?id=991679 Timer Migration Tracking Bug]
 +
* Update systemd wikipage to contain timer units example
  
 
== 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 -->
+
For application that are applicable for migration the cron job will be migrated to native timer units.
N/A (not a System Wide Change)
+
  
 
== How To Test ==
 
== How To Test ==
<!-- 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.
+
* Install the package that contains the new native systemd timer unit file.
 
+
* Check if the the time trigger ran
A good "how to test" should answer these four questions:
+
 
+
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 -->
+
N/A (not a System Wide Change)
+
  
 
== User Experience ==
 
== User Experience ==
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
+
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
Administrators will have better time trigger in units compared to cron jobs like for example when administrator stops a service/daemon the timer unit will stop as well etc.  
N/A (not a System Wide Change)
+
  
 
== 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 -->
+
No external dependency
N/A (not a System Wide Change)
+
  
 
== 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: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+
Continue to ship the cron jobs as is.  
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
+
* 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 -->
+
* Blocks product? product <-- Applicable for Changes that blocks specific product release/Fedora.next -->
+
  
 
== 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 -->
+
* updated guidelines and systemd wiki page
N/A (not a System Wide Change)
+
  
 
== 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 change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
 
  
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.  
+
There shouldn't be anything we need to specifically say other than highlighting the change.  
-->
+
  
[[Category:ChangePageIncomplete]]
+
[[Category:ChangeReadyForWrangler]]
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Revision as of 11:52, 4 March 2014

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 CHANGE PROPOSAL.


Contents

cron to systemd time units

Summary

Fix dependency on crontab in packages containing cron jobs as well as migrate cron jobs that are applicable to native systemd timer units.

Owner


Current status


Detailed Description

Add dependency on crontab in packages containing cron jobs as well as migrate cron jobs that are applicable to native systemd timer units in packages that already depend on systemd.

Benefit to Fedora

Proper dependency in packages shipping cron jobs. Better systemd integration in the distribution. [edit]

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 Fix Cron Dependency Tracking Bug
  • Adjust packaging guidelines to mention migration of cron jobs to timer units for packages that already depend on systemd
  • Review and migrate if applicable cron jobs shipped in packages that already depend on systemd Timer Migration Tracking Bug
  • Update systemd wikipage to contain timer units example

Upgrade/compatibility impact

For application that are applicable for migration the cron job will be migrated to native timer units.

How To Test

  • Install the package that contains the new native systemd timer unit file.
  • Check if the the time trigger ran

User Experience

Administrators will have better time trigger in units compared to cron jobs like for example when administrator stops a service/daemon the timer unit will stop as well etc.

Dependencies

No external dependency

Contingency Plan

Continue to ship the cron jobs as is.

Documentation

  • updated guidelines and systemd wiki page

Release Notes

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