Re: [pve-devel] [PATCH cluster/access-control/guest-common/qemu-server/manager v4] cluster mapping backend

2023-05-26 Thread DERUMIER, Alexandre
Thanks for sharing your progress Dominik. It'll try to retest them with an nvidia mdev vgpu cluster in coming weeks. Le jeudi 25 mai 2023 à 12:17 +0200, Dominik Csapak a écrit : > this series aims to add a cluster-wide device mapping for pci and usb > devices. so that an admin can configure a

[pve-devel] [PATCH docs] cephfs: mention fs-name parameter

2023-05-26 Thread Aaron Lauterer
Signed-off-by: Aaron Lauterer --- pve-storage-cephfs.adoc | 5 + 1 file changed, 5 insertions(+) diff --git a/pve-storage-cephfs.adoc b/pve-storage-cephfs.adoc index c10976b..8d36246 100644 --- a/pve-storage-cephfs.adoc +++ b/pve-storage-cephfs.adoc @@ -34,6 +34,10 @@ Configuration This

[pve-devel] Plan for (invasive) shrink of pve-manager git repository

2023-05-26 Thread Thomas Lamprecht
Hi all! It follows a head's up for the plan of making it easier to work with our pve-manager git repository by rewriting its history to filter out huge artefacts. This will only affect developers, nothing in the current pve-manager Debian package will change. # Background Our current

Re: [pve-devel] [PATCH v4 manager] ui: ceph: improve discoverability of warning details

2023-05-26 Thread Aaron Lauterer
ping? Considering that some users are rather hesitant to upgrade to a major version, it might be a good idea to still get this into Proxmox VE 7 to make it easier for users to discover more details about any issues they experience. On 3/15/23 14:09, Aaron Lauterer wrote: by * replacing the

Re: [pve-devel] [PATCH storage 1/2] rbd: improve handling of missing images

2023-05-26 Thread Aaron Lauterer
ping? ___ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [PATCH manager] ui: ceph: pool: add pool number as column

2023-05-26 Thread Aaron Lauterer
ping? On 3/22/23 10:23, Aaron Lauterer wrote: The pool number is shown in a few places, having it easily accessible can help to understand which pool a warning/error refers to. For example, the PG ID consists of '{pool nr}.{pg nr}' and is shown in every warning concerning that PG.

Re: [pve-devel] [PATCH widget-toolkit] tfa: paperkey: cleanup iframes for printing after window close

2023-05-26 Thread Aaron Lauterer
ping? ___ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Re: [pve-devel] [PATCH common 1/3] fix #3893: network: make bridge vids configurable

2023-05-26 Thread Aaron Lauterer
ping? On 4/13/23 17:10, Aaron Lauterer wrote: For that we need to add a new format option that checks against valid VLAN tags and ranges, for example: 2 4 100-200 The check, if the default value should be used, needs to fail not just when not defined, but also in case it is an empty string.

Re: [pve-devel] [PATCH v2 cluster/guest-common/manager/ha-manager/proxmox{, -perl-rs} 00/42] fix #4156: introduce new notification module

2023-05-26 Thread Lukas Wagner
On 5/24/23 15:56, Lukas Wagner wrote: - Channels: Logically, channel can be thought of as a 'group of endpoints'. Each endpoint can be included in one or more channels. If one is using the notification API to send a notification, a channel has to be specified. The

[pve-devel] [PATCH qemu-server 1/1] api2: add check_bridge_access for create/update vm

2023-05-26 Thread Alexandre Derumier
Signed-off-by: Alexandre Derumier --- PVE/API2/Qemu.pm | 37 - 1 file changed, 36 insertions(+), 1 deletion(-) diff --git a/PVE/API2/Qemu.pm b/PVE/API2/Qemu.pm index 587bb22..ebef93f 100644 --- a/PVE/API2/Qemu.pm +++ b/PVE/API2/Qemu.pm @@ -46,6 +46,12 @@ use

[pve-devel] [PATCH qemu-server 0/1] api2: add check_bridge_access

2023-05-26 Thread Alexandre Derumier
For proxmox 8, following the pve-manager patch serie https://lists.proxmox.com/pipermail/pve-devel/2023-May/056970.html This patch serie add check of permissions for bridge/vnets access (currently only at vm create/update, I'm note sureif they are other places where it should be added) if user

[pve-devel] [PATCH pve-manager 3/4] api2: network: check permissions for local bridges

2023-05-26 Thread Alexandre Derumier
Signed-off-by: Alexandre Derumier --- PVE/API2/Network.pm | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/PVE/API2/Network.pm b/PVE/API2/Network.pm index b3faba1a..ba3b3e0e 100644 --- a/PVE/API2/Network.pm +++ b/PVE/API2/Network.pm @@ -240,22 +240,20 @@

[pve-devel] [PATCH pve-manager 0/4] add vnet/localbridge permissions management

2023-05-26 Thread Alexandre Derumier
Hi, as we has discuted some weeks ago, this patche serie introduce management of acl for vnets && local bridges I have reuse current sdn permissions path, to have common paths /sdn/vnets// where the local vmbr are in a virtual "local" zone /sdn/vnets/local/ Vlans permissions are also handled

[pve-devel] [PATCH pve-manager 1/4] add vnet permissions panel

2023-05-26 Thread Alexandre Derumier
Signed-off-by: Alexandre Derumier --- www/manager6/Makefile| 2 + www/manager6/sdn/Browser.js | 17 +- www/manager6/sdn/VnetACLView.js | 299 +++ www/manager6/sdn/ZoneContentPanel.js | 41 www/manager6/sdn/ZoneContentView.js | 25

[pve-devel] [PATCH pve-manager 4/4] api2: network: check vlan permissions for local bridges

2023-05-26 Thread Alexandre Derumier
We need to display the bridge is the user have a permission on any vlan on the bridge. to avoid to check permissions on 4096 vlans for each bridge (could be slow with a lot of bridges), we first list vlans where acls are defined. (4000 check took 60ms on 10year xeon server, should be enough for

[pve-devel] [PATCH pve-manager 2/4] add permissions management for "local" network zone

2023-05-26 Thread Alexandre Derumier
add a default virtual zone called 'local' in the ressource tree, and handle permissions like a true sdn zone Signed-off-by: Alexandre Derumier --- PVE/API2/Cluster.pm | 12 PVE/API2/Network.pm | 5 +++-- www/manager6/sdn/ZoneContentView.js | 27