F21 System Wide Change: cron to systemd time units

["Jóhann B. Guðmundsson"]

On 03/04/2014 02:54 PM, Miloslav Trmač wrote:
> Hello,
> 2014-03-04 15:32 GMT+01:00 Jaroslav Reznik <jreznik at redhat.com 
> <mailto:jreznik at redhat.com>>:
>
>     = Proposed System Wide Change: cron to systemd time units =
>     https://fedoraproject.org/wiki/Changes/cron-to-systemd-time-units
>

I'm not so sure this should be a system wide change since the migration 
it self affects less then half of total shipped cron jobs and for those 
that arent it only updates the components specfile to current packaging 
guidelines.

>     == Scope ==
>
>
> (Everyone), please keep the explicit "Proposal owners"/"other 
> developers"/"release engineering"/"policies and guidelines" split.  
> Other contributors /need/ to know what they are being asked to do by 
> your Change.

Accept patches that's what I'm "asking" of them.

>
>     * Policies and guidelines:
>
>     ** Adjust packaging guidelines to mention migration of cron jobs
>     to timer
>     units for packages that already depend on systemd
>
>
> Last time this was discussed in 
> http://meetbot.fedoraproject.org/fedora-meeting/2013-02-06/fesco.2013-02-06-18.00.log.html 
> , there were concerns about "confusion of users/admins", specifically 
> referring to the disabling a .service / disabling a .socket duality.  
> So we will need packaging guidelines not only for the migration, but 
> for the timer units themselves.

Not following here we already have packaging guidelines for systemd units

>
> (From the Change page:)
>
>     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. 
>
> This would also seem to require detailed packaging guidelines for the 
> timer units.
>
>     * Fix spec files in packages that are not applicable for migration
>     [Fix Cron
>     Dependency Tracking Bug 2]
>     * Review and migrate if applicable cron jobs shipped in packages
>     that already
>     depend on systemd [Timer Migration Tracking Bug 3]
>
>
> How many packages (at least an of magnitude) are we talking about?  Is 
> it the 16+3 that are currently blocking the tracker bugs?
>      Mirek
>

To be clear not all cron jobs will be migrate, things like the drupal 
cron job "wget -O - -q -t 1 http://www.example.com/cron.php" wont be 
migrated since drupal does not depend on systemd and thus has no 
business being migrated but "mailman" cron job will be migrated since 
mailman ships a daemon hence unit and already depends on systemd so 
components that are applicable for migration due to their existing 
dependency on systemd are....

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

For the above components cron jobs will be manually inspected each and 
everyone *before* being decided if it will be migrated.

JBG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20140304/1211ff79/attachment.html>