From: Max Schettler via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Max Schettler <max@simplyblock.io>
Subject: [pve-devel] Migration of VM/Container on custom storage type
Date: Tue, 15 Apr 2025 11:55:28 +0200 [thread overview]
Message-ID: <mailman.1000.1744715821.359.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 6088 bytes --]
From: Max Schettler <max@simplyblock.io>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Migration of VM/Container on custom storage type
Date: Tue, 15 Apr 2025 11:55:28 +0200
Message-ID: <48b4f31c-c8dd-44bf-9dc3-3dd478b3bb08@simplyblock.io>
Hi,
I'm developing a Proxmox storage plugin. Trying to use the
high-availability features or migrating VMs/Containers to another
hypervisor in the cluster I get error messages about the storage type
I'm providing not being supported.
Looking at the source, it seems like there is a whitelist of
storagetypes, and no feature check like e.g. for snapshotting. Am I
right to assume there is currently no way of providing a storage backend
that can use this functionality? Are there details beyond this check
that prevent this possibility?
If I am reading the code correctly, are there plans to extend the Plugin
API s.t. it becomes an option? Providing this feature would be an
important addition to our plugin.
Thanks in advance &
kind regards
Max
[-- 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-04-15 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 9:55 Max Schettler via pve-devel [this message]
2025-04-16 8:46 ` 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.1000.1744715821.359.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=max@simplyblock.io \
/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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal