[Bug 1115430] New: [TRACKERBUG-OPENSUSE] FATE#323635: Reduce usage of cron in favour of systemd timers
http://bugzilla.suse.com/show_bug.cgi?id=1115430
Bug ID: 1115430 Summary: [TRACKERBUG-OPENSUSE] FATE#323635: Reduce usage of cron in favour of systemd timers Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: kstreitova@suse.com Reporter: kstreitova@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: ---
This is a tracker bug for fate#323635 (Reduce usage of cron package in favor of systemd timers). It tracks openSUSE packages only (for SLE packages see bug#1115399).
The goal is to minimize the number of openSUSE:Factory packages that use cron in favour of systemd timers. See dependent bugs for more information about particular packages that should be migrated.
http://bugzilla.suse.com/show_bug.cgi?id=1115430
Kristyna Streitova kstreitova@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1115434, 1115435, 1115436, | |1115438, 1115439, 1115442, | |1115443, 1115444, 1115445, | |1115446, 1115447, 1115448, | |1115451, 1115452, 1115453, | |1115454, 1115455, 1115456, | |1115457, 1115458, 1115459
http://bugzilla.suse.com/show_bug.cgi?id=1115430 http://bugzilla.suse.com/show_bug.cgi?id=1115430#c1
Wolfgang Rosenauer wolfgang@rosenauer.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wolfgang@rosenauer.org
--- Comment #1 from Wolfgang Rosenauer wolfgang@rosenauer.org --- Is it possible to give some pointers to packagers how systemd timers should look like in openSUSE? I've spent a few minutes searching the wiki if there is dedicated information on it but haven't found anything. openSUSE:Systemd packaging guidelines does not have anything on timers. Could easily be that I missed it but I think this tracking bug is a good place to indicate some pointers packagers could use if they have not been in touch with systemd-timers much.
http://bugzilla.suse.com/show_bug.cgi?id=1115430 http://bugzilla.suse.com/show_bug.cgi?id=1115430#c2
Kristyna Streitova kstreitova@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS
--- Comment #2 from Kristyna Streitova kstreitova@suse.com --- Thanks for bringing this idea. I've created a systemd timers section at opensuse wiki [1]. It covers the basic packaging schema. I suppose that it can happen that each package can need a little bit different approach as the purpose of the former cron entry can be various.
So anybody can enhance this wiki page when he/she encounters a situation that can be interesting for other packagers dealing with the cron->timers migration.
[1] https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#Systemd_timers
http://bugzilla.suse.com/show_bug.cgi?id=1115430
Jan Ritzerfeld suse@bugs.jan.ritzerfeld.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |suse@bugs.jan.ritzerfeld.or | |g
http://bugzilla.suse.com/show_bug.cgi?id=1115430
Oliver Kurz okurz@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |okurz@suse.com
http://bugzilla.suse.com/show_bug.cgi?id=1115430 http://bugzilla.suse.com/show_bug.cgi?id=1115430#c5
Flavio Castelli fcastelli@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fcastelli@suse.co | |m) |
--- Comment #5 from Flavio Castelli fcastelli@suse.com --- It is true that running systemd inside of an **application** container (like one started by Docker) is tricky. However this isn't something really needed on a daily basis. Application containers have a completely different use case from system containers (like the ones created by LXC and LXD).
Because of that I would find really really wrong to have someone running cron jobs inside of application containers.
I think you don't have to worry about containers (neither application, nor system) in this discussion.
http://bugzilla.suse.com/show_bug.cgi?id=1115430 http://bugzilla.suse.com/show_bug.cgi?id=1115430#c6
--- Comment #6 from Michael Ströder michael@stroeder.com --- Disclaimer: I'm not a container expert.
(In reply to Flavio Castelli from comment #5)
It is true that running systemd inside of an **application** container (like one started by Docker) is tricky.
AFAIK it is not recommended to modify a container setup to allow running systemd because of some security implications. Thus there won't be systemd available in normal container setups.
However this isn't something really needed on a daily basis. Application containers have a completely different use case from system containers (like the ones created by LXC and LXD).
Because of that I would find really really wrong to have someone running cron jobs inside of application containers.
Frankly I don't understand your answer.
Personally I think that running a DNS resolver like unbound in a Docker container on e.g. an elastic Kubernetes cluster is something users definitely want. Thus requiring systemd for installing and using unbound package is a real obstacle for such a setup.
I think you don't have to worry about containers (neither application, nor system) in this discussion.
I strongly disagree.
http://bugzilla.suse.com/show_bug.cgi?id=1115430 http://bugzilla.suse.com/show_bug.cgi?id=1115430#c7
--- Comment #7 from Kristyna Streitova kstreitova@suse.com --- General info for packagers dealing with the migration: Please see [1] for more information about enabling timers and mainly how to pick the correct preset package where to put your timer (systemd-presets-common-SUSE or systemd-presets-branding-openSUSE).
[1] https://en.opensuse.org/openSUSE:Systemd_packaging_guidelines#Enabling_syste...
http://bugzilla.suse.com/show_bug.cgi?id=1115430
Kristyna Streitova kstreitova@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |1140077
http://bugzilla.suse.com/show_bug.cgi?id=1115430
Bug 1115430 depends on bug 1115445, which changed state.
Bug 1115445 Summary: logwatch: migrate from cron to systemd timers http://bugzilla.suse.com/show_bug.cgi?id=1115445
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
http://bugzilla.suse.com/show_bug.cgi?id=1115430
Bug 1115430 depends on bug 1115438, which changed state.
Bug 1115438 Summary: cyrus-imapd: migrate from cron to systemd timers http://bugzilla.suse.com/show_bug.cgi?id=1115438
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID
http://bugzilla.suse.com/show_bug.cgi?id=1115430
Bug 1115430 depends on bug 1115459, which changed state.
Bug 1115459 Summary: yum: migrate from cron to systemd timers http://bugzilla.suse.com/show_bug.cgi?id=1115459
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX
http://bugzilla.suse.com/show_bug.cgi?id=1115430
Bug 1115430 depends on bug 1115443, which changed state.
Bug 1115443 Summary: leafnode: migrate from cron to systemd timers http://bugzilla.suse.com/show_bug.cgi?id=1115443
What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED
https://bugzilla.suse.com/show_bug.cgi?id=1115430
Bug 1115430 depends on bug 1115436, which changed state.
Bug 1115436 Summary: cacti: migrate from cron to systemd timers https://bugzilla.suse.com/show_bug.cgi?id=1115436
What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED
https://bugzilla.suse.com/show_bug.cgi?id=1115430
Bug 1115430 depends on bug 1115434, which changed state.
Bug 1115434 Summary: apt-cacher-ng: migrate from cron to systemd timers https://bugzilla.suse.com/show_bug.cgi?id=1115434
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX
https://bugzilla.suse.com/show_bug.cgi?id=1115430
Danilo Spinella danilo.spinella@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |danilo.spinella@suse.com Assignee|kstreitova@suse.com |danilo.spinella@suse.com OS|openSUSE Factory |All
https://bugzilla.suse.com/show_bug.cgi?id=1115430
Bug 1115430 depends on bug 1115435, which changed state.
Bug 1115435 Summary: atop: migrate from cron to systemd timers https://bugzilla.suse.com/show_bug.cgi?id=1115435
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
https://bugzilla.suse.com/show_bug.cgi?id=1115430
Bug 1115430 depends on bug 1115457, which changed state.
Bug 1115457 Summary: storeBackup: migrate from cron to systemd timers https://bugzilla.suse.com/show_bug.cgi?id=1115457
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FEATURE
https://bugzilla.suse.com/show_bug.cgi?id=1115430
Bug 1115430 depends on bug 1115455, which changed state.
Bug 1115455 Summary: rkhunter: migrate from cron to systemd timers https://bugzilla.suse.com/show_bug.cgi?id=1115455
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com