public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Fabian Ebner <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH-SERIES storage/manager/guest-common/docs] improvements for protected backups
Date: Mon, 20 Dec 2021 11:31:20 +0100	[thread overview]
Message-ID: <976dac28-05b7-12cb-b534-dfdb9712db93@proxmox.com> (raw)
In-Reply-To: <20211216121233.162288-1-f.ebner@proxmox.com>

one question:

either it's not explained, or i missed it:
what do we gain by having a limit on the number of protected backups?

storage 2/2 mentions that protection broke some assumption of vzdump
which is (somehow? not really explained imho) fixing it?

if it's not fixing it, what is the relation between those things?

also, why have a 'magic' -1 value that means indefinite, we could
simply always have that behavior?

in my opinion, it makes no sense to limit the number of protected
backups..

if it is necessary for some reason, it would be good to include
that reason either in the commit message, or at least in the cover
letter...

On 12/16/21 13:12, Fabian Ebner wrote:
> The series consists of two parts:
> 
> First part (up to docs 2/2) is for introducing a storage property
> to limit the number of protected backups and only count unprotected
> backups for the limit check in vzdump.
> 
> Second part is a convenience feature allowing 'protected' and 'notes'
> to be set directly with vzdump and for manual backups in the UI.
> 
> 
> storage:
> 
> Fabian Ebner (2):
>    list volumes: also return backup type for backups
>    plugins: allow limiting the number of protected backups per guest
> 
>   PVE/Storage.pm                 | 24 ++++++++++++++++++++++++
>   PVE/Storage/BTRFSPlugin.pm     |  3 ++-
>   PVE/Storage/CIFSPlugin.pm      |  1 +
>   PVE/Storage/CephFSPlugin.pm    |  1 +
>   PVE/Storage/DirPlugin.pm       |  1 +
>   PVE/Storage/GlusterfsPlugin.pm |  1 +
>   PVE/Storage/NFSPlugin.pm       |  1 +
>   PVE/Storage/PBSPlugin.pm       |  2 ++
>   PVE/Storage/Plugin.pm          |  8 ++++++++
>   test/list_volumes_test.pm      | 10 ++++++++++
>   10 files changed, 51 insertions(+), 1 deletion(-)
> 
> 
> manager:
> 
> Fabian Ebner (6):
>    vzdump: backup file list: drop unused parameter
>    vzdump: backup limit: only count unprotected backups
>    ui: storage edit: retention: add max-protected-backups setting
>    ui: storage creation: retention: dynamically adapt
>      max-protected-backups
>    vzdump: support setting protected status and notes
>    ui: backup: allow setting protected and notes for manual backup
> 
>   PVE/VZDump.pm                        | 69 ++++++++++++++++++---------
>   www/manager6/panel/BackupJobPrune.js | 71 ++++++++++++++++++++++++----
>   www/manager6/storage/Base.js         |  1 +
>   www/manager6/window/Backup.js        | 25 +++++++++-
>   4 files changed, 132 insertions(+), 34 deletions(-)
> 
> 
> guest-common:
> 
> Fabian Ebner (1):
>    vzdump: schema: add 'notes' and 'protected' properties
> 
>   src/PVE/VZDump/Common.pm | 14 +++++++++++++-
>   1 file changed, 13 insertions(+), 1 deletion(-)
> 
> 
> docs:
> 
> Fabian Ebner (2):
>    storage: switch to prune-backups in examples
>    vzdump/storage: mention protected backups limit and give an example
> 
>   pve-storage-dir.adoc | 9 +++++----
>   pve-storage-pbs.adoc | 2 +-
>   vzdump.adoc          | 3 +++
>   3 files changed, 9 insertions(+), 5 deletions(-)
> 





  parent reply	other threads:[~2021-12-20 10:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 12:12 Fabian Ebner
2021-12-16 12:12 ` [pve-devel] [PATCH storage 1/2] list volumes: also return backup type for backups Fabian Ebner
2022-03-16 16:42   ` [pve-devel] applied: " Thomas Lamprecht
2021-12-16 12:12 ` [pve-devel] [PATCH storage 2/2] plugins: allow limiting the number of protected backups per guest Fabian Ebner
2022-03-16 16:42   ` Thomas Lamprecht
2022-03-17  8:03     ` Fabian Ebner
2022-03-17  8:11       ` Thomas Lamprecht
2021-12-16 12:12 ` [pve-devel] [PATCH manager 1/6] vzdump: backup file list: drop unused parameter Fabian Ebner
2021-12-16 12:12 ` [pve-devel] [PATCH manager 2/6] vzdump: backup limit: only count unprotected backups Fabian Ebner
2021-12-16 12:12 ` [pve-devel] [RFC manager 3/6] ui: storage edit: retention: add max-protected-backups setting Fabian Ebner
2021-12-16 12:12 ` [pve-devel] [RFC manager 4/6] ui: storage creation: retention: dynamically adapt max-protected-backups Fabian Ebner
2021-12-16 12:12 ` [pve-devel] [PATCH docs 1/2] storage: switch to prune-backups in examples Fabian Ebner
2021-12-16 12:12 ` [pve-devel] [PATCH docs 2/2] vzdump/storage: mention protected backups limit and give an example Fabian Ebner
2021-12-16 12:12 ` [pve-devel] [PATCH guest-common 1/1] vzdump: schema: add 'notes' and 'protected' properties Fabian Ebner
2022-03-16 11:04   ` Fabian Ebner
2022-03-16 18:25     ` Thomas Lamprecht
2022-03-17  7:57       ` Fabian Ebner
2022-03-17  8:07         ` Thomas Lamprecht
2022-03-17  8:18           ` Fabian Ebner
2022-03-17  8:20             ` Thomas Lamprecht
2021-12-16 12:12 ` [pve-devel] [PATCH manager 5/6] vzdump: support setting protected status and notes Fabian Ebner
2021-12-16 12:12 ` [pve-devel] [PATCH manager 6/6] ui: backup: allow setting protected and notes for manual backup Fabian Ebner
2021-12-20 10:31 ` Dominik Csapak [this message]
2021-12-21 15:11   ` [pve-devel] [PATCH-SERIES storage/manager/guest-common/docs] improvements for protected backups Thomas Lamprecht
2021-12-22  7:02     ` Dominik Csapak
2022-01-03  9:12       ` Fabian Ebner
2022-03-10  7:46 ` Fabian Ebner

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=976dac28-05b7-12cb-b534-dfdb9712db93@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=f.ebner@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal