Re: [Freeipmi-users] Automated testing

[Andy Colson]

On Wed, Feb 7, 2024 at 11:00 PM Al Chu <chu11@llnl.gov> wrote:

> Hi,
>
> > Chassis Controller:  This is the top level thing.  Its got a web interface
> and tells everything else when to power on/off, etc.
>
> I'm not 100% sure if this is a common term, but it could be.  It need not
> be a web interface in my opinion (there's no GUI in FreeIPMI).  I think in 
> general
> you're looking for a IPMI "client" where as the BMC is the "server".  The
> FreeIPMI tools implement the "client side".
>
> > 1) Does this seem like a reasonable setup?
> > 2) Will I be able to use freeipmi for testing, (and hopefully automated
> testing)?
>
> 1 & 2 seems reasonable and FreeIPMI commands should do the job.
>
> > 3) I'm assuming the Chassis Controller keeps the SEL and SDR?  If so then I
> wont be able to test either of those until I get a Chassis Controller,
> right?
>
> By "keep", do you mean "cache"?  The tools ipmi-sel and ipmi-sensor do cache
> the SDR it downloads from the BMC.
>
> > 4) Is it possible for freeipmi to act as a Chassis Controller (of any sort)?
>
> In the sense of "client side" tools, yes.
>
> > 5) If I find some command thats not supported (say a device command that
> bmc-device doesnt have an option for), would ipmi-raw be something I can
> turn to?  Is there a better option?
>
> Yes, ipmi-raw is perfect for that.
>
> Hope that helps,
>
> Al
>
>
Thanks Al.  This is good news.  Yeah, I agree on the web interface, I was
just trying to distinguish things.
We are going to buy a chassis and it'll come with a chassis manager, here
is a picture:

https://i.imgur.com/AsWqQNu.png

I need to emulate the chassis manager.  In this picture, I'm creating the
FRU part.  It's a plugin card (think large graphics card, but it can power
itself on/off, has lots of sensors, etc, etc).

This is a video I watched about SOSA standards:
https://youtu.be/WleNs9ON6Ws?si=r4lMLeWMstK_Vd9t&t=422
It might help explain where I'm comming from.


Another question for you about the bmc-info command.  There are two command
line options:

--driver-address=DRIVER-ADDRESS
--target-slave-address=SLAVE-ADDRESSFR

I'm guessing target-slave-address is the address I've assigned to my custom
hardware, so what is driver-address?

Thanks for all the help,
-Andy