Hi,
I just completed the implementation of the IPMI OEM mini plug-ins.
It's a mechanism to add mini plug-ins to the ipmidirect plug-in. It is using
the class cIpmiMcVendorFactory and the mechanism already in place in
ipmi_mc_vendor.cpp. I have recover 100% of the implementation of Force
computer and Intel that was registering board to the mc vendor factory. They
are now (if OK with you), moved out from the ipmidirect plug-in and compile as
a stand-alone OEM IPMI mini plug-in.
In order load the plug-in, the openhpi.conf shall be modified as follow:
In openhpi.conf
## Section for ipmidirect plugin using RMCP:
handler libipmidirect {
entity_root = "{SYSTEM_CHASSIS,7}"
...
ipmi_plugins =
"libipmidirect_kontron,libipmidirect_intel,libipmidirect_force"
}
I would like to know how you want to have the new code. I have:
Made changes on the following files:
- openhpi.conf
- configure.ac
- openhpi/plugins/ipmidirect <-- changes in many files in this
directory.
Added the following files:
- openhpi/plugins/ipmidirect/ipmi_plugin.cpp
- openhpi/plugins/ipmidirect/ipmi_plugin.h
Created the following tree
- openhpi/plugins/ ipmidirect/oem_plugins/*** (Where *** is the
manufacturer name, I have created the folder for kontron, intel and force)
Moved:
- board factory registration and ipmi_mc_vendor_intel.* and
ipmi_mc_vendor_force.* into the oem_plugins vendor folders.
I have created the plug-ins for Force and Intel but I do not have made any
tests. However, I have made no changes to the ipmi_mc_vendor_xxx files.
Kontron will certainly provide fixes and maybe other implementations. Can I
join the developer list? (You may want to wait after this).
Your comments will be greatly appreciated.
Let me know!
Jean-Michel Audet
Kontron Canada
________________________________
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Renier Morales
Envoyé : Monday, October 22, 2007 10:43 AM
À : [email protected]
Objet : Re: [Openhpi-devel] Plug-In
[EMAIL PROTECTED] wrote on 10/19/2007 03:13:28 PM:
> Hi all,
> I have a general question regarding the plug-ins. Is
> there a way to add the OEM specific stuff without modifying the
> OpenHPI direct plug-in? From what I can see in the ATCA and uTCA
> world, it looks like the companies are currently modifying the
> ipmidirect plug-in in order to provide OEM functionalities.
> However, an ATCA chassis can be populate with many vendors blades
> equipped with different IPMI solutions. If each company has their
> own flavor of the ipmidirect plug-in, it is then impossible to have
> a fully integrated solution.
>
> Do I understand it correctly?
>
> Is there any other solution?
>
>
> One of the answers will probably be that the company just has to
> commit the changes into the OpenHPI CVS... but I am not sure that you
> want to pollute the plug-ins with full of OEM stuff (maintenance... etc.).
>
You should take a look at the ipmi plugin in OpenHPI which uses OpenIPMI. Its
purpose is to provide an integrated solution for all ipmi-based hardware. There
are some problems with it as it is not under active development anymore and in
need of testing and code contributions to get it into shape.
To add OEM specific stuff, the ipmi plugin could have its own set of
mini-plugins, each for a specific type of ipmi hardware that contains any OEM
magic stuff. Vendors would only need to provide the mini-plugin.
If you'd like to work on something like this, it would be a real improvement in
OpenHPI's ipmi support.
--Renier
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
