We only have a few open items that I think should be resolved before releasing 2.7.3. The list grew a bit in the past week, but we'll cover that later. Here is the list: * #93: Devices Dumps Library improvements <https://github.com/networkupstools/nut/issues/93> * #158: Powerware BCMXCP advanced features <https://github.com/networkupstools/nut/pull/158> * #185: insecure storage of password in nut-monitor favorites file <https://github.com/networkupstools/nut/issues/185> * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM <https://github.com/networkupstools/nut/issues/187> * #190: upsd: NSS SSL only working in debug mode <https://github.com/networkupstools/nut/issues/190> * eaton_epdus branch: <https://github.com/networkupstools/nut/tree/eaton-epdus> Most of these are from the GitHub 2.7.3 milestone: https://github.com/networkupstools/nut/issues?q=milestone%3A2.7.3 #93: The scope of this issue is a bit broad (encompassing a Gen3 dummy-ups driver, etc) but for 2.7.3, I think we can call this closed, so long as there are no issues pushing this to www.networkupstools.org. The current auto-generated DDL is here: http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/ #158: I will rebase the commits, and replace the author's email address with the GitHub username at noreply address, but if someone has additional Powerware-based UPSes to test, that would be handy. #185: Debian patch is on a branch; I will bump the version number and merge. #187: This is a driver-specfic fix, but I haven't had time to work through the logic from the vendor driver. This is not listed on the GitHub 2.7.3 milestone - should it be? #190 is a bit more complicated. We are still in the initial investigation stage, but it seems that this may have crept past the Ubuntu automated test suite. Running in the foreground is a bit of an ugly hack, but if it works with the Ubuntu init scripts... I'll let Arno cover the eaton_epdus branch. Also driver-specific (snmp-ups), so should not affect the rest of NUT. (Is this the same as issue #188? <https://github.com/networkupstools/nut/issues/188> ) Glad to hear that Arno will have more time to work on NUT again! -- Charles Lepple clepple at gmail
Hi, There is one issue that I would consider as a major issue and not fixed yet. It is the use of wall time for scheduling ups polls instead of a monotonic clock source. I provided a (partial) patch in the past and I believe there was some work on it. The bug manifests itself as a stop of monitoring with no alarm when the clock is moved backwards in time. Please consider adding this to the release. Cheers, Baruch On Wed, Mar 4, 2015 at 4:04 PM, Charles Lepple <clepple at gmail.com> wrote:> We only have a few open items that I think should be resolved before > releasing 2.7.3. The list grew a bit in the past week, but we'll cover that > later. Here is the list: > > * #93: Devices Dumps Library improvements < > https://github.com/networkupstools/nut/issues/93> > * #158: Powerware BCMXCP advanced features < > https://github.com/networkupstools/nut/pull/158> > * #185: insecure storage of password in nut-monitor favorites file < > https://github.com/networkupstools/nut/issues/185> > * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM < > https://github.com/networkupstools/nut/issues/187> > * #190: upsd: NSS SSL only working in debug mode < > https://github.com/networkupstools/nut/issues/190> > * eaton_epdus branch: < > https://github.com/networkupstools/nut/tree/eaton-epdus> > > Most of these are from the GitHub 2.7.3 milestone: > https://github.com/networkupstools/nut/issues?q=milestone%3A2.7.3 > > #93: The scope of this issue is a bit broad (encompassing a Gen3 dummy-ups > driver, etc) but for 2.7.3, I think we can call this closed, so long as > there are no issues pushing this to www.networkupstools.org. The current > auto-generated DDL is here: > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/ > > #158: I will rebase the commits, and replace the author's email address > with the GitHub username at noreply address, but if someone has additional > Powerware-based UPSes to test, that would be handy. > > #185: Debian patch is on a branch; I will bump the version number and > merge. > > #187: This is a driver-specfic fix, but I haven't had time to work through > the logic from the vendor driver. This is not listed on the GitHub 2.7.3 > milestone - should it be? > > #190 is a bit more complicated. We are still in the initial investigation > stage, but it seems that this may have crept past the Ubuntu automated test > suite. Running in the foreground is a bit of an ugly hack, but if it works > with the Ubuntu init scripts... > > I'll let Arno cover the eaton_epdus branch. Also driver-specific > (snmp-ups), so should not affect the rest of NUT. (Is this the same as > issue #188? <https://github.com/networkupstools/nut/issues/188> ) > > Glad to hear that Arno will have more time to work on NUT again! > > -- > Charles Lepple > clepple at gmail > > > > > _______________________________________________ > Nut-upsdev mailing list > Nut-upsdev at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150305/77c3aefc/attachment.html>
For reference: https://github.com/networkupstools/nut/issues/10 On Mar 5, 2015, at 1:09 AM, Baruch Even <baruch at ev-en.org> wrote:> Hi, > > There is one issue that I would consider as a major issue and not fixed yet. It is the use of wall time for scheduling ups polls instead of a monotonic clock source. I provided a (partial) patch in the past and I believe there was some work on it. > > The bug manifests itself as a stop of monitoring with no alarm when the clock is moved backwards in time. > > Please consider adding this to the release.Hi Baruch, What seems to have happened is that it was assigned to an Eaton contractor, and it got tangled up in a C++ unit test framework branch that did not get fully merged before the contract apparently ended. It was also tagged in GitHub with the "2.8" milestone, probably with the understanding that there would be a few more 2.7.x incremental releases in the mean time. The issue list I mentioned for 2.7.3 is composed of two categories: small patches with limited impact, and a larger issue that would affect a lot of people (the NSS bug). While I think that monotonic clocks are the right solution for polling timers in the long term, I would be surprised if a lot of NUT installations worry about time going backwards, since that has big implications for log traceability. I am prepared to suggest releasing 2.7.3 with the NSS bug intact, since it fails safe (although useless) and can be worked around with configuration (run upsd in foreground). Documenting the handling of non-monotonic time as a known bug (with a simple patch tested on Linux) is perhaps not equivalent, but given the developer resource constraints we have had over the past year, I think it is not out of the question. -- Charles Lepple clepple at gmail
Hi Charles and NUT Developers, As mentioned privately to the NUT Core team, I'm almost back, thanks to Eaton renewed involvement... That still implies to catch up my late on the many topics and the roadmap. But finally, this time, it should be for real. 2015-03-04 15:04 GMT+01:00 Charles Lepple <clepple at gmail.com>:> We only have a few open items that I think should be resolved before > releasing 2.7.3. The list grew a bit in the past week, but we'll cover that > later. Here is the list: > > * #93: Devices Dumps Library improvements < > https://github.com/networkupstools/nut/issues/93> >* #158: Powerware BCMXCP advanced features <> https://github.com/networkupstools/nut/pull/158> > * #185: insecure storage of password in nut-monitor favorites file < > https://github.com/networkupstools/nut/issues/185> > * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM < > https://github.com/networkupstools/nut/issues/187> > * #190: upsd: NSS SSL only working in debug mode < > https://github.com/networkupstools/nut/issues/190> > * eaton_epdus branch: < > https://github.com/networkupstools/nut/tree/eaton-epdus> > > Most of these are from the GitHub 2.7.3 milestone: > https://github.com/networkupstools/nut/issues?q=milestone%3A2.7.3 > > #93: The scope of this issue is a bit broad (encompassing a Gen3 dummy-ups > driver, etc) but for 2.7.3, I think we can call this closed, so long as > there are no issues pushing this to www.networkupstools.org. The current > auto-generated DDL is here: > http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/ >I've updated that one, closed the last task that makes sense, and postponed the others for now (Gen3 dummy-ups and call to massive users reports), to not block 2.7.3 more. #158: I will rebase the commits, and replace the author's email address> with the GitHub username at noreply address, but if someone has additional > Powerware-based UPSes to test, that would be handy. >I'm checking to get a hand on these legacy Eaton devices. My current workload is a bit too crowded to however commit on being able to test for 2.7.3 before Thursday March 19th.> #185: Debian patch is on a branch; I will bump the version number and > merge. > > #187: This is a driver-specfic fix, but I haven't had time to work through > the logic from the vendor driver. This is not listed on the GitHub 2.7.3 > milestone - should it be? > > #190 is a bit more complicated. We are still in the initial investigation > stage, but it seems that this may have crept past the Ubuntu automated test > suite. Running in the foreground is a bit of an ugly hack, but if it works > with the Ubuntu init scripts... > > I'll let Arno cover the eaton_epdus branch. Also driver-specific > (snmp-ups), so should not affect the rest of NUT. (Is this the same as > issue #188? <https://github.com/networkupstools/nut/issues/188> ) >there is still at least 1 RFC on a set of new variables (input.*.load, input.*.realpower, input.*.power) for ePDUs, prior to merging. Note that ePDU measure such data on the input, hence these new variables... !! we may consider the present mail as the RFC to speed up things !!> Glad to hear that Arno will have more time to work on NUT again! >yeah ;) thanks and cheers, Arno -- Eaton Data Center Automation - Opensource Leader NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150311/c24683a6/attachment.html>
On Mar 4, 2015, at 9:04 AM, Charles Lepple wrote:> We only have a few open items that I think should be resolved before releasing 2.7.3. The list grew a bit in the past week, but we'll cover that later. Here is the list: > > * #93: Devices Dumps Library improvements <https://github.com/networkupstools/nut/issues/93> > * #158: Powerware BCMXCP advanced features <https://github.com/networkupstools/nut/pull/158> > * #185: insecure storage of password in nut-monitor favorites file <https://github.com/networkupstools/nut/issues/185> > * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM <https://github.com/networkupstools/nut/issues/187> > * #190: upsd: NSS SSL only working in debug mode <https://github.com/networkupstools/nut/issues/190> > * eaton_epdus branch: <https://github.com/networkupstools/nut/tree/eaton-epdus> > > Most of these are from the GitHub 2.7.3 milestone: https://github.com/networkupstools/nut/issues?q=milestone%3A2.7.3A quick status update: * #93: most of the DDL stuff is merged; anything else can wait for 2.7.4. * #158: the branch has been collapsed into one commit, but additional documentation (nut-names.txt) is needed: https://github.com/networkupstools/nut/commit/00b8c8383a2614fc0bc8df190402b2dc885848a2 * #185: merged * #187: no update from original comment: "This is a driver-specfic fix, but I haven't had time to work through the logic from the vendor driver. This is not listed on the GitHub 2.7.3 milestone - should it be?" * #190: no update on NSS SSL bug. Since it fails safe, I am willing to document around it (foreground hack). Has anyone else had a chance to look at it? * eaton_epdus branch: Arnaud, you may need to refresh my memory on what there the latest code is (pushed to same branch, or another issue?), and what needs to be agreed upon for the new names? thanks, -- Charles Lepple clepple at gmail
Hi Charles and the list, a complementary update... 2015-03-16 13:46 GMT+01:00 Charles Lepple <clepple at gmail.com>:> On Mar 4, 2015, at 9:04 AM, Charles Lepple wrote: > > > We only have a few open items that I think should be resolved before > releasing 2.7.3. The list grew a bit in the past week, but we'll cover that > later. Here is the list: > > > > * #93: Devices Dumps Library improvements < > https://github.com/networkupstools/nut/issues/93> > > * #158: Powerware BCMXCP advanced features < > https://github.com/networkupstools/nut/pull/158> > > * #185: insecure storage of password in nut-monitor favorites file < > https://github.com/networkupstools/nut/issues/185> > > * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM < > https://github.com/networkupstools/nut/issues/187> > > * #190: upsd: NSS SSL only working in debug mode < > https://github.com/networkupstools/nut/issues/190> > > * eaton_epdus branch: < > https://github.com/networkupstools/nut/tree/eaton-epdus> > > > > Most of these are from the GitHub 2.7.3 milestone: > https://github.com/networkupstools/nut/issues?q=milestone%3A2.7.3 > > A quick status update: > > * #93: most of the DDL stuff is merged; anything else can wait for 2.7.4. > > * #158: the branch has been collapsed into one commit, but additional > documentation (nut-names.txt) is needed: > https://github.com/networkupstools/nut/commit/00b8c8383a2614fc0bc8df190402b2dc885848a2 >branch updated for nut-names.txt + few minor updates. I've also rebased on master, but will need another round (following the 2 branches pushed below) I'm still lagging behind the HW tests, so if you can, let's move on... otherwise, I'll do, but not today. I'll check whenever possible, but Igor's feedback seems good to me, until proven the opposite. Note that I've added an issue to track battery.charger.status needed documentation completion: https://github.com/networkupstools/nut/issues/196 * #185: merged> > * #187: no update from original comment: "This is a driver-specfic fix, > but I haven't had time to work through the logic from the vendor driver. > This is not listed on the GitHub 2.7.3 milestone - should it be?" >if it can be addressed quickly, maybe. Otherwise, for 2.7.4...> * #190: no update on NSS SSL bug. Since it fails safe, I am willing to > document around it (foreground hack). Has anyone else had a chance to look > at it? >sadly, no, not yet. Still head underwater, as you can see...> * eaton_epdus branch: Arnaud, you may need to refresh my memory on what > there the latest code is (pushed to same branch, or another issue?), and > what needs to be agreed upon for the new names? >I pushed to the same branch and documented the new vars: input.*.load, input.*.realpower and input.*.power No much need for a hard agreement, more for info... I've rebased and pushed this branch to master. I've also fixed the eaton-energysave branch as per the names pushed in in #158. Note that I've proposed and made an addition for battery.energysave.realpower Just rebased and merged the branch few minutes ago. The rest is good to me too. So is everything good to go from your PoV Charles? thanks for this update and all your work, as usual Charles! Cheers, Arno -- Eaton Data Center Automation - Opensource Leader NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150319/c64594b8/attachment.html>