-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
False
-
Satellite Rocket Sprint 2, Satellite Rocket Sprint 7, Satellite Rocket Sprint 8, Satellite Rocket Sprint 9, Satellite Rocket Sprint 10
-
sat-rocket
-
None
-
None
-
None
-
None
Goal:
Foreman has various recurring tasks that today run via cron. Foremanctl should avoid cron and instead try to provide container native solutions where possible.
This story is about porting over the tasks to use systemd timers as a direct port. This is a short term solution where SAT-40686 is a proper solution.
The timers should follow a default schedule, ideally aiming at aligning the jobs to a regular pattern that falls into:
- Hourly
- Daily
- Weekly
- Monthly
The timers may use RandomizedDelaySec= or FixedRandomDelay= to avoid all jobs on the server running at exactly the same time, but is not a requirement.
Acceptance criteria:
- All cronjobs that run today are converted to systemd timers
- The approach is documented in foremanctl's docs directory so that there's a reference design we can point to
- depends on
-
SAT-39376 Add quadlet timer for foreman recurring task (reports:daily) by archanaserver · Pull Request #252 · theforeman/foremanctl · GitHub
-
- Closed
-
-
SAT-39830 Add Quadlet timer for Foreman recurring task (db:sessions:clear) by archanaserver · Pull Request #271 · theforeman/foremanctl · GitHub
-
- Closed
-
- is triggering
-
SAT-40686 Rework Foreman's recurring tasks in foremanctl
-
- Refinement
-