From: Gabriel Goller <g.goller@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-manager v3 3/3] permissions: differentiate between zone and fabric paths
Date: Tue, 26 Aug 2025 11:49:54 +0200 [thread overview]
Message-ID: <20250826095000.180173-14-g.goller@proxmox.com> (raw)
In-Reply-To: <20250826095000.180173-1-g.goller@proxmox.com>
With the addition of the fabrics status in the resources, there are
fabrics and zones using the 'sdn' type. The finer distinction between
zones and fabrics is done using the new 'sdn_type' parameter.
Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
---
www/manager6/data/PermPathStore.js | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/www/manager6/data/PermPathStore.js b/www/manager6/data/PermPathStore.js
index c7ec42314c82..8a5344483f0d 100644
--- a/www/manager6/data/PermPathStore.js
+++ b/www/manager6/data/PermPathStore.js
@@ -43,7 +43,14 @@ Ext.define('PVE.data.PermPathStore', {
path = '/vms/' + record.get('vmid');
break;
case 'sdn':
- path = '/sdn/zones/' + record.get('sdn');
+ switch (record.get('sdn_type')) {
+ case 'zone':
+ path = '/sdn/zones/' + record.get('sdn');
+ break;
+ case 'fabric':
+ path = '/sdn/fabrics/' + record.get('sdn');
+ break;
+ }
break;
case 'storage':
path = '/storage/' + record.get('storage');
--
2.47.2
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-08-26 9:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 9:49 [pve-devel] [PATCH manager/network/proxmox{-ve-rs, -perl-rs} v3 00/13] Add fabric status view Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH proxmox-ve-rs v3 1/3] frr: make room for deserialization structs Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH proxmox-ve-rs v3 2/3] frr: add deserialization types for openfabric and ospf Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH proxmox-ve-rs v3 3/3] ve-config: add helper function to iterate over all nodes in all fabrics Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH proxmox-perl-rs v3 1/4] pve: fabrics: update proxmox-frr import path Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH proxmox-perl-rs v3 2/4] fabrics: add function to get status of fabric Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH proxmox-perl-rs v3 3/4] fabrics: add function to get all routes distributed by the fabrics Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH proxmox-perl-rs v3 4/4] fabrics: add function to get all neighbors of the fabric Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH pve-network v3 1/3] fabrics: add fabrics status to SDN::status function Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH pve-network v3 2/3] fabrics: add api endpoint to return fabrics routes Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH pve-network v3 3/3] fabrics: add api endpoint to return fabric neighbors Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH pve-manager v3 1/3] pvestatd: add fabrics status to pvestatd Gabriel Goller
2025-08-26 9:49 ` [pve-devel] [PATCH pve-manager v3 2/3] fabrics: add resource view for fabrics Gabriel Goller
2025-08-26 9:49 ` Gabriel Goller [this message]
2025-09-04 11:42 ` [pve-devel] [PATCH manager/network/proxmox{-ve-rs, -perl-rs} v3 00/13] Add fabric status view Gabriel Goller
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=20250826095000.180173-14-g.goller@proxmox.com \
--to=g.goller@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