From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Fabian Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH-SERIES zsync] fix #1669: allow prepending storage ID
Date: Tue, 4 May 2021 14:01:22 +0200 [thread overview]
Message-ID: <b66a19bc-d56c-881b-4aff-ffc68af0e28b@proxmox.com> (raw)
In-Reply-To: <20210504081004.21898-1-f.ebner@proxmox.com>
On 04.05.21 10:09, Fabian Ebner wrote:
> which makes it possible to use pve-zsync for guests with disks with the same
> name on different storages, i.e.
> storageA:vm-123-disk-0
> storageB:vm-123-disk-0
>
> Currently they would collide to
> target/vm-123-disk-0
>
> When the new prepend-storage-id flag is specified, they will be synced to
> target/storageA/vm-123-disk-0$
> target/storageB/vm-123-disk-0$
> instead.
>
>
> The first four patches are cleanups/usage description fixes.
>
> The next five patches are preparations for the last patch, which is the one
> actually implementing the new feature.
>
>
> Fabian Ebner (10):
> whitespace fix
> copyright: update year
> usage: describe flag parameters correctly
> usage: fix type for maxsnap
> add target_dataset function
> add check_dataset_exists function
> add create_file_system function
> parse disks: don't include colon in storage name variable
> parse disks: also include storage ID information
> fix #1669: add prepend-storage-id flag
>
> pve-zsync | 118 ++++++++++++++++++++++++++++++++++++++++--------------
> 1 file changed, 89 insertions(+), 29 deletions(-)
>
applied series, thanks!
prev parent reply other threads:[~2021-05-04 12:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 8:09 [pve-devel] " Fabian Ebner
2021-05-04 8:09 ` [pve-devel] [PATCH zsync 01/10] whitespace fix Fabian Ebner
2021-05-04 8:09 ` [pve-devel] [PATCH zsync 02/10] copyright: update year Fabian Ebner
2021-05-04 8:09 ` [pve-devel] [PATCH zsync 03/10] usage: describe flag parameters correctly Fabian Ebner
2021-05-04 8:09 ` [pve-devel] [PATCH zsync 04/10] usage: fix type for maxsnap Fabian Ebner
2021-05-04 8:09 ` [pve-devel] [PATCH zsync 05/10] add target_dataset function Fabian Ebner
2021-05-04 8:10 ` [pve-devel] [PATCH zsync 06/10] add check_dataset_exists function Fabian Ebner
2021-05-04 8:10 ` [pve-devel] [PATCH zsync 07/10] add create_file_system function Fabian Ebner
2021-05-04 8:10 ` [pve-devel] [PATCH zsync 08/10] parse disks: don't include colon in storage name variable Fabian Ebner
2021-05-04 8:10 ` [pve-devel] [PATCH zsync 09/10] parse disks: also include storage ID information Fabian Ebner
2021-05-04 8:10 ` [pve-devel] [PATCH zsync 10/10] fix #1669: add prepend-storage-id flag Fabian Ebner
2021-05-04 12:01 ` Thomas Lamprecht [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=b66a19bc-d56c-881b-4aff-ffc68af0e28b@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-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