[Nut-upsdev] Roadmap to 2.7.3

Arnaud Quette
Wed, 11 Mar 2015 08:23:02 -0000

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>