From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH cluster/manager v2] add scheduling daemon for pvesr + vzdump (and more)
Date: Wed, 10 Nov 2021 21:42:06 +0100 [thread overview]
Message-ID: <a337ef4d-02ec-162c-209e-9affdb3021f4@proxmox.com> (raw)
In-Reply-To: <20211108130758.160914-1-d.csapak@proxmox.com>
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 ^^
next prev parent reply other threads:[~2021-11-10 20:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 13:07 [pve-devel] " Dominik Csapak
2021-11-08 13:07 ` [pve-devel] [PATCH cluster v2 1/1] add 'jobs.cfg' to observed files Dominik Csapak
2021-11-09 17:18 ` [pve-devel] applied: " Thomas Lamprecht
2021-11-08 13:07 ` [pve-devel] [PATCH manager v2 1/6] replace systemd timer with pvescheduler daemon Dominik Csapak
2021-11-08 13:07 ` [pve-devel] [PATCH manager v2 2/6] add PVE/Jobs to handle VZDump jobs Dominik Csapak
2021-11-08 13:07 ` [pve-devel] [PATCH manager v2 3/6] pvescheduler: run jobs from jobs.cfg Dominik Csapak
2021-11-08 13:07 ` [pve-devel] [PATCH manager v2 4/6] api/backup: refactor string for all days Dominik Csapak
2021-11-08 13:07 ` [pve-devel] [PATCH manager v2 5/6] api/backup: handle new vzdump jobs Dominik Csapak
2021-11-08 13:07 ` [pve-devel] [PATCH manager v2 6/6] ui: dc/backup: show id+schedule instead of dow+starttime Dominik Csapak
2021-11-09 14:17 ` [pve-devel] [PATCH cluster/manager v2] add scheduling daemon for pvesr + vzdump (and more) Dylan Whyte
2021-11-10 9:38 ` Dominik Csapak
2021-11-10 11:05 ` Thomas Lamprecht
2021-11-09 16:55 ` Aaron Lauterer
2021-11-10 20:42 ` Thomas Lamprecht [this message]
2021-11-11 11:35 ` Fabian Ebner
2021-11-11 11:46 ` Dominik Csapak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a337ef4d-02ec-162c-209e-9affdb3021f4@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox