New Feature
GUI integration for the pve-manager 9.2.29+ custom-storage dialog. On a pve-manager that exposes the new /plugins/storage/plugin/<type> API route (shipped in 9.2.29 and later), the Add Storage → TrueNAS and Edit dialogs are now rendered from this plugin's schema instead of the generic fallback. The form is laid out as two columns of fields:
- Nine essentials at the top:
Content,Transport(iscsi / nvme-tcp),TrueNAS host,API key(sensitive),TrueNAS account,Auth mechanism(plain / scram / scram-plus / auto),Parent dataset,iSCSI target IQN,iSCSI discovery portal,NVMe subsystem NQN. - A collapsible Advanced section holding the 23 tuning knobs admins commonly touch (iSCSI portals / CHAP / multipath toggles, NVMe allow-list and DH-CHAP secrets, ZFS compression/sparse/blocksize defaults, snapshot behaviour, debug level, etc.).
- 19 rarely-touched knobs (connection shape, API retry/backoff tunings, the
tn_use_cluster_lockpair, the three#147cross-node reconcile knobs, NVMe kernel tunings) are hidden from the dialog to keep it legible. They remain settable viapvesm set <storage> --<option> <value>or by editing/etc/pve/storage.cfgdirectly.
The API key and the three NVMe/iSCSI secrets (CHAP password, DH-HMAC-CHAP host and controller keys) are marked sensitive — the UI never renders their stored value on edit, and leaving the field empty keeps the stored value.
Every property also carries a title for its field label, so no field falls back to the auto-generated "Tn Api Username" style.
Behaviour Change
$TESTED_APIVER bumped from 16 to 17. pve-manager 9.2.30 advertises APIVER 17, so older plugins log an "older storage API" warning on every load; this bump silences it. No signature changes in the storage API surface the plugin exercises between 16 and 17.
Validation
- Cluster-tested on a 4-node PVE cluster (pve, proxmox2, pvevm1, pve2 — all at
pve-manager9.2.31, kernel 7.0.14-30). After installing the beta deb,pvesh get /plugins/storage/plugin/truenaspluginreturnsorigin: custom,display-name: TrueNAS,x-advanced: 23,x-hidden: 19,sensitive: 4; essentials listed correctly top-level;tn_api_transportrenderedx-hidden=1as expected. - Unit tests:
prove -I t/nvme/lib t/nvme/*.t t/iscsi/*.t— 256/256 pass. - Backwards compatibility: on older
pve-manager(9.2.28 and earlier) the newplugindata()keys are silently ignored; the plugin falls back to the generic storage editor. No regression.
Install
wget https://github.com/truenas/truenas-proxmox-plugin/releases/download/v2.1.25-beta2/truenas-proxmox-plugin_2.1.25.beta2_all.deb
sha256sum -c <(curl -sL https://github.com/truenas/truenas-proxmox-plugin/releases/download/v2.1.25-beta2/SHA256SUMS)
dpkg -i truenas-proxmox-plugin_2.1.25.beta2_all.deb
systemctl restart pvedaemon pveproxy
GitHub renames the asset's ~ to . on upload; the published filename is _2.1.25.beta2_all.deb even though SHA256SUMS lists _2.1.25~beta2_all.deb. The bytes are identical — verify with sha256sum by hand.
Upgrading from 2.1.24: the same postinst fix that 2.1.25~beta1 shipped for #144 still applies. On 2.1.24 and older, upgrade this package from an SSH session rather than the Proxmox Web Shell / Updates > Upgrade button. From 2.1.25 onwards, future upgrades from the Web Shell are safe.