public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Hannes Laimer <h.laimer@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH v1 proxmox-backup 0/5] add scheduled verification of datastore
Date: Fri, 18 Sep 2020 10:34:02 +0200	[thread overview]
Message-ID: <20200918083407.69140-1-h.laimer@proxmox.com> (raw)

Adds support for scheduling the verification of datastores the same way
GC or Prune is scheduled.

Hannes Laimer (5):
  api2: add VERIFY_SCHEDULE_SCHEMA
  add verify_schedule field to DataStoreConfig
  api2: add optional verify-schdule field to create/update datastore
    endpoint
  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         |   6 ++
 www/config/DataStoreConfig.js   |   5 +-
 www/window/DataStoreEdit.js     |   9 +++
 6 files changed, 136 insertions(+), 3 deletions(-)

-- 
2.20.1





             reply	other threads:[~2020-09-18  8:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18  8:34 Hannes Laimer [this message]
2020-09-18  8:34 ` [pbs-devel] [PATCH v1 proxmox-backup 1/5] api2: add VERIFY_SCHEDULE_SCHEMA Hannes Laimer
2020-09-18  8:34 ` [pbs-devel] [PATCH v1 proxmox-backup 2/5] add verify_schedule field to DataStoreConfig Hannes Laimer
2020-09-18  8:34 ` [pbs-devel] [PATCH v1 proxmox-backup 3/5] api2: add optional verify-schdule field to create/update datastore endpoint Hannes Laimer
2020-09-18  8:34 ` [pbs-devel] [PATCH v1 proxmox-backup 4/5] ui: add verify-schedule field to edit datastore form Hannes Laimer
2020-09-18  8:34 ` [pbs-devel] [PATCH v1 proxmox-backup 5/5] add verification scheduling to proxmox-backup-proxy Hannes Laimer

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=20200918083407.69140-1-h.laimer@proxmox.com \
    --to=h.laimer@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