Software:Network UPS Tools
| Developer(s) | Evgeny "Jim" Klimov Arnaud Quette Arjen de Korte Charles Lepple Numerous contributors (...) |
|---|---|
| Initial release | March 8, 1998 |
| Stable release | 2.8.0
/ April 26, 2022 |
| Written in | C |
| Operating system | Cross-platform |
| License | GPL |
| Website | {{{1}}} |
Network UPS Tools (NUT) is a suite of software component designed to monitor power devices, such as uninterruptible power supplies, power distribution units, solar controllers and servers power supply units. Many brands and models are supported and exposed via a network protocol and standardized interface.
It follows a three-tier model with dozens of NUT device driver daemons that communicate with power-related hardware devices over selected media using vendor-specific protocols, the NUT server upsd which represents the drivers on the network (defaulting to IANA registered port 3493/tcp[1]) using the standardized NUT protocol, and NUT clients (running on same localhost as the server, or on remote systems) which can manage the power devices and query their power states and other metrics for any applications, usually ranging from historic graphing and graceful shutdowns to orchestrated power failover and VM migration.
Based on NUT design and protocol, the project community authored "UPS management protocol", Informational RFC 9271, which was published by IETF in August 2022,[2] and the IANA port number registry was updated to reflect it (even though this RFC is not formally an Internet Standard).
Clients maintained in the NUT codebase include upsc, upsrw and upscmd for command-line actions, upsmon for relatively simple monitoring and graceful shutdowns (considering the amount of minimally required vs. total available power source units in the current server), upssched for complex monitoring scenarios, upscgi for a simple web interface, a NUT-Monitor X11 desktop client, as well as C, C++ and Python libraries for third-party clients. Community projects include more clients and bindings for other languages.
Being a cross-platform project, NUT works on most Unix, BSD and Linux platforms with various system architectures, from embedded systems to venerable Solaris, HP-UX and AIX servers. There were also native Windows builds based on previous stable NUT release line, last being 2.6.5. This effort was revived after the NUT 2.8.0 release, becoming part of the main codebase in September 2022 (at this time there are areas of the codebase documented in the project as placeholders and not yet ported to the Windows platform, and packages are not yet produced by the project).
History
Pavel Korensky's original apcd provided the inspiration for pursuing the APC Smart-UPS protocol in 1996.[3] This is the same software that Apcupsd derived from, according to the Debian maintainer of the latter.[4]
Russell Kroll, the original NUT author and coordinator, released the initial package, named smartupstools, in 1998. The design already provided for two daemons, upsd (which serves data) and upsmon (which protects systems), a set of drivers and examples, a number of CGI modules and client integration, and a set of client CLI tools (upsc, upsrw and upscmd), for interfacing the system with a specific UPS of a given model.[5]
Evgeny "Jim" Klimov, the current project leader since 2020,[6] focuses first on automated testing and quality assurance of existing codebase to ensure minimal breakage introduced by new contributions, as well as to clean up older technical debts and inconsistencies highlighted by modern lint and coverage tools,[7] and issuing a long-overdue new official release.[citation needed]
Over its two-decade history, the open-source project became the de facto standard solution for UPS monitoring provided with OS distributions and embedded into many NAS solutions, some converged hypervisor set-ups, and other appliances, and enjoyed contributions and support from numerous end-users as well as representatives of power hardware vendors providing protocol specifications, sample hardware, and in many cases new NUT driver code and subsequent fixes based on NUT community feedback.[citation needed]
References
- ↑ "3493/tcp". https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=3493.
- ↑ Price, Roger (August 2022), UPS management protocol, doi:10.17487/RFC9271, RFC 9271, https://tools.ietf.org/html/rfc9271
- ↑ Russell Kroll (25 November 2004). "Network UPS Tools: Acknowledgements". http://www.networkupstools.org/acknowledgements.html.
- ↑ Nils Rennebarth (1 Jul 1997). "apcupsd, genpower, and PowerChute(TM) "Black" cable". debian-user (Mailing list). Retrieved 2010-06-09.
apcupsd is derived from apcd by Pavel Korensky
- ↑ The README file for smartupstools-0.20.
- ↑ "Updates to NUT project leadership". Nut-upsdev (Mailing list). 13 November 2020.
- ↑ "NUT coding quality improvements". Nut-upsdev (Mailing list). 28 November 2020.
External links
 |  |
