From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 12ECA1FF13E for ; Fri, 06 Feb 2026 08:41:48 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 600921FF8D; Fri, 6 Feb 2026 08:42:20 +0100 (CET) Message-ID: <2ad60298-0ed2-467b-9591-7d719b96201d@proxmox.com> Date: Fri, 6 Feb 2026 08:41:45 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Beta Subject: Re: [PATCH manager v2 01/17] api/pvestatd: broadcast and expose non-x86 host architecture To: Dominik Csapak , pve-devel@lists.proxmox.com References: <20260203102118.1430545-1-d.csapak@proxmox.com> <20260203102118.1430545-2-d.csapak@proxmox.com> <4ddfce08-13c5-4d1e-9dc0-fd74d6c22cb5@proxmox.com> <4dffdb37-c01d-45eb-8053-4ec54e847390@proxmox.com> Content-Language: en-US From: Thomas Lamprecht In-Reply-To: <4dffdb37-c01d-45eb-8053-4ec54e847390@proxmox.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1770363627207 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.022 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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: GFMKCBOORBEIBC3MFOZ7S5TGIIN36EWJ X-Message-ID-Hash: GFMKCBOORBEIBC3MFOZ7S5TGIIN36EWJ 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: Am 06.02.26 um 08:25 schrieb Dominik Csapak: > do you also mean that i change the api property from 'architecture' ? > (this seems a bit implied from the code snippet below, but I wanted > to clarify before sending a wrong v3) Might be slightly nicer to have and now it would be still relatively easy. Albeit, should there already be a usage of "architecture" for the node/host arch present in the API, then I have no hard feelings in keeping that term as is here too. btw. I'm fine with only sending the pvestatd patch as new version for now, I can adapt the UI locally and then give some feedback there too – or already (partially) apply it.