From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 57C9B1FF141 for ; Tue, 16 Jun 2026 16:06:35 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 54E94B6EA; Tue, 16 Jun 2026 16:06:33 +0200 (CEST) X-ICL-Out-Info: HUtFAUMEWwJACUgBTUQeDx5WFlZNRAJCTQFMHVkHRQNADlYBXQdLVxQEE0EMRAJfGUtWQQxZDFccVg4CX3cCURxWDVdDVARfUF8cDgRUB10FXVZQAlpLQBMESRMFUgddTVYNRw9YHlwUFxtaQ14IXh9MHB0OWAYSAE0KDjYGWQVeCVYDQwU2EhRdRVoOWwRHFBcbXAAXBlsUBEQDK3RZAkMJQB5ZBFIAXQ05A1waKnZJClUKK3FcBkF4THBUdFhyGVoUXBhTRVEfVEYTGU4bV01QG18CQg8= Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=1a1hai; t=1781617404; x=1784209404; bh=qg/Zhmo/eTa8K4RfK0o20aCc663ahd3dYk/vtBA3QkQ=; h=From:Content-Type:Mime-Version:Subject:Message-Id:Date:To:x-icloud-hme; b=npS4Gk6EIsUJKvUMbVsOfLlZojHBd0D5vkRIjEKvD6LW+Biuvj+wcswC2O8k1F7Mp6apd3b0GjahTEbhQ3PZ2IlKstbB7z3jQ8hAB9EBFMjwr/gmiIbSjEZXTzFRgeRvP7e5snwSEMMit87dRJF/CkEGhX3nPf/yhvTvQtYf/koukHY4m0XHK40ykMYKDpOWu4zOASyHCm9P9C/XFafHuhvo9mVqW1c25Jn9NlpUDCkqRii6lQyiARERl3LUz4tmJ4kPXeDUsS8Z+ab+fqWMl/peRCAb9pbfvf6aMR74XlbwtDcC899cuCBYqVxUsx2F/XtsINPU1qvtRSOKHrNdgQ== From: Krasimir Rangelov Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.600.51.1.1\)) Subject: [RFC] Add read-only DMI hardware endpoint to Proxmox VE Message-Id: <0FC20308-4392-4A01-AD93-9FF741A4C9C3@icloud.com> Date: Tue, 16 Jun 2026 16:43:06 +0300 To: pve-devel@lists.proxmox.com X-Mailer: Apple Mail (2.3864.600.51.1.1) X-Proofpoint-ORIG-GUID: TjOXWVCg3GHeUcj-H-f6mBKzt2_DUhrd X-Proofpoint-Spam-Details-Enc: AW1haW4tMjYwNjE2MDE0MCBTYWx0ZWRfX64X/AWSBePrf x2IG2yuoy8CvEjBz8zGQdwlchT/VG6m6SCOZRRuIHt88TiiU9Ol9XgqYI0ORwshNwU7aYobR4kl 6TuYp70KYy1btHJPJDskms/fOU19OazUX5RAil6jopmVwaOlxz7O+azm3qukc2IedaexgiqAqR6 SLfAxjWX7kVJcdLW882+/r6OiD/4mm7hWRkNzgQx8TZ3josAlGc24cV0e+tBy0V6IlpmfRImIBT Py374zQHLkvU/btgfGbwBUAOdyzjmIu/cfNtSPjNW3O+YwEUYXGrQ54fsiAnxXo/wbTjvivvN3P ID+HxFAmHifqwc1xrXr X-Proofpoint-GUID: TjOXWVCg3GHeUcj-H-f6mBKzt2_DUhrd X-SPAM-LEVEL: Spam detection results: 0 BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy FREEMAIL_ENVFROM_END_DIGIT 1 Envelope-from freemail username ends in digit FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message POISEN_SPAM_PILL 0.1 Meta: its spam POISEN_SPAM_PILL_1 0.1 random spam to be learned in bayes POISEN_SPAM_PILL_3 0.1 random spam to be learned in bayes RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust SPF_HELO_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record X-MailFrom: krasimir.rangelov12@icloud.com X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation Message-ID-Hash: FJCVBCUU2ADBAXHOGTB6DRHKSTWHKO23 X-Message-ID-Hash: FJCVBCUU2ADBAXHOGTB6DRHKSTWHKO23 X-Mailman-Approved-At: Tue, 16 Jun 2026 16:06:32 +0200 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 3.3.10 X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Hello Proxmox developers, > > I would like to propose a small, read-only API extension for Proxmox VE: a new endpoint at GET /nodes/{node}/hardware/dmi. > > The endpoint would expose basic DMI hardware identification data from /sys/devices/virtual/dmi/id/ (for example BIOS vendor/version/date, board vendor/name/serial, chassis details, product name/UUID/serial, and system vendor). The implementation would be protected => 1 so it runs via pvedaemon with sufficient privileges to read sysfs directly, while still requiring Sys.Audit on /nodes/{node}. > > My goal is to provide a standard, documented way to retrieve hardware metadata for asset management, inventory tracking, provisioning, CMDB integration, and reporting. I am reading the data directly from sysfs rather than using dmidecode, since sysfs is faster, avoids parsing, and is available on Linux systems exposing DMI. > > I have prepared a sample implementation as a new module PVE/API2/Hardware/DMI.pm, plus registration in PVE/API2/Hardware.pm. I would appreciate feedback on the API shape, permission model, and whether the endpoint belongs in pve-manager or another repository. > > If this sounds acceptable, I can split it into a small patch series and send it to the list. > > Best regards, > Krasimir Rangelov