From Fedora Project Wiki
(Replaced content with "{{warning|This proposal was removed by it's feature submitter since it no longer was applicable due to requirements by FESCO/FPC. Please submit an new feature proposal for...")
Line 1: Line 1:
<!-- Self Contained or System Wide Change Proposal?
+
{{warning|This proposal was removed by it's feature submitter since it no longer was applicable due to requirements by FESCO/FPC. Please submit an new feature proposal for this feature which has been adjusted to meet those requirments and outlines those changes and how they are going to be impelemented in the distribution. }}
Use this guide to determine to which category your proposed change belongs to.
 
 
 
Self Contained Changes are:
 
* changes to isolated/leaf package without the impact on other packages/rest of the distribution
 
* limited scope changes without the impact on other packages/rest of the distribution
 
* coordinated effort within SIG with limited impact outside SIG functional area, accepted by the SIG
 
 
 
System Wide Changes are:
 
* changes that does not fit Self Contained Changes category touching
 
* changes that require coordination within the distribution (for example mass rebuilds, release engineering or other teams effort etc.)
 
* changing system defaults
 
 
 
For Self Contained Changes, sections marked as "REQUIRED FOR SYSTEM WIDE CHANGES" are OPTIONAL but FESCo/Wrangler can request more details (especially in case the change proposal category is
 
improper or updated to System Wide category). For System Wide Changes all fields on this form are required for FESCo acceptance (when applies). 
 
 
 
We request that you maintain the same order of sections so that all of the change proposal pages are uniform.
 
-->
 
 
 
<!-- 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 -->
 
 
 
= 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 ==
 
 
 
* Name: [[User:Johannbg| Jóhann B. Guðmundsson]]
 
* Email: johannbg AT gmail DOT com
 
* Release notes owner: <!--- To be assigned by docs team [[User:FASAccountName| Release notes owner name]] <email address> -->
 
 
 
== Current status ==
 
 
 
* Targeted release: [[Releases/Fedora 21 | Fedora 21 ]]
 
* Last updated: 04/03/2014
 
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1076445 #1076445]
 
 
 
== 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.
 
 
 
== Scope ==
 
 
 
* Policies and guidelines: 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 ==
 
 
 
For application that are applicable for migration the cron job will be migrated to native timer units.
 
 
 
List of components might be migrated are here.
 
 
 
<pre>
 
amavisd-new
 
apt
 
arm4
 
atop
 
bcfg2
 
clement
 
cyrus-imapd
 
dbmail
 
denyhosts
 
dspam
 
exim
 
fetch-crl
 
freeipa
 
hylafax+
 
inn
 
leafnode
 
ltsp
 
mailman
 
mcelog
 
mdadm
 
mldonkey
 
newscache
 
nsd
 
opendnssec
 
openvas-scanner
 
ovirt-engine
 
ovirt-node
 
polipo
 
sagator
 
sipwitch
 
spamassassin
 
squidGuard
 
subscription-manager
 
sysstat
 
vdsm
 
vnstat
 
yum-cron
 
</pre>
 
 
 
== 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 ==
 
 
 
* Contingency mechanism: Continue to ship the cron jobs as is.
 
* Contingency deadline: N/A
 
* Blocks release: No
 
 
 
== Documentation ==
 
 
 
* updated guidelines and systemd wiki page
 
 
 
== Release Notes ==
 
 
 
There shouldn't be anything we need to specifically say other than highlighting the change.
 
 
 
[[Category:ChangePageIncomplete]]
 
 
 
<!---[[Category:ChangeAcceptedF21]] -->
 
<!-- When your change proposal page is completed and ready for review and announcement -->
 
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
 
<!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
 
<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
 
 
 
<!-- Select proper category, default is Self Contained Change -->
 
<!-- [[Category:SystemWideChange]] -->
 
<!-- [[Category:SystemWideChange]] -->
 

Revision as of 12:22, 16 October 2014

Stop (medium size).png