From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
"d.kral@proxmox.com" <d.kral@proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 storage 05/10] rbd plugin: implement volume import/export
Date: Thu, 19 Dec 2024 09:56:37 +0100 [thread overview]
Message-ID: <4907685d-5331-40b1-8630-6ed71b9ff71e@proxmox.com> (raw)
In-Reply-To: <mailman.268.1734536036.332.pve-devel@lists.proxmox.com>
Am 18.12.24 um 16:33 schrieb DERUMIER, Alexandre via pve-devel:
>>> Am 18.12.24 um 15:20 schrieb Daniel Kral:
>>>> - When exporting with "pvesm export ...", the volume has the same
>> checksum as with "rbd export ..." with the size header prepended
>
>>> Well, I totally missed the existence of "rbd export" in my hurry to
>>> get
>>> this working. Seems to be about 1.5 times faster than mapping+dd from
>>> some initial testing. Will use that in v3.
>
> Hi, fiona, rbd export|import, this is the way, like zfs send|receive.
> (with snapshot support too, with export-diff|import-diff)
>
Saw that in the man page, and yes, would be the way to go for an 'rbd'
transport format with incremental support similar to 'zfs' :)
> I't really fast because, if I remember, it's use big block size and is
> able to do parallelism. (can be tunned with --rbd-concurrent-
> management-ops <number> )
>
We'll need to evaluate trade-off between speed and putting more load on
the system/Ceph. After all, the disk move might not be the most
important thing happening at that moment.
> No related, but could it be possible to implement it, for simple
> vm/template full cloning with source+target are both rbd ? It's really
> faster with 'qemu-img convert'
Hmm, we could shift offline copy of images to the storage layer (at
least in some cases). We just need a version of storage_migrate() that
goes to the local node instead of SSH to a different one. Could you
please open a feature request for this?
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-12-19 8:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 15:48 [pve-devel] [PATCH v2 storage 00/10] import/export for shared storages Fiona Ebner
2024-12-17 15:48 ` [pve-devel] [PATCH v2 storage 01/10] iscsi direct plugin: fix return value for path() method in non-array context Fiona Ebner
2024-12-18 13:39 ` Fiona Ebner
2024-12-18 13:43 ` Fiona Ebner
2024-12-17 15:48 ` [pve-devel] [PATCH v2 storage 02/10] rbd plugin: schema: document default value for 'krbd' setting Fiona Ebner
2024-12-17 15:48 ` [pve-devel] [PATCH v2 storage 03/10] export: redirect stdout to avoid any unrelated messages ending up in the export stream Fiona Ebner
2024-12-17 15:48 ` [pve-devel] [PATCH v2 storage 04/10] rbd plugin: factor out helper to check if volume already exists Fiona Ebner
2024-12-17 15:48 ` [pve-devel] [PATCH v2 storage 05/10] rbd plugin: implement volume import/export Fiona Ebner
2024-12-18 14:20 ` Daniel Kral
2024-12-18 15:14 ` Fiona Ebner
2024-12-18 15:33 ` DERUMIER, Alexandre via pve-devel
2024-12-19 8:56 ` Fiona Ebner [this message]
2024-12-19 10:43 ` DERUMIER, Alexandre via pve-devel
2024-12-17 15:48 ` [pve-devel] [PATCH v2 storage 06/10] iscsi plugin: support volume export Fiona Ebner
2024-12-18 14:05 ` Filip Schauer
2024-12-17 15:48 ` [pve-devel] [PATCH v2 storage 07/10] iscsi direct " Fiona Ebner
2024-12-18 14:07 ` Filip Schauer
2024-12-17 15:48 ` [pve-devel] [RFC v2 storage 08/10] rbd plugin: volume exists helper: distinguish between different errors Fiona Ebner
2024-12-17 15:48 ` [pve-devel] [PATCH v2 storage 09/10] common: introduce common module Fiona Ebner
2024-12-18 9:36 ` Max Carrara
2024-12-18 9:41 ` Fiona Ebner
2024-12-17 15:48 ` [pve-devel] [PATCH v2 storage 10/10] plugins: volume import: align size up to 1KiB Fiona Ebner
2024-12-18 10:34 ` [pve-devel] [PATCH v2 storage 00/10] import/export for shared storages Fiona Ebner
2024-12-18 14:08 ` Aaron Lauterer
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=4907685d-5331-40b1-8630-6ed71b9ff71e@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=d.kral@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