From: Fiona Ebner <f.ebner@proxmox.com>
To: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>,
pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-manager v4 17/17] RFC: ui: group custom CPU with resource mappings
Date: Mon, 11 May 2026 16:01:14 +0200 [thread overview]
Message-ID: <16ff735e-97a3-4edf-b0eb-05f1004b4383@proxmox.com> (raw)
In-Reply-To: <20260430160109.565536-18-a.bied-charreton@proxmox.com>
Am 30.04.26 um 6:02 PM schrieb Arthur Bied-Charreton:
> As suggested by Fiona on the list [0], create a
> "Guest Resources/Hardware" group with "Custom CPU models", "Directory
> Mappings", and "Resource Mappings" in the Datacenter menu.
>
> [0]
> https://lore.proxmox.com/pve-devel/b9274cb9-0ae1-46aa-a4b5-e10251c1a948@proxmox.com/T/#u
>
> Suggested-by: Fiona Ebner <f.ebner@proxmox.com>
> Signed-off-by: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
With my single comment addressed:
Reviewed-by: Fiona Ebner <f.ebner@proxmox.com>
> ---
> www/manager6/dc/Config.js | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/www/manager6/dc/Config.js b/www/manager6/dc/Config.js
> index ad830ba8..119aba18 100644
> --- a/www/manager6/dc/Config.js
> +++ b/www/manager6/dc/Config.js
> @@ -379,6 +379,21 @@ Ext.define('PVE.dc.Config', {
> );
> }
>
> + if (
> + caps.mapping['Mapping.Audit'] ||
> + caps.mapping['Mapping.Use'] ||
> + caps.mapping['Mapping.Modify'] ||
> + caps.dc['Sys.Audit']
> + ) {
> + me.items.push({
> + xtype: 'pveGuestResourcesAndHardwareView',
That xtype does not exist
> + title: gettext('Guest Resources/Hardware'),
> + iconCls: 'fa fa-sitemap',
> + itemId: 'guestresourcesandhardware',
> + expandedOnInit: true,
> + });
> + }
> +
> if (
> caps.mapping['Mapping.Audit'] ||
> caps.mapping['Mapping.Use'] ||
next prev parent reply other threads:[~2026-05-11 14:01 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 16:00 [PATCH docs/manager/qemu-server v4 00/17] Add API and UI for custom CPU models Arthur Bied-Charreton
2026-04-30 16:00 ` [PATCH pve-docs v4 01/17] qm: add anchor to "CPU Type" section Arthur Bied-Charreton
2026-05-07 10:34 ` Fiona Ebner
2026-04-30 16:00 ` [PATCH qemu-server v4 02/17] cpu config: rename CPU models config path variable Arthur Bied-Charreton
2026-05-07 10:57 ` Fiona Ebner
2026-04-30 16:00 ` [PATCH qemu-server v4 03/17] cpu flags: move cpu flags-related utilities to their own module Arthur Bied-Charreton
2026-05-07 11:15 ` Fiona Ebner
2026-04-30 16:00 ` [PATCH qemu-server v4 04/17] cpu flags: add helper querying CPU flags with nodes supporting them Arthur Bied-Charreton
2026-05-07 11:57 ` Fiona Ebner
2026-04-30 16:00 ` [PATCH qemu-server v4 05/17] cpu config: add helpers to lock and write config Arthur Bied-Charreton
2026-05-07 12:06 ` Fiona Ebner
2026-04-30 16:00 ` [PATCH qemu-server v4 06/17] cpu: register standard option for CPU format Arthur Bied-Charreton
2026-05-07 12:11 ` Fiona Ebner
2026-05-07 14:01 ` Arthur Bied-Charreton
2026-05-07 14:08 ` Fiona Ebner
2026-05-08 6:40 ` Arthur Bied-Charreton
2026-04-30 16:00 ` [PATCH qemu-server v4 07/17] cpu config: set 'type' field before writing Arthur Bied-Charreton
2026-05-07 12:24 ` Fiona Ebner
2026-05-08 7:48 ` Arthur Bied-Charreton
2026-04-30 16:01 ` [PATCH qemu-server v4 08/17] cpu flags: improve flags list returned by endpoint Arthur Bied-Charreton
2026-05-07 13:10 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 09/17] api: add endpoint querying available CPU flags cluster-wide Arthur Bied-Charreton
2026-05-07 13:29 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 10/17] api: add CRUD handlers for custom CPU models Arthur Bied-Charreton
2026-05-07 14:02 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 11/17] ui: cpu model selector: allow filtering out custom models Arthur Bied-Charreton
2026-05-11 8:53 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 12/17] ui: add basic custom CPU model editor Arthur Bied-Charreton
2026-05-11 9:27 ` Fiona Ebner
2026-05-11 13:52 ` Arthur Bied-Charreton
2026-04-30 16:01 ` [PATCH pve-manager v4 13/17] ui: cpu flags selector: add CPU flag editor for custom models Arthur Bied-Charreton
2026-05-11 11:35 ` Fiona Ebner
2026-05-11 14:14 ` Arthur Bied-Charreton
2026-04-30 16:01 ` [PATCH pve-manager v4 14/17] ui: cpu flags selector: fix buffered rendering error Arthur Bied-Charreton
2026-05-11 13:36 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 15/17] ui: cpu flags selector: allow filtering out flags supported on 0 nodes Arthur Bied-Charreton
2026-05-11 13:40 ` Fiona Ebner
2026-05-11 13:42 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 16/17] ui: cpu flags selector: add search bar for large lists of flags Arthur Bied-Charreton
2026-05-11 13:56 ` Fiona Ebner
2026-04-30 16:01 ` [PATCH pve-manager v4 17/17] RFC: ui: group custom CPU with resource mappings Arthur Bied-Charreton
2026-05-11 14:01 ` Fiona Ebner [this message]
2026-05-06 14:31 ` [PATCH docs/manager/qemu-server v4 00/17] Add API and UI for custom CPU models David Riley
2026-05-07 7:14 ` Arthur Bied-Charreton
2026-05-11 10:42 ` Fiona Ebner
2026-05-11 14:16 ` Arthur Bied-Charreton
2026-05-12 8:11 ` Arthur Bied-Charreton
2026-05-12 8:50 ` Fiona Ebner
2026-05-12 9:00 ` Arthur Bied-Charreton
2026-05-11 14:08 ` Fiona Ebner
2026-05-11 14:21 ` Arthur Bied-Charreton
2026-05-15 9:30 ` superseded: " Arthur Bied-Charreton
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=16ff735e-97a3-4edf-b0eb-05f1004b4383@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=a.bied-charreton@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