Sorry for the wide distribution, but I'm looking for possible options to add new interface support for x86 platform. I wasn't really into ipmitool-devel committee that much, so could someone suggest what's the right way to start off? Is there any one from intel in this committee? Lifu > To: ipmitool-devel@lists.sourceforge.net > From: jm...@hp.com > Date: Tue, 4 Aug 2015 16:33:45 -0600 > Subject: Re: [Ipmitool-devel] Some news > > Dmitry, > > I think the project continues to move forward because people like > yourself and many others use and continue to contribute to it. The speed > of change for ipmitool is a function of the number of active ipmitool > developers and their available time to work on ipmitool. SInce I've > been involved I don't recall ever having more than 2 developers at any > one time, so change comes about very slowly. > > I can't really comment on whether or not system admins are switching > from ipmitool to other tools, but I do know that the Linux vendors > continue to package ipmitool into their releases and there are still > applications, old and new, which still rely use ipmitool today > (OpenStack Ironic for example). Certainly there are other ipmi > alternatives available in the open source community, so you do have a > choice. > > The actual testing of ipmitool at a release is simply myself running a > set of simple tests on whatever HP platforms I happen have available > when it's time to release. I do request via the ipmitool dev alias > that people please do testing prior to the release, but to be honest no > one has ever done this to my knowledge. There is no automated > ipmitool testing. > > I do know that some of the Linux vendors do their own testing prior to > integration of a new version of ipmitool into their release bundles, and > products with dependencies on ipmitool tend to pick up new releases and > do their own testing based on their own release schedules. It has > always been my assumption (right or wrong) that when an OEM contributes > code, it is their responsibility to do testing and provide bug fixes > based on their testing. When a new release of ipmitool is made > available, all we can do is hope that individual OEMs test the new > release and provide feedback via the developer email alias or ipmitool > bug tracker. > > There really isn't a lot of refactoring that goes on simply because > there is no easy way to test everything. When I first got involved > in ipmitool, I made pretty significant changes that were very difficult > to get adequately tested. We released with my changes and as time > when on, folks found issues and I fixed problems as they came in. I > think this is the best we can do. > > Thanks for your help and contributions and your statement of support for > generic PICMG/VITA testing > > Jim > > On 8/4/2015 12:51 PM, Dmitry Bazhenov wrote: > > Hello, Jim, > > > > Thank you for answering. > > > > Could you please comment on whether you think the project is more alive > > than dead, > > or the vast majority of system administrators are switching to ipmiutil > > or something else? > > > > I'm asking because we've been using ipmitool for a long time, we did > > some input into it > > to satisfy our needs, but the project activity makes its future dim. > > > > Could you also comment on whether the ipmitool releases undergo some > > release testing? > > > > There is (among other) a lot of OEM-specific stuff in the utility which > > obviously can be tested > > only by those who possess the corresponding hardware, and which can be > > broken > > when the utility code is re-factored. > > Do OEM vendors offer help for testing OEM-specific things? > > > > By the way, I personally offer my support for testing generic PICMG/VITA > > functionality for release purposes. > > > > Regards, > > Dmitry > > > > 04.08.2015 22:39, Jim Mankovich пишет: > >> Dmitry, > >> > >> I've been doing the packaging and releases of ipmitool as necessary, but > >> we need one or more people who can spare the time to actively merge > >> contributed patches and bug fixes into the tool. I can continue to > >> do packaging and releases and I'll continue to help out where I can with > >> bug fixes and features as well, but the time I can contribute is > >> limited. Since I've been involved in ipmitool, Zdenek has been the > >> main person driving all the reported bug fixes and features into the > >> mainline (and this has been very much appreciated). Thanks for all > >> your effort Zdenek! > >> > >> Thanks, > >> Jim > >> > >> On 7/31/2015 10:43 PM, Dmitry Bazhenov wrote: > >>> Hello, Zdenek, > >>> > >>> We very appreciate your effort giving that you do this without any > >>> payment and in your free time. > >>> Could you please comment whether someone except you is going to maintain > >>> ipmitool and > >>> do releases? > >>> We, at PigeonPoint, have intentions to continue to provide fixes and new > >>> features (especially > >>> related to PICMG and VITA-based systems) into the source tree, but we > >>> certainly depend on > >>> someone who would help us to integrate them. > >>> > >>> Regards, > >>> Dmitry > >>> 01.08.2015 9:35, Zdenek Styblik пишет: > >>>> Hello all, > >>>> > >>>> my apologies for some quiet period and no new releases in quite some > >>>> time(almost a year). I was busy. > >>>> I'm back now, although probably for only a brief period of time. > >>>> During last couple months I've realized I should/want/have to(depends > >>>> on point of view) pay attention to other things in my free time. > >>>> Therefore, I can't do this in my free time any more, because I have > >>>> only so much of free time. However, I'll try to finish up whatever > >>>> I've started or promised to help with. > >>>> > >>>> Thank you and have a nice weekend. > >>>> > >>>> Best regards, > >>>> Z. > >>>> > >>>> ------------------------------------------------------------------------------ > >>>> _______________________________________________ > >>>> Ipmitool-devel mailing list > >>>> Ipmitool-devel@lists.sourceforge.net > >>>> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel > >>> ------------------------------------------------------------------------------ > >>> _______________________________________________ > >>> Ipmitool-devel mailing list > >>> Ipmitool-devel@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel > >> ------------------------------------------------------------------------------ > >> _______________________________________________ > >> Ipmitool-devel mailing list > >> Ipmitool-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/ipmitool-devel > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Ipmitool-devel mailing list > > Ipmitool-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/ipmitool-devel > > ------------------------------------------------------------------------------ > _______________________________________________ > Ipmitool-devel mailing list > Ipmitool-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
------------------------------------------------------------------------------
_______________________________________________ Ipmitool-devel mailing list Ipmitool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ipmitool-devel
