public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: "Proxmox Backup Server development discussion"
	<pbs-devel@lists.proxmox.com>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/2] api: create default prune job on datastore creation
Date: Wed, 29 Nov 2023 14:54:00 +0100 (CET)	[thread overview]
Message-ID: <523329318.1118.1701266040813@webmail.proxmox.com> (raw)
In-Reply-To: <1701264220.irmoe4u1io.astroid@yuna.none>

> On 29.11.2023 14:27 CET Fabian Grünbichler <f.gruenbichler@proxmox.com> wrote:
> 
> is this documented anywhere?

No, there is no documentation on this. I will have to include that as well in a new
version of the patches.

> `proxmox-backup-manager datastore create ..` does not add any
> schedules/jobs by default, it's just the web UI that does (but that also
> tells you about this, and allows you to override it!)

Yes, that is indeed true. I would argue for an increased usability by a default
creation of prune job and garbage collection schedules with well documented defaults
for all possible datastore creation routes, and allow to override these defaults via
the optional parameters.
Are there objections to such a change in behavior? This should further
be considered a breaking change for the API, I suppose.
 
> 
> I agree that it probably makes sense, but it should be consistent
> - web UI does it, but then it should display it (and it would need to
>   become a new optional parameter here, maybe by extending
>   "add_datastore", else overriding would not be possible)
> - proxmox-backup-manager does it, but then it should also do it for a
>   "plain" datastore creation by default?

You are right in that these patches are not sufficient to create consistent behavior
for all possible cases. I will have to refine and extend this.

Thank you for your feedback!

Cheers,
Chris




  parent reply	other threads:[~2023-11-29 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 11:36 [pbs-devel] [PATCH proxmox-backup 0/2] add default prune job and gc-schedule Christian Ebner
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 [this message]
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=523329318.1118.1701266040813@webmail.proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=f.gruenbichler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal