From: Andrei Perapiolkin via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
Subject: [pve-devel] [pve-dev] Storage assisted copy feature for Proxmox storage plugin
Date: Thu, 2 Oct 2025 20:15:34 -0400 [thread overview]
Message-ID: <mailman.625.1759450547.390.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 6871 bytes --]
From: Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: [pve-dev] Storage assisted copy feature for Proxmox storage plugin
Date: Thu, 2 Oct 2025 20:15:34 -0400
Message-ID: <75fcae3c-1112-45f0-b1f9-ff4bdccf0966@open-e.com>
Hi,
Can the honorable community help me find an elegant way for
volume_import to identify the source volume origin type and name?
I’m investigating this to implement storage-assisted copy (i.e.,
performing the volume copy entirely on the storage side).
My initial assumption was that this could be achieved by defining custom
volume_export and volume_import functions.
However, may be there is a better way to do storage assisted copy.
Best regards,
Andrei Perepiolkin
P.S.
Just found out about
https://pve.proxmox.com/wiki/Storage_Plugin_Development:_Writing_a_Storage_Plugin_for_SSHFS
This is grate!
Many thanks for posting this article!
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-10-03 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 0:15 Andrei Perapiolkin via pve-devel [this message]
2025-10-03 6:42 ` Fabian Grünbichler
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=mailman.625.1759450547.390.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=andrei.perepiolkin@open-e.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.