[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
