From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id E7C671FF0C0 for ; Wed, 18 Nov 2026 07:57:42 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 5223D21A56; Wed, 18 Nov 2026 07:54:14 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com Subject: [PATCH v6 manager 42/42] ui: node: san: add a column for the iSCSI target of a LUN Date: Wed, 18 Nov 2026 07:52:59 +0100 Message-ID: <20261118065302.3033937-43-t.lamprecht@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261118065302.3033937-1-t.lamprecht@proxmox.com> References: <20261118065302.3033937-1-t.lamprecht@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794984789568 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.178 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: YPYISE4ZUFST3G3HKOSZP4NZP7P3PJDL X-Message-ID-Hash: YPYISE4ZUFST3G3HKOSZP4NZP7P3PJDL X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: The inventory reports the target a LUN is attached through, but the list did not show it. The name tells where a LUN comes from, which helps most with an array or a storage plugin that exports one target per volume and names it after that volume. Hidden by default, the search covers it either way. Signed-off-by: Thomas Lamprecht --- www/manager6/node/SANLuns.js | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/www/manager6/node/SANLuns.js b/www/manager6/node/SANLuns.js index e55bdf1bd..2c55ba23f 100644 --- a/www/manager6/node/SANLuns.js +++ b/www/manager6/node/SANLuns.js @@ -96,6 +96,13 @@ Ext.define('PVE.node.SANLunList', { width: 100, renderer: PVE.SANUtils.renderSanTransport, }, + { + text: gettext('Target'), + dataIndex: 'iscsi-target', + flex: 2, + hidden: true, + renderer: Ext.htmlEncode, + }, { text: 'LUN', dataIndex: 'iscsi-lun', width: 60, hidden: true }, { text: gettext('Vendor'), @@ -191,6 +198,7 @@ Ext.define('PVE.node.SANLunList', { 'detail', 'multipath-storage', 'devpath', + 'iscsi-target', 'path-search', 'vendor', 'model',