All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sui Chen <suichen6@gmail.com>
To: openbmc@lists.ozlabs.org
Subject: An IPMI Request Visualization Tool
Date: Wed, 13 May 2020 15:38:47 -0700	[thread overview]
Message-ID: <CAFaEeaFTP9v1xZefxzoU9E6h7SpjfbxVrnnSRCmJfJ3QjWRqhA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1183 bytes --]

Hello, OpenBMC Mailing List,

We're working on a GUI tool that allows the user to capture and visualize
BMC IPMI requests.

The tool accepts 2 kinds of inputs:
 1) Load a DBus traffic dump file generated by dbus-monitor on the BMC
 2) Capture IPMI requests on the BMC -- the tool connects to the BMC
console by launching a program of the the user's choice (example: ssh or
telnet), then starts "dbus-monitor" on the BMC and checks its outputs for DBus
calls on the IPMI daemon and then draws the IPMI requests on the canvas
accordingly.

In both ways, this tool operates on data that originate on the BMC (so it's
different from host-side IPMI capture tools.)

The tool makes minimal use of electron.js and should be able to run on
multiple operating systems. We hope this tool might be useful for those who
work on OpenBMC.

What I'm not sure is: do I need to have this accessible on a repo managed
by my Company first so OpenBMC can review it, or can I request to create a
repo for this tool under openbmc-tools now --- provided that OpenBMC is
okay with adding this tool?

A screenshot is attached to illustrate what it does:
[image: scrnshot_compressed.png]


Thanks a lot!

Sui

[-- Attachment #1.2: Type: text/html, Size: 2028 bytes --]

[-- Attachment #2: scrnshot_compressed.png --]
[-- Type: image/png, Size: 36637 bytes --]

             reply	other threads:[~2020-05-13 22:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 22:38 Sui Chen [this message]
2020-05-14 13:57 ` An IPMI Request Visualization Tool Patrick Williams
2020-05-19  1:36   ` Andrew Jeffery
2020-05-21 16:44     ` Sui Chen
2020-05-21 22:39       ` Michael Richardson
2020-05-26 18:22         ` Brandon Wyman
2020-06-03 12:06         ` Andrew Jeffery
2020-06-08  3:07           ` Michael Richardson
2020-06-11  0:57             ` Andrew Jeffery
2020-05-26 18:56       ` Vijay Khemka

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=CAFaEeaFTP9v1xZefxzoU9E6h7SpjfbxVrnnSRCmJfJ3QjWRqhA@mail.gmail.com \
    --to=suichen6@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.