all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>,
	"Proxmox Backup Server development discussion"
	<pbs-devel@lists.proxmox.com>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: Re: [pbs-devel] [PATCH v3 proxmox-backup] ui: warn of missing gc-schedule, prune/verify jobs
Date: Mon, 11 Dec 2023 11:59:55 +0100 (CET)	[thread overview]
Message-ID: <1720255851.3759.1702292395719@webmail.proxmox.com> (raw)
In-Reply-To: <29aa81de-aa7b-4246-8d4e-9f7c1e566435@proxmox.com>

> On 11.12.2023 11:43 CET Thomas Lamprecht <t.lamprecht@proxmox.com> wrote:
> 
> 
> I'd just use the daily timer which we use for sending out notifications about
> available apt updates.
> 
> I.e., just some fixed-scheduled daily health checking, that, e.g., can be
> configured in the nodes' config, but only some params like the low-water
> mark for when to send the alert.

Okay, will integrate a low storage space datastore sanity check and prune + gc-schedule
verification there, sending a notification if the configured threshold is reached.

> 
> We use that also in PVE, i.e., we do not check for specific VMIDs as there access
> is covered by what the API returns anyway, the overall datastore list would be
> the same, but what one can do within not, so yeah Datastore.Audit might not have
> been the best example here.

Thanks for the feedback!

Cheers,
Chris




      reply	other threads:[~2023-12-11 10:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-06 11:31 Christian Ebner
2023-12-06 13:37 ` Gabriel Goller
2023-12-06 14:09 ` Fabian Grünbichler
2023-12-06 14:43   ` Christian Ebner
2023-12-11  9:09     ` Thomas Lamprecht
2023-12-11  9:44       ` Christian Ebner
2023-12-11 10:43         ` Thomas Lamprecht
2023-12-11 10:59           ` Christian Ebner [this message]

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=1720255851.3759.1702292395719@webmail.proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=f.gruenbichler@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=t.lamprecht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal