HP iLO driver
----- Original Message ----
Quoted 32 lines
From: Pavel Machek <[email protected]>
To: "Altobelli, David" <[email protected]>
Cc: "[email protected]" <[email protected]>; "[email protected]" <[email protected]>
Sent: Wednesday, July 9, 2008 1:08:50 AM
Subject: Re: [PATCH][resubmit] HP iLO driverQuoted 6 lines · David
Quoted 2 lines · Pavel Machek
Could you provide the list of commands (at least) so we can be more concrete?
Unfortunately, I don't believe that I can. We reviewed this internally, and the question of documentation was raised. The hardware teams
You could at least provide list of high-level functionality.
Quoted 4 lines
Quoted 2 lines
(I assume management processors have pretty similar functionality accross vendors, right?)
I can't speak for other vendors.
And neither can they speak, because you did not tell us what the iLO does.
Quoted 8 lines
Quoted 7 lines
Quoted 4 lines
It seems much cleaner to keep the kernel interface simple and opaque (ie read/write), and handle the details of the commands in user space. From my limited understanding, I thought that was a common goal here: move what you can to userspace.
We are not _that_ extreme. Yes, keep stuff in userspace is important, but "hide hardware differences" is more important goal.
Quoted 6 lines
Quoted 3 lines
That seems like a larger question/goal. Giving users some consistent interfaces to do stuff would be nice, but I'd really like to handle this driver on its own.
This driver can't be handled on its own, that would lead to a mess in future. Sorry. We need more info here.
Somehow I feel the need to step in, as I believe that this thread is really going in the wrong direction.
It is true that David (or HP) definitely could have done a better job in describing why this driver is needed and what HP-Utilities are depending on it. This might have lead some people to misinterpret what ILO is about.
ILO (Q: does HP still sell RILOE boards and are they supporten by the driver?) is a command processor that allows *external* administration (Power control, Rebooting, Remote Console, ..) of certain HP (and HP only) products. For this it provides a separate NIC and a separate serial connector. Access is completely independant of an OS running on the server. This HP-ILO has nothing to do with that functionality.
ILO can be configured either offline (server OS shut down), or via the external interfaces, or from a running OS via some HP provided utilities. For this a driver is needed, and that is what we are talking about. From my experience as an administrator of HP Proliant systems the only local uses for the *internal* ILO interface is to set-up the thing, and to do firmware upgrades.
To obtain sensor data locally there are other ways, which do not need the ILO kernel driver (hplog together with hpasmd, which unfortunately are closed source). So , unless the HP-ILO driver is just a replacement of the old "cpqci" driver, there is no need to pester David on functionality. If, of course the HP-ILO driver is needed to get to the hpasm/hplog functionality (no driver was needed so far) the story might be different. But then HP should provide the specs for the Proliant sensor interface anyway and work together with the lm_sensors project. But that is a different story.
Cheers
Martin
Quoted 7 lines · Martin Knoblauch
Somehow I feel the need to step in, as I believe that this thread is really going in the wrong direction.
It is true that David (or HP) definitely could have done a better job in describing why this driver is needed and what HP-Utilities are depending on it. This might have lead some people to misinterpret what ILO is about.
I'm sorry about that. This driver is needed for tools like:
hponcfg, hpdiags, hp-snmp-agents, and iLO flash utilities.
Quoted 2 lines
ILO (Q: does HP still sell RILOE boards and are they supporten by the driver?) is a command processor that allows
RILOE cards are not sold any more, and are not supported by this driver.
Quoted 8 lines
ILO can be configured either offline (server OS shut down), or via the external interfaces, or from a running OS via some HP provided utilities. For this a driver is needed, and that is what we are talking about. From my experience as an administrator of HP Proliant systems the only local uses for the *internal* ILO interface is to set-up the thing, and to do firmware upgrades.
Yeah, those are most common. This driver will also surface data through HPSMH or HPSIM, if the proper packages are installed.
Quoted 10 lines
To obtain sensor data locally there are other ways, which do not need the ILO kernel driver (hplog together with hpasmd, which unfortunately are closed source). So , unless the HP-ILO driver is just a replacement of the old "cpqci" driver, there is no need to pester David on functionality. If, of course the HP-ILO driver is needed to get to the hpasm/hplog functionality (no driver was needed so far) the story might be different. But then HP should provide the specs for the Proliant sensor interface anyway and work together with the
lm_sensorsproject. But that is a different story.
This is a replacement for cpqci, which was released in the "hprsm" package, and later replaced by the "hp-ilo" package. The former package was not GPL, the latter is.
I rewrote the driver to make it (hopefully) more palatable, in terms of both style and functionality.