From: Joaquin Varela <joaquinvarela@neatech.ar>
To: pve-devel@lists.proxmox.com
Cc: Joaquin Varela <joaquinvarela@neatech.ar>
Subject: [PATCH docs v2 0/5] document ZFS over NVMe/TCP storage
Date: Sun, 2 Aug 2026 00:36:25 -0300 [thread overview]
Message-ID: <cover.1785636981.git.joaquinvarela@neatech.ar> (raw)
Hi,
this is the documentation companion series for the `zfsnvme` backend. It
covers target and initiator setup, native multipath, DH-HMAC-CHAP, lifecycle
semantics, failure policy and the storage schema.
The follow-up patches document target reboot prerequisites, the complete Host
NQN ACL list required for atomic reconstruction, and the cloud-init datasource
hazard on a dedicated target that can see guest `cidata` zvols.
The documentation packages build successfully. The exact branch is:
https://github.com/joaquinv98/pve-docs/tree/submission/zfs-nvme-tcp-rfc-v2
Joaquin Varela (5):
storage: document ZFS over NVMe/TCP backend
storage: harden ZFS over NVMe/TCP guidance
storage: document NVMe all-path loss policy
zfsnvme: document target reboot prerequisites
zfsnvme: document host ACL and cloud-init prerequisites
pve-storage-zfsnvme.adoc | 200 +++++++++++++++++++++++++++++++++++++++
pvesm.adoc | 4 +
2 files changed, 204 insertions(+)
create mode 100644 pve-storage-zfsnvme.adoc
--
2.54.0.windows.1
next reply other threads:[~2026-08-02 3:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 3:36 Joaquin Varela [this message]
2026-08-02 3:36 ` [PATCH docs v2 1/5] storage: document ZFS over NVMe/TCP backend Joaquin Varela
2026-08-02 3:36 ` [PATCH docs v2 2/5] storage: harden ZFS over NVMe/TCP guidance Joaquin Varela
2026-08-02 3:36 ` [PATCH docs v2 3/5] storage: document NVMe all-path loss policy Joaquin Varela
2026-08-02 3:36 ` [PATCH docs v2 4/5] zfsnvme: document target reboot prerequisites Joaquin Varela
2026-08-02 3:36 ` [PATCH docs v2 5/5] zfsnvme: document host ACL and cloud-init prerequisites 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.1785636981.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.