From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH v3 manager 17/18] ui: san: show that a namespace uses native multipath
Date: Sun, 22 Nov 2026 02:25:54 +0100 [thread overview]
Message-ID: <20261122012605.1848824-18-t.lamprecht@proxmox.com> (raw)
In-Reply-To: <20261122012605.1848824-1-t.lamprecht@proxmox.com>
The cluster-wide status lists the namespaces of NVMe over Fabrics
storages too. They use the native multipath of the kernel, with
neither an entry nor a storage that requests a map, so the Multipath
column would call them unmanaged. Show "Native" for them, as the LUN
list of a node does, and name them as namespaces in Paths by Node.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
---
www/manager6/dc/SAN.js | 16 ++++++++++++++--
www/manager6/window/SANLunState.js | 8 ++++----
2 files changed, 18 insertions(+), 6 deletions(-)
diff --git a/www/manager6/dc/SAN.js b/www/manager6/dc/SAN.js
index e30b5ef48..fdf2935bf 100644
--- a/www/manager6/dc/SAN.js
+++ b/www/manager6/dc/SAN.js
@@ -15,6 +15,7 @@ Ext.define('pve-san-status', {
'name',
'explicit',
'multipath-storage',
+ 'native',
'nodes',
'size',
'used-by-storage',
@@ -118,6 +119,7 @@ Ext.define('PVE.dc.SANView', {
Ext.create('PVE.window.SANLunState', {
wwid: rec.get('wwid'),
name: rec.get('name'),
+ nvme: !!rec.get('native'),
autoShow: true,
});
let setupItem = (type) => ({
@@ -258,7 +260,11 @@ Ext.define('PVE.dc.SANView', {
disabled: !canModify,
handler: function (button) {
let lun = button.up('grid').getSelection()[0];
- let wwid = lun?.get('explicit') ? undefined : lun?.get('wwid');
+ // a namespace uses native multipath, which takes no entry
+ let wwid =
+ lun?.get('explicit') || lun?.get('native')
+ ? undefined
+ : lun?.get('wwid');
edit({ wwid, isCreate: true });
},
},
@@ -381,7 +387,13 @@ Ext.define('PVE.dc.SANView', {
width: 170,
renderer: (value, md, rec) => {
let storage = rec.get('multipath-storage');
- let kind = value ? 'manual' : storage ? 'storage' : 'unmanaged';
+ let kind = rec.get('native')
+ ? 'native'
+ : value
+ ? 'manual'
+ : storage
+ ? 'storage'
+ : 'unmanaged';
return Ext.htmlEncode(PVE.SANUtils.multipathText(kind, storage));
},
},
diff --git a/www/manager6/window/SANLunState.js b/www/manager6/window/SANLunState.js
index 5dfce247a..f84940fd8 100644
--- a/www/manager6/window/SANLunState.js
+++ b/www/manager6/window/SANLunState.js
@@ -23,12 +23,12 @@ Ext.define('PVE.window.SANLunState', {
let title = me.nvme
? gettext('Storage {0}: Namespace State')
: gettext('Storage {0}: LUN State');
+ let pathsTitle = me.nvme
+ ? gettext('Namespace {0}: Paths by Node')
+ : gettext('LUN {0}: Paths by Node');
me.title = me.storage
? Ext.String.format(title, me.storage)
- : Ext.String.format(
- gettext('LUN {0}: Paths by Node'),
- Ext.htmlEncode(me.name || me.wwid),
- );
+ : Ext.String.format(pathsTitle, Ext.htmlEncode(me.name || me.wwid));
// The other nodes set up the LUN of a new storage with their next status updates.
let pendingUntil = me.storage ? Date.now() + 60000 : 0;
let rstore = Ext.create('Proxmox.data.UpdateStore', {
next prev parent reply other threads:[~2026-11-22 1:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-22 1:25 [PATCH v3 storage,docs,manager 00/18] NVMe over Fabrics storage Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 storage 01/18] diskmanage: skip SMART queries for NVMe fabric namespaces Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 storage 02/18] nvmeof: add a storage for NVMe over Fabrics subsystems Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 storage 03/18] lvm: allow a volume group on an NVMe over Fabrics namespace Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 storage 04/18] api: scan: add NVMe over Fabrics discovery Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 storage 05/18] pvesm: add a scan command for NVMe over Fabrics Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 storage 06/18] api: san luns: attribute NVMe namespaces to storage Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 storage 07/18] api: add node-level NVMe over Fabrics status and controller removal Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 storage 08/18] multipath: report the NVMe host NQN of each node Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 storage 09/18] multipath: report NVMe over Fabrics namespaces in the cluster status Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 docs 10/18] storage: document NVMe over Fabrics storages Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 manager 11/18] report: add the NVMe over Fabrics host NQN and subsystems Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 manager 12/18] ui: storage: add NVMe over Fabrics storage Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 manager 13/18] ui: lvm: offer NVMe over Fabrics storages as base storage Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 manager 14/18] ui: storage: add a guided setup for shared LVM on NVMe over Fabrics Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 manager 15/18] ui: node san: list NVMe over Fabrics controllers Thomas Lamprecht
2026-11-22 1:25 ` [PATCH v3 manager 16/18] ui: san: show the NVMe host NQN of each node Thomas Lamprecht
2026-11-22 1:25 ` Thomas Lamprecht [this message]
2026-11-22 1:25 ` [PATCH v3 manager 18/18] pvestatd: notify on NVMe over Fabrics namespaces as on multipath maps Thomas Lamprecht
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=20261122012605.1848824-18-t.lamprecht@proxmox.com \
--to=t.lamprecht@proxmox.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