public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: Re: [pbs-devel] [PATCH v2 proxmox-backup 0/6] add scheduled verification of datastore
Date: Fri, 18 Sep 2020 12:10:39 +0200	[thread overview]
Message-ID: <ef26b2e3-f644-971f-26c7-7da42a66a0ea@proxmox.com> (raw)
In-Reply-To: <20200918090052.79979-1-h.laimer@proxmox.com>

like we talked off-list

verification schedules are wanted, but
we probably want to have them more like we have sync-jobs
independent of datastores

(so we can have multiple verification schedules per datastore,
which will be important once we have parameters such as
'verify only unverified snapshots')

also please use the 'Job' helper for keeping track of the state
since that is cheaper than searching for the last time in the
task list

On 9/18/20 11:00 AM, Hannes Laimer wrote:
> Adds support for scheduling the verification of datastores the same way
> GC or Prune is scheduled.
> 
> v2:  - add patch to make verify-schedule deletable
> 
> Hannes Laimer (6):
>    api2: add VERIFY_SCHEDULE_SCHEMA
>    add verify_schedule field to DataStoreConfig
>    api2: add optional verify-schdule field to create/update datastore
>      endpoint
>    api2: make verify_schedule deletable
>    ui: add verify-schedule field to edit datastore form
>    add verification scheduling to proxmox-backup-proxy
> 
>   src/api2/config/datastore.rs    |  10 +++
>   src/api2/types/mod.rs           |   5 ++
>   src/bin/proxmox-backup-proxy.rs | 104 +++++++++++++++++++++++++++++++-
>   src/config/datastore.rs         |   9 ++
>   www/config/DataStoreConfig.js   |   5 +-
>   www/window/DataStoreEdit.js     |   9 +++
>   6 files changed, 139 insertions(+), 3 deletions(-)
> 





  parent reply	other threads:[~2020-09-18 10:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  9:00 Hannes Laimer
2020-09-18  9:00 ` [pbs-devel] [PATCH v2 proxmox-backup 1/6] api2: add VERIFY_SCHEDULE_SCHEMA Hannes Laimer
2020-09-18  9:00 ` [pbs-devel] [PATCH v2 proxmox-backup 2/6] add verify_schedule field to DataStoreConfig Hannes Laimer
2020-09-18  9:00 ` [pbs-devel] [PATCH v2 proxmox-backup 3/6] api2: add optional verify-schdule field to create/update datastore endpoint Hannes Laimer
2020-09-18  9:00 ` [pbs-devel] [PATCH v2 proxmox-backup 4/6] api2: make verify_schedule deletable Hannes Laimer
2020-09-18  9:00 ` [pbs-devel] [PATCH v2 proxmox-backup 5/6] ui: add verify-schedule field to edit datastore form Hannes Laimer
2020-09-18 13:26   ` Thomas Lamprecht
2020-09-18  9:00 ` [pbs-devel] [PATCH v2 proxmox-backup 6/6] add verification scheduling to proxmox-backup-proxy Hannes Laimer
2020-09-18 10:10 ` Dominik Csapak [this message]
2020-09-18 13:23   ` [pbs-devel] [PATCH v2 proxmox-backup 0/6] add scheduled verification of datastore Thomas Lamprecht
2020-09-18 10:13 ` [pbs-devel] applied: " Dietmar Maurer

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=ef26b2e3-f644-971f-26c7-7da42a66a0ea@proxmox.com \
    --to=d.csapak@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