From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>,
Hannes Laimer <h.laimer@proxmox.com>,
Dietmar Maurer <dietmar@proxmox.com>
Subject: Re: [pbs-devel] [PATCH v2 proxmox-backup 0/6] add scheduled verification of datastore
Date: Fri, 18 Sep 2020 15:23:08 +0200 [thread overview]
Message-ID: <531614ab-ad43-a615-ef9f-2665ececa4cb@proxmox.com> (raw)
In-Reply-To: <ef26b2e3-f644-971f-26c7-7da42a66a0ea@proxmox.com>
On 9/18/20 12:10 PM, Dominik Csapak wrote:
> 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
>
agree here. Dominik and I discussed this a bit and a schedule panel
where one can not only add different schedules with different options
but also one schedule for multiple/all datastores seems like better UX.
It makes it easier to set "catch all" schedules, and get an overview over
schedules.
This includes things like adding a "next run" column, which would crowd
the space in the datastore config grid a lot.
next prev parent reply other threads:[~2020-09-18 13:23 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 ` [pbs-devel] [PATCH v2 proxmox-backup 0/6] add scheduled verification of datastore Dominik Csapak
2020-09-18 13:23 ` Thomas Lamprecht [this message]
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=531614ab-ad43-a615-ef9f-2665ececa4cb@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=dietmar@proxmox.com \
--cc=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