Add bounded HMC serviceable-event diagnostic snapshots

Open
  • Is something wrong?
#3,539 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
backend-api-design

Research direction

Read docs/design/m4-byo-host.md:168-174 and src/kdive/domain/catalog/resources.py:17-22, then check the prerequisite issues #1817, #1822, and #1824 before starting. The contribution extends the HMC driver after its prerequisite lands; the payload does not name that driver's file or tests. Done means a bounded, read-only event snapshot preserves provenance and distinguishes unsupported, unavailable, empty, and truncated results, with redaction and documented reporting limits; it must not create an allocation veto.

Written by the indexing model from the issue text.

Description

area:control-retrieve effort:S priority:P2 provider:powervm status:blocked type:feature

Problem

The PowerVM diagnostic path needs a bounded snapshot of HMC serviceable hardware events. Generic sensor readings do not establish LPAR health, and event presence must not silently become an allocation veto.

Part of #1814. Follow-up to the capability survey in #1816, explicitly approved for filing and campaign enqueueing. Hardware operations remain held.

Blocked by #1817
Blocked by #1822
Blocked by #1824

Evidence

  • docs/design/m4-byo-host.md:168-174 limits OOB widening to surveyed capabilities with a named caller. The BYO doctor report (#1824) is the caller for this contribution.

  • src/kdive/domain/catalog/resources.py:17-22 currently enumerates local, fault-injection, and remote-libvirt resources; the BYO skeleton and HMC driver are prerequisites, rather than an existing implemented HMC capability.

  • IBM documents lssvcevents -t hardware with managed-system selection and status filtering: https://www.ibm.com/docs/en/power8/9080-MHE?topic=commands-lssvcevents . This is documented command support, not a hardware proof.

Expected

The BYO doctor contribution can request a read-only, bounded serviceable-event snapshot for its configured managed system, preserving event provenance and distinguishing frame-level events from established LPAR relevance. Unsupported, unavailable, empty, and truncated results remain distinguishable. No automatic health or allocation veto is added.

Proposed approach

Extend the existing HMC driver after its prerequisite lands; use fixed supported command selectors, bounded duration/output/event count, structured parsing, deterministic redaction, and diagnostic artifact references. Test command construction, version-dependent/unknown fields, relevance, empty/error/truncation paths, and secret/identifier redaction at the external boundary. Document the supported command/version contract and reporting limitations. Keep this one diagnostic contribution in one PR; no arbitrary command runner, raw sensor promise, event modification, new public MCP tool, or hardware operation is authorized by this tracking issue.

Dominant language
Python
Stars
0
Forks
0
Avg merge
9h 13m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from randomparity/kdive

All issues in randomparity/kdive

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.