public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: 蘇國瑋 <nansen.su@sianit.com>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>,
	"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-storage v1 1/2] fix #4929: iscsi: add hidden option to hide storage from UI
Date: Thu, 31 Jul 2025 09:20:40 +0800	[thread overview]
Message-ID: <WC20250731012040.2400D8@sianit.com> (raw)
In-Reply-To: <1753870180.tbicayir20.astroid@yuna.none>



The rationale is for iSCSI multipath configurations. Many users migrating to 
Proxmox have multiple iSCSI storage entries pointing to the same underlying 
storage for redundancy.
These create clutter in the sidebar and don't show useful capacity 
information since they represent the same storage.

The 'hidden' option allows keeping multipath functionality intact while 
hiding redundant entries from the web interface, providing a cleaner 
management experience for enterprise iSCSI multipath setups.


From: Fabian Grünbichler <f.gruenbichler@proxmox.com>
To: "nansen.su" <nansen.su@sianit.com>, Proxmox VE development discussion 
<pve-devel@lists.proxmox.com>
Date: Wed, 30 Jul 2025 12:10:29 +0200
Subject: Re: [pve-devel] [PATCH pve-storage v1 1/2] fix #4929: iscsi: add 
hidden option to hide storage from UI


On July 30, 2025 11:48 am, Thomas Lamprecht wrote:
> Am 30.07.25 um 07:41 schrieb nansen.su:
>>   This patch adds a 'hidden' boolean option to the iSCSI storage plugin.
>>   When enabled, it allows hiding the storage from the resource tree in
>>   the web interface while keeping it functional for actual storage 
operations.
>
> And why should one want that? Can you provide some rationale?

I think the rationale is "hidden" in the bug report - for some setups
you might have N iSCSI storages backing a single shared LVM storage, and
those iSCSI storages pollute the UI view since only the LVM storage on
top is actually relevant for the user/admin in daily operations..
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

      reply	other threads:[~2025-07-31  1:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30  5:40 nansen.su
2025-07-30  9:48 ` Thomas Lamprecht
2025-07-30 10:10   ` Fabian Grünbichler
2025-07-31  1:20     ` 蘇國瑋 [this message]

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=WC20250731012040.2400D8@sianit.com \
    --to=nansen.su@sianit.com \
    --cc=f.gruenbichler@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal