From: Christian Ebner <c.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox-backup 0/2] add default prune job and gc-schedule
Date: Wed, 29 Nov 2023 12:36:35 +0100 [thread overview]
Message-ID: <20231129113637.204053-1-c.ebner@proxmox.com> (raw)
These patches add a default prune job configuration and a default
garbage collection schedule to datastores created as part of disk/zpool
creation transactions.
This is to be consistent with the conventional creation of a datastore,
where these also are created so the user might not forget about it.
E.g.
`proxmox-backup-manager disk fs create <storage-name> --disk <block-device>
--add-datastore true` creates the datastore with daily gc-schedule and a
daily prune job with default keep options.
Currently, patch 0001 depends on this patch being applied:
https://lists.proxmox.com/pipermail/pbs-devel/2023-November/007336.html
I can send a v2 without this interdependecy if desired and/or required.
Christian Ebner (2):
api: create default prune job on datastore creation
api: create default garbage collection schedule
src/api2/node/disks/directory.rs | 30 ++++++++++++++++++++++++++----
src/api2/node/disks/zfs.rs | 32 +++++++++++++++++++++++++++-----
2 files changed, 53 insertions(+), 9 deletions(-)
--
2.39.2
next reply other threads:[~2023-11-29 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 11:36 Christian Ebner [this message]
2023-11-29 11:36 ` [pbs-devel] [PATCH proxmox-backup 1/2] api: create default prune job on datastore creation Christian Ebner
2023-11-29 13:27 ` Fabian Grünbichler
2023-11-29 13:31 ` Thomas Lamprecht
2023-11-29 13:54 ` Christian Ebner
2023-11-29 11:36 ` [pbs-devel] [PATCH proxmox-backup 2/2] api: create default garbage collection schedule Christian Ebner
2023-11-29 13:27 ` Fabian Grünbichler
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=20231129113637.204053-1-c.ebner@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-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