From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager/docs] handle missed jobs better
Date: Wed, 1 Jun 2022 12:23:17 +0200 [thread overview]
Message-ID: <20220601102321.4093592-1-d.csapak@proxmox.com> (raw)
by adding a config option 'skip-missed' for jobs that skips the jobs
on pvescheduler start and when changing from disabled -> enabled
i did not use the systemd name 'persistent' since the name does
not really convey what it means, so i tried to come up with
a better name for it (the logic is just reversed from the systemd
variant, and our default is 0)
pve-manager:
Dominik Csapak (3):
fix #4026: add 'skip-missed' option for jobs
fix #4053: enable 'skip-missed' behaviour also for change from
disabled->enabled
ui: dc/Backup: add 'skip-missed' checkbox
PVE/API2/Backup.pm | 33 +++++++++++++++++++++++++++++----
PVE/Jobs.pm | 5 +++++
PVE/Jobs/Plugin.pm | 6 ++++++
PVE/Jobs/VZDump.pm | 1 +
PVE/Service/pvescheduler.pm | 6 +++++-
www/manager6/dc/Backup.js | 9 +++++++++
6 files changed, 55 insertions(+), 5 deletions(-)
pve-docs:
Dominik Csapak (1):
vzdump: add section about 'skip-missed'
vzdump.adoc | 6 ++++++
1 file changed, 6 insertions(+)
--
2.30.2
next reply other threads:[~2022-06-01 10:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 10:23 Dominik Csapak [this message]
2022-06-01 10:23 ` [pve-devel] [PATCH manager 1/3] fix #4026: add 'skip-missed' option for jobs Dominik Csapak
2022-06-01 10:23 ` [pve-devel] [PATCH manager 2/3] fix #4053: enable 'skip-missed' behaviour also for change from disabled->enabled Dominik Csapak
2022-06-01 10:23 ` [pve-devel] [PATCH manager 3/3] ui: dc/Backup: add 'skip-missed' checkbox Dominik Csapak
2022-06-01 10:23 ` [pve-devel] [PATCH docs 1/1] vzdump: add section about 'skip-missed' Dominik Csapak
2022-06-02 7:07 ` [pve-devel] [PATCH manager/docs] handle missed jobs better Thomas Lamprecht
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=20220601102321.4093592-1-d.csapak@proxmox.com \
--to=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