Skip to contentSkip to conversation

HP iLO driver

PATCH Martin Knoblauch 4 participants 4 messages Jul 9, 2008

lore
Share & tools
lore
#0 lore raw

----- Original Message ----

Quoted 10 lines

From: "Altobelli, David" <[email protected]>
To: Martin Knoblauch <[email protected]>; Pavel Machek <[email protected]>
Cc: "[email protected]" <[email protected]>; "[email protected]" <[email protected]>
Sent: Wednesday, July 9, 2008 4:47:14 PM
Subject: RE: [PATCH][resubmit] HP iLO driver

Quoted 3 lines · Martin Knoblauch

Somehow I feel the need to step in, as I believe that this thread is really going in the wrong direction.

Quoted 8 lines
Quoted 4 lines

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.

hponcfg - configuration
hpdiags - ???
hp-snmp-agents - ??? Do they provide sensor information? iLO Flash - Firmware upgrade

Quoted 5 lines
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.

OK, so this is really Proliant and likely Blades only? No chance that this will show up elsewhere?

Quoted 9 lines
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.

Quoted 3 lines

Yeah, those are most common. This driver will also surface data through HPSMH or HPSIM, if the proper packages are installed.

Hmm. I am a bit out of touch. What are they doing?

Quoted 11 lines
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_sensors project. But that is a different story.

Quoted 5 lines

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.

I really believe that if the HP-ILO driver is only needed for configuration and FW upgrades, it is OK in the current state. I do not think that anybody really wants to write another hponcfg or iLO-flash.

But if it is also needed to obtain sensor information, your colleagues should really think about supporting the lm_sensors framework.

Cheers
Martin

#1 lore raw
Quoted 5 lines · Martin Knoblauch

hponcfg - configuration
hpdiags - ???
hp-snmp-agents - ??? Do they provide sensor information? iLO Flash - Firmware upgrade

hpdiags and hp-snmp-agents both use this driver to gather basic management processor info, stuff like MP NIC config and stats, serial number, etc (but no sensors).

Quoted 4 lines

OK, so this is really Proliant and likely Blades only? No
chance that this will show up elsewhere?

I know of no plans to use this elsewhere.

Quoted 5 lines
Quoted 3 lines

Yeah, those are most common. This driver will also surface data through HPSMH or HPSIM, if the proper packages are installed.

Hmm. I am a bit out of touch. What are they doing?

HPSMH is "System Management Homepage", and SIM is "Systems Insight Manager". They both are web based management consoles, and show the info gathered by hp-snmp-agents and hpdiags, along with lots of other system info.

Quoted 5 lines

I really believe that if the HP-ILO driver is only needed
for configuration and FW upgrades, it is OK in the current state. I do not think that anybody really wants to write another hponcfg or iLO-flash.

That is true. Even if there was a management processor framework, I would still want a simple read/write interface, to support our existing software.

Quoted 3 lines

But if it is also needed to obtain sensor information, your
colleagues should really think about supporting the lm_sensors framework.

It isn't needed/used for sensor info.

#2 lore raw
Quoted 3 lines

hpdiags and hp-snmp-agents both use this driver to gather basic management processor info, stuff like MP NIC config and stats, serial number, etc (but no sensors).

That all sounds like stuff which should be in sys or proc. That would also give the simple read/write interfaces people want and make it scriptable without random HP tools that may cease to be available some day in the future.

As to supporting old software, well HP decided not to submit the original driver so HP committed to a non upstream API. Thats a hole HP dug and despite the fact people are always warned about it have now fallen down.

Alan

#3 lore raw
In reply to Martin Knoblauch
Quoted 66 lines · On Wed, 9 Jul 2008 08:15:09 -0700 (PDT) Martin Knoblauch wrote:

----- Original Message ----

Quoted 10 lines

From: "Altobelli, David" <[email protected]>
To: Martin Knoblauch <[email protected]>; Pavel Machek <[email protected]>
Cc: "[email protected]" <[email protected]>; "[email protected]" <[email protected]>
Sent: Wednesday, July 9, 2008 4:47:14 PM
Subject: RE: [PATCH][resubmit] HP iLO driver

Quoted 3 lines · Martin Knoblauch

Somehow I feel the need to step in, as I believe that this thread is really going in the wrong direction.

Quoted 8 lines
Quoted 4 lines

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.

hponcfg - configuration
hpdiags - ???
hp-snmp-agents - ??? Do they provide sensor information? iLO Flash - Firmware upgrade

Quoted 5 lines
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.

OK, so this is really Proliant and likely Blades only? No chance that this will show up elsewhere?

Quoted 9 lines
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.

Quoted 3 lines

Yeah, those are most common. This driver will also surface data through HPSMH or HPSIM, if the proper packages are installed.

Hmm. I am a bit out of touch. What are they doing?

Quoted 11 lines
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_sensors project. But that is a different story.

Quoted 5 lines

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.

Quoted 3 lines

I really believe that if the HP-ILO driver is only needed for configuration and FW upgrades, it is OK in the current state. I do not think that anybody really wants to write another hponcfg or iLO-flash.

But if it is also needed to obtain sensor information, your colleagues should really think about supporting the lm_sensors framework.

I use it (hp_ilo driver previous to 2.6.25 nopage changes, from some HP package, not _this_ driver) for scripted power usage readings over the lifetime of a kernel test run. (xml command scripts)

---
~Randy
Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
http://linuxplumbersconf.org/