From: Joaquin Varela <joaquinvarela@neatech.ar>
To: pve-devel@lists.proxmox.com
Cc: Joaquin Varela <joaquinvarela@neatech.ar>
Subject: [PATCH manager v2 0/3] add ZFS over NVMe/TCP storage editor
Date: Sun, 2 Aug 2026 00:35:31 -0300 [thread overview]
Message-ID: <cover.1785636980.git.joaquinvarela@neatech.ar> (raw)
Hi,
this is the UI companion series for the `zfsnvme` backend proposed in the
pve-storage series. It registers the new storage type and exposes ZFS,
NVMe/TCP, native multipath and DH-HMAC-CHAP settings.
Since the RFC, the editor gained the optional fast-I/O-fail policy and the
complete cluster Host NQN allow-list needed to reconstruct target ACLs before
publishing a restarted target.
The series passes `make check`; Biome checked 376 files. The exact branch is:
https://github.com/joaquinv98/pve-manager/tree/submission/zfs-nvme-tcp-rfc-v2
Joaquin Varela (3):
ui: add ZFS over NVMe/TCP storage editor
ui: expose NVMe fast I/O fail policy
ui: configure zfsnvme host NQN allow-list
www/manager6/Makefile | 1 +
www/manager6/Utils.js | 6 +
www/manager6/storage/ZFSNVMeEdit.js | 164 ++++++++++++++++++++++++++++
3 files changed, 171 insertions(+)
create mode 100644 www/manager6/storage/ZFSNVMeEdit.js
--
2.54.0.windows.1
next reply other threads:[~2026-08-02 3:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 3:35 Joaquin Varela [this message]
2026-08-02 3:35 ` [PATCH manager v2 1/3] ui: add ZFS over NVMe/TCP storage editor Joaquin Varela
2026-08-02 3:35 ` [PATCH manager v2 2/3] ui: expose NVMe fast I/O fail policy Joaquin Varela
2026-08-02 3:35 ` [PATCH manager v2 3/3] ui: configure zfsnvme host NQN allow-list Joaquin Varela
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=cover.1785636980.git.joaquinvarela@neatech.ar \
--to=joaquinvarela@neatech.ar \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.