On 08.11.21 14:07, Dominik Csapak wrote: > pve-cluster: > > Dominik Csapak (1): > add 'jobs.cfg' to observed files > > data/PVE/Cluster.pm | 1 + > data/src/status.c | 1 + > 2 files changed, 2 insertions(+) > > pve-manager: > > Dominik Csapak (5): > add PVE/Jobs to handle VZDump jobs > pvescheduler: run jobs from jobs.cfg > api/backup: refactor string for all days > api/backup: handle new vzdump jobs > ui: dc/backup: show id+schedule instead of dow+starttime > > Thomas Lamprecht (1): > replace systemd timer with pvescheduler daemon
applied series, thanks! It's obv. time to call it a day now as I forgot to apply Dylan's and Aaron's T-b tags, sorry about that, but they certainly assured me and allowed to invest less time here, thanks to both of you testers! I made a few smaller followup on top: bd0af783 ui: form/calendar event: add some more complex examples 90d66ebf ui: form/calendar event: increase width of combobox picker 9569c89b ui: backup job: limit ID to 20 chars for now 3fc5bbc4 ui: backup job: ellipsize read-only ID on edit ae8c5aba ui: backup job: avoid row wrapping due to overly long label @Dominik, please still check the other reply to the followup series: https://lists.proxmox.com/pipermail/pve-devel/2021-November/050863.html And I think now it would be a good time to add that scheduler simulation API call to get the next X actual date-times and calendar event would trigger, which we could use to provide a small button for the users to show them their 10 (or so) next events, at least that functionality from `systemd-analyze calendar <event>` always helps me a lot to reassure my systemd.timer units are going off as planned ^^ _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
