public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Max R. Carrara" <m.carrara@proxmox.com>
To: "Alfonso Kuen" <gerencia@idkmanager.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH common/manager/proxmox-widget-toolkit/storage/storage-plugin-examples v3 00/17] GUI Support for Custom Storage Plugins
Date: Tue, 29 Sep 2026 11:21:52 +0200	[thread overview]
Message-ID: <DLROUQY9CNF4.2YWB25EWOMTF2@proxmox.com> (raw)
In-Reply-To: <179025770001.167092.13101306988170112450@idkmanager.com>

On Thu Sep 24, 2026 at 3:48 PM CEST, Alfonso Kuen wrote:
> Hi Max,
>
> I gave v3 a spin with a real third-party plugin, the TrueNAS storage
> plugin (iSCSI and NVMe/TCP, PVE::Storage::Custom::TrueNASPlugin), on a
> single-node PVE 9.2 test host.
>
> Setup: the 17 patches applied cleanly with git am on pve-common
> 9943f6f, pve-storage 9b5a5a5, proxmox-widget-toolkit 5faa913 and
> pve-manager 122efff2. Building the widget toolkit needed
> proxmox-biome, which is not in pve-no-subscription yet; I built it
> from git.proxmox.com, which in turn needed rustc/cargo from
> trixie-backports (the 1.85 in trixie is too old for one of the
> vendored crates).
>
> On the plugin side I only added a `title` to each of its 46
> properties and an 'advanced-properties' hash (23 tuning knobs) - not a
> line of JavaScript. What I checked:
>
> - The type shows up in Datacenter -> Storage -> Add next to the
>   built-in ones, and the form is built from the schema with the titles.
> - Its four 'sensitive-properties' (API key, CHAP password, two NVMe
>   DH-HMAC-CHAP secrets) render as password fields and show
>   "Unchanged" on edit, never the stored value.
> - The advanced knobs stay behind the Advanced toggle.
> - `fixed` properties are editable on create and display-only on edit.
> - Add and edit round-trip through the API with the secrets ending up
>   in the plugin's /etc/pve/priv files, not in storage.cfg.
>
> I didn't hit any problem with this plugin beyond what Thomas already
> reported.

Amazing, thank you very much for your thorough testing! It's greatly
appreciated.

>
> One thought for later rather than for this series: the next gap for
> a plugin like this one is operational rather than configuration -
> per-volume actions and plugin-specific commands (for us, adopting
> snapshots taken on the array into the guest config). Some way for a
> plugin to declare such actions would round this out nicely.

Thanks for the suggestions! Similar things already exist as ideas in my
head, but I'm not sure how to properly integrate those things for plugin
authors just yet. First step is getting this merged anyhow.

>
> Tested-by: Alfonso Kuen <gerencia@idkmanager.com>
>
> Thanks for the work on this.
>
> Alfonso

Thanks for testing this again!

- Max





      reply	other threads:[~2026-09-29  9:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 14:34 [PATCH common/manager/proxmox-widget-toolkit/storage/storage-plugin-examples v3 00/17] GUI Support for Custom Storage Plugins Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-common v3 01/17] json schema: add multiline string format Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 02/17] api: plugins/storage: add initial routes and endpoints Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 03/17] api: plugins/storage/plugin: include schema in plugin metadata Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 04/17] api: plugins/storage/plugin: mark sensitive properties in schema Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 05/17] api: plugins/storage/plugin: factor plugin metadata code into helper Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 06/17] api: plugins/storage/plugin: add plugins' 'content' to their metadata Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 07/17] all plugins: add 'title' to properties, adapt 'description's Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 08/17] all plugins, api: mark certain properties as advanced in plugindata() Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage v3 09/17] all plugins, api: mark certain properties as hidden " Max R. Carrara
2026-07-27 14:34 ` [PATCH proxmox-widget-toolkit v3 10/17] form: introduce new 'proxmoxtextarea' field Max R. Carrara
2026-07-27 14:34 ` [PATCH proxmox-widget-toolkit v3 11/17] utils: introduce helper function getFieldDefFromPropertySchema Max R. Carrara
2026-07-27 14:34 ` [PATCH proxmox-widget-toolkit v3 12/17] acme: use helper to construct ExtJS fields from property schemas Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-manager v3 13/17] api2: sort modules and API method registrations Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-manager v3 14/17] api: add API routes 'plugins' and 'plugins/storage' Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-manager v3 15/17] ui: storage view: display error when no editor for storage type exists Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-manager v3 16/17] ui: storage: add basic UI integration for custom storage plugins Max R. Carrara
2026-07-27 14:34 ` [PATCH pve-storage-plugin-examples v3 17/17] sshfs: Update SSHFS plugin Max R. Carrara
2026-08-03 11:50 ` [PATCH common/manager/proxmox-widget-toolkit/storage/storage-plugin-examples v3 00/17] GUI Support for Custom Storage Plugins Jakob Klocker
2026-08-03 13:27   ` Jakob Klocker
2026-08-07  9:48   ` Max R. Carrara
2026-08-04 10:40 ` Thomas Ellmenreich
2026-08-07 10:02   ` Max R. Carrara
2026-09-24 13:48 ` Alfonso Kuen
2026-09-29  9:21   ` Max R. Carrara [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=DLROUQY9CNF4.2YWB25EWOMTF2@proxmox.com \
    --to=m.carrara@proxmox.com \
    --cc=gerencia@idkmanager.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal