public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Luca Vornheder <luca@vornheder.cloud>
To: pve-devel@lists.proxmox.com
Cc: Luca Vornheder <luca@vornheder.cloud>
Subject: [PATCH manager 0/3] add opt-in IPMI SEL log tab for nodes
Date: Fri, 18 Sep 2026 18:45:06 +0200	[thread overview]
Message-ID: <20260918164509.46468-1-luca@vornheder.cloud> (raw)

This series adds a per-node, opt-in view of the IPMI System Event Log
(SEL) to the GUI, as requested in
https://bugzilla.proxmox.com/show_bug.cgi?id=7656.

A new 'IPMI' tab next to the system log of a node lists the entries of
the SEL of the node's local BMC, read in-band via 'ipmitool sel elist',
with reload and export buttons. The feature is off by default and is
enabled per node through a new 'ipmi-sel' node option, either in the
node's options in the GUI or with 'pvenode config set --ipmi-sel 1'.
While it is disabled, the API returns 501 and the tab shows a hint
instead of an error.

Design notes / open questions:

* Only the local BMC of the node itself is supported (no remote,
  out-of-band access with stored BMC credentials).
* The endpoint uses the existing Sys.Syslog privilege, like the other
  log endpoints. Enabling the option needs Sys.Modify, as for all node
  options.
* 'ipmitool' is only a Recommends of pve-manager, as the feature is
  opt-in. The GUI marks the feature as technology preview.
* Only reading the log is implemented, there is no way to clear it.
* I did not add documentation to pve-docs yet, I'm happy to do that in
  a follow-up once the general approach is fine.

Tested on a PVE 9.2 node: option toggling in the GUI and via pvenode,
the disabled/enabled behaviour of the tab, and the export. 'make check'
passes, apart from test-ceph-key-migration (2 failing sub-tests in
CephKeyMigrationScript_test.pl), which fails the same way on an
unmodified master and is unrelated to this series.

Luca Vornheder (3):
  api: nodes: add opt-in endpoint to read the local IPMI SEL
  fix #7656: ui: node: add opt-in IPMI SEL log tab
  d/control: recommend ipmitool

 PVE/API2/Nodes.pm                    | 111 ++++++++++++++++++++++
 PVE/NodeConfig.pm                    |   8 ++
 debian/control                       |   3 +-
 www/manager6/Makefile                |   1 +
 www/manager6/node/Config.js          |   9 ++
 www/manager6/node/IPMI.js            | 134 +++++++++++++++++++++++++++
 www/manager6/node/NodeOptionsView.js |  31 +++++++
 7 files changed, 296 insertions(+), 1 deletion(-)
 create mode 100644 www/manager6/node/IPMI.js

-- 
2.50.1 (Apple Git-155)




             reply	other threads:[~2026-09-21  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18 16:45 Luca Vornheder [this message]
2026-09-18 16:45 ` [PATCH manager 1/3] api: nodes: add opt-in endpoint to read the local IPMI SEL Luca Vornheder
2026-09-18 16:45 ` [PATCH manager 2/3] fix #7656: ui: node: add opt-in IPMI SEL log tab Luca Vornheder
2026-09-18 16:45 ` [PATCH manager 3/3] d/control: recommend ipmitool Luca Vornheder

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=20260918164509.46468-1-luca@vornheder.cloud \
    --to=luca@vornheder.cloud \
    --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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal