From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Dex <dex@fur.lol>
Subject: Re: [pve-devel] PVE Plugin System
Date: Tue, 23 Dec 2025 13:05:47 +0100 [thread overview]
Message-ID: <1766491248.mykdhok069.astroid@yuna.none> (raw)
In-Reply-To: <mailman.163.1766485018.353.pve-devel@lists.proxmox.com>
On December 22, 2025 6:42 pm, Dex via pve-devel wrote:
> Hello,
>
> I'm planning to implement a plugin system for PVE to enable runtime
> loading of third-party code into pve-manager. It would allow loading
> of Perl code for things like creating custom REST endpoints, and
> modifying existing endpoint logic. It would also allow loading of
> Javascript code into the web UI to allow for new UI elements/pages to
> be created. The goal is to provide an way to run/load third party code
> as part of pve-manager instead of needing to modify files in a
> deployment to provide this support.
Thanks for your interest and reaching out!
I don't think such a generic and invasive extension mechanism is
acceptable for us upstream, as it would cause a big support load and has
a huge potential for breakage.
We already have a few extension points/mechanisms which are defined:
- vzdump hook scripts
- guest (lifecycle) hook scripts
- storage plugins
- backup provider plugins
Those all have a specific scope and defined interface, for storage
plugins there are also plans to allow some level of UI integration as
well:
https://lore.proxmox.com/pve-devel/20251121165858.818307-1-m.carrara@proxmox.com/
> I'm looking to implement this system for one of my projects, and was
> curious if you guys would be interested in collaborating on
> implementation details as I work through development, and if there
> would be interest in having a patch submitted to the upstream for
> this.
It would make more sense for us to know what features you are missing
for your particular use case - then we could discuss whether/how those
can be implemented.
Regards,
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-12-23 12:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 17:42 Dex via pve-devel
2025-12-23 12:05 ` 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=1766491248.mykdhok069.astroid@yuna.none \
--to=f.gruenbichler@proxmox.com \
--cc=dex@fur.lol \
--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