I'll be on vacation starting tomorrow until the 17th of November, so don't
have much time to look at this now. Hopefully Pierre can get to it and
give his opinion before then.
--Renier
[EMAIL PROTECTED] wrote on 11/01/2007 03:59:47
PM:
> Here?s the patch?
>
> Let me know if I made it wrong? or right!
>
> Again, your comments will be greatly appreciated.
>
> (To make is work, don?t forget to look at the differences in
openhpi.conf)
>
> Jean-Michel Audet
> Kontron
>
>
>
>
> De : [EMAIL PROTECTED] [mailto:openhpi-
> [EMAIL PROTECTED] De la part de Renier Morales
> Envoyé : Wednesday, October 31, 2007 5:04 PM
> À : [email protected]
> Objet : Re: [Openhpi-devel] Plug-In
>
>
> [EMAIL PROTECTED] wrote on 10/31/2007 03:45:45
PM:
>
> > What is the version of the SVN that you are using? I have 1.4.2
> > (r22196) from CollabNet.
> >
> > I get the following output when trying to get trunk:
> >
> > svn: PROPFIND request failed on '/svnroot/openhpi/openhpi/trunk'
> > svn: PROPFIND of '/svnroot/openhpi/openhpi/trunk': Could not resolve
> > hostname `openhpi.svn.sourceforge.net': Temporary failure in name
> resolution (
> > https://openhpi.svn.sourceforge.net)
>
> I'm using subversion 1.4.0 (r21228), so probably more of a network
issue.
>
> Can you get to https://openhpi.svn.sourceforge.net on your browser at
least?
> Pinging openhpi.svn.sourceforge.net gives me 66.35.250.145.
>
> --Renier
>
> > I?m used to CVS but SVN is new for me.
> >
> > Jean-Michel Audet
> >
> >
> > De : [EMAIL PROTECTED] [mailto:openhpi-
> > [EMAIL PROTECTED] De la part de Renier Morales
> > Envoyé : Wednesday, October 31, 2007 3:37 PM
> > À : [email protected]
> > Objet : Re: [Openhpi-devel] Plug-In
> >
> >
> > [EMAIL PROTECTED] wrote on 10/31/2007
01:52:05 PM:
> >
> > >
> > > 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.
> >
> > That's great! I will wait to see what Pierre thinks.
> >
> > > 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.
> >
> > This is how I'd like to see the changes. Check out the trunk version
> > of OpenHPI like this:
> > svn co
https://openhpi.svn.sourceforge.net/svnroot/openhpi/openhpi/trunk
> > openhpi-trunk
> >
> > Make/patch the changes you mention there (adding new files and dirs
> > with 'svn add') and send the output of "svn diff" to the list.
> >
> > >
> > > 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).
> >
> > You can. Let's start with you posting the patch so that everyone can
> > review. Then I'll give you devel access to the repository so that
> > you can check the changes in.
> >
> > >
> > > Your comments will be greatly appreciated.
> >
> > This sounds like a very good patch. Thanks again.
> >
> > --Renier
> >
> > >
> > > Let me know!
> > > Jean-Michel Audet
> > > Kontron Canada
> > >
> > > De : [EMAIL PROTECTED] [mailto:openhpi-
> > > [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
> >
-------------------------------------------------------------------------
> > 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[attachment "add_ipmidirect_miniplugins.patch" deleted by
> Renier Morales/Poughkeepsie/IBM]
>
-------------------------------------------------------------------------
> 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
-------------------------------------------------------------------------
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
