User Tools

Site Tools


NEMS To Do List

This list details features which are planned for future releases of NEMS. NEMS is released on a 6 month schedule, with a major release every May and November. Thanks to the NEMS Migrator, upgrading is a cinch, and thanks to NEMS' rolling release system, many fixes, patches and upgrades can find their way into existing installations.

Things I Plan To Do

There is not necessarily a planned timeline for each of these items, but here is a list of some of the things I do hope to do in an upcoming release.

  • Fix items which currently reside on the Known Issues list.
  • Add SSL option for all web connections or force as default with documentation on why certs will be self-signed. Will be part of NEMS 1.3+. As per Steve.
  • Add interface to allow all active data to saved to an external hard drive or network share as suggested by meveric.
  • Further improve the mobile responsive layout for tablets and smartphones (It's really rudimentary at the moment due to the nature of Nagios' interface… frames? C'mon now.)
  • Branch NEMS out to more powerful SBCs for larger environments, starting with the ODROID C2.
  • Provide pre-built NEMS hardware appliances (anyone interested?).
  • Upgrade Nagios to Nagios Core 4. (?) - Unlikely since most of the cool things about NEMS rely on Nagios Core 3.5.1 … at least for now.
  • Further streamline the implementation of Check_MK. Deploy check-mk-server.
  •  Expand the documentation to include setting up SMTP and mail alerts, including a new video demonstration on Category5 Technology TV.
  • Create an OVA of NEMS for deployment on existing virtual infrastructures (just for the challenge/fun of it).
  • Build a graphical interface for nems-init.
  • Build a graphical interface for NEMS-Migrator's “Restore” feature.
  • Make it so nems-benchmark runs a nightly test and saves to a log file. Include this log in backup.nems for support purposes.
  • I'm open to suggestions! Please post your comments at

Things I Will Not Do

This is a list of features I will not implement.

  • Raspberry Pi Zero, 1 & 2 support. Buy a Raspberry Pi 3. The higher performance of a Pi 3 is a major asset for a project like NEMS, so I will not be focusing any of my efforts on supporting legacy hardware.
  • GUI/Desktop. NEMS is a Linux server. If you require a GUI/Desktop Environment, you're doing it wrong. I have built a very nice, easy to use web interface, and have worked hard to provide good documentation to ease the complication of configuration for novice users. NEMS itself should not even have a screen connected to it. Just power and Ethernet. Everything happens either through your browser, or for advanced users, an SSH connection.