NUT 3.0 & new architecture - networkupstools/nut GitHub Wiki

This is a sandbox to lay down all ideas and considerations NUT 3.0, and shape up a specification:

Architecture considerations

1) C++ transition for the core (in parallel of the classic / historic core)

  • new drivers (nutdrv_*, external mapping, thread-safe code in libs, main.cpp loader / "empty shell", callbacks with real interface (not void/void))

  • nutdrv-controller

  • nutd

  • nutmon

  • nut-client

  • …​

2) asynchronous communication from end-to-end (use MQ)…​ energy efficient SW

  • needs UML diagrams (flows, class, …​)

Sandbox

  • Source tree reorganization

  • Naming transition

    • nutd, with multiple back-end plugins (classic, dbus, MQ / MQTT, Upower, SNMP, …​)

    • drivers renamed to nutdrv-*

    • clients merged into nut-client

  • Roadmap

Welcome to the Network UPS Tools (NUT) project Wiki, and feel free to contribute tricks and insights.

While there are several good entries in the menu, ones referenced most frequently in issue discussions include:

Also keep in mind the documentation links from NUT website and the FAQ in particular.

⚠️ **GitHub.com Fallback** ⚠️