From: Dietmar Maurer <dietmar@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 0/7] pull/sync group filter
Date: Mon, 26 Jul 2021 10:01:15 +0200 [thread overview]
Message-ID: <f142eca4-299f-354f-3674-161981f450b8@proxmox.com> (raw)
In-Reply-To: <20210722143510.238967-1-f.gruenbichler@proxmox.com>
As discussed offline, we want to make the filter more flexible, e.g.:
-group vm/100 # this is what we have now
-group regex:vm/.* # a regex
-group type:ct #all containers
-exclude-groups true # exclude specified groups instead of include
...
On 7/22/21 4:35 PM, Fabian Grünbichler wrote:
> this has been requested a few times on the forum, e.g. for a special
> sync job for the most important groups, or seeding of a new datastore
> with a partial view of an existing one.
>
> while it's possible to achieve similar results with hacky workarounds
> based on group ownership and reduced "visibility", implementing it
> properly is not that complex.
>
> possible future additions in a similar fashion:
> - only sync/pull encrypted snapshots (less trusted off-site location)
> - only sync/pull latest snapshot in each group (fast seeding of new
> datastore)
>
> Fabian Grünbichler (7):
> api-types: add schema for backup group
> pull: allow pulling groups selectively
> sync: add group filtering
> remote: add backup group scanning
> manager: extend sync/pull completion
> manager: render group filter properly
> manager: don't complete sync job ID on creation
>
> pbs-api-types/src/lib.rs | 4 +
> src/api2/config/remote.rs | 69 +++++++++++++++-
> src/api2/config/sync.rs | 22 ++++++
> src/api2/pull.rs | 36 ++++++++-
> src/bin/proxmox-backup-manager.rs | 105 ++++++++++++++++++++++---
> src/bin/proxmox_backup_manager/sync.rs | 22 +++++-
> src/config/sync.rs | 10 +++
> src/server/pull.rs | 24 +++++-
> www/config/SyncView.js | 13 ++-
> www/window/SyncJobEdit.js | 12 +++
> 10 files changed, 295 insertions(+), 22 deletions(-)
>
prev parent reply other threads:[~2021-07-26 8:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 14:35 Fabian Grünbichler
2021-07-22 14:35 ` [pbs-devel] [PATCH proxmox-backup 1/7] api-types: add schema for backup group Fabian Grünbichler
2021-07-22 14:35 ` [pbs-devel] [PATCH proxmox-backup 2/7] pull: allow pulling groups selectively Fabian Grünbichler
2021-07-22 14:35 ` [pbs-devel] [PATCH proxmox-backup 3/7] sync: add group filtering Fabian Grünbichler
2021-07-22 14:35 ` [pbs-devel] [PATCH proxmox-backup 4/7] remote: add backup group scanning Fabian Grünbichler
2021-07-22 14:35 ` [pbs-devel] [PATCH proxmox-backup 5/7] manager: extend sync/pull completion Fabian Grünbichler
2021-07-22 14:35 ` [pbs-devel] [PATCH proxmox-backup 6/7] manager: render group filter properly Fabian Grünbichler
2021-07-22 14:35 ` [pbs-devel] [PATCH proxmox-backup 7/7] manager: don't complete sync job ID on creation Fabian Grünbichler
2021-07-26 8:01 ` Dietmar Maurer [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=f142eca4-299f-354f-3674-161981f450b8@proxmox.com \
--to=dietmar@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