From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Max Schettler <max@simplyblock.io>
Subject: Re: [pve-devel] Migration of VM/Container on custom storage type
Date: Wed, 16 Apr 2025 10:46:39 +0200 (CEST) [thread overview]
Message-ID: <1964246391.2072.1744793199860@webmail.proxmox.com> (raw)
In-Reply-To: <mailman.1000.1744715821.359.pve-devel@lists.proxmox.com>
> Max Schettler via pve-devel <pve-devel@lists.proxmox.com> hat am 15.04.2025 11:55 CEST geschrieben:
> 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.
Hi! thanks for reaching out!
out of interest, what is the storage plugin for?
in general it always helps to provide a bit of detail and to include all
error messages. I made an educated guess below what your issue is, if it
is not correct, please just add more details and I am sure we can figure
it out.
> 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?
at the moment there is a list of shared storage types in PVE::Storage::Plugin
that is used to set the shared flag on the storage instance (which in turn
makes migrations ignore volumes there since a storage being shared means its
volumes have identical content on all nodes where the storage is available).
the only option at the moment is to add your type to that list (it is shared
state across all plugins, so any plugin can do so).
> 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.
I think we will switch to just making this a property of the plugin in a
declarative fashion as part of revamping the plugin interface, but that has
not happened yet, so for now the only option to add a new shared plugin is
to push to that list.
you might be interested Max (still open/iterated upon) series documenting
and improving the plugin interface:
https://lore.proxmox.com/pve-devel/20250326142059.261938-1-m.carrara@proxmox.com/
while some parts are still in flux there, it should give some missing details!
Fabian
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-04-16 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 9:55 Max Schettler via pve-devel
2025-04-16 8:46 ` Fabian Grünbichler [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=1964246391.2072.1744793199860@webmail.proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=max@simplyblock.io \
--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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal