User Tools

Site Tools


NEMS Linux To Do List

This list details features which are planned for future releases of NEMS Linux. NEMS Linux is released on a 6 month schedule, with a major release every May and November. Thanks to the NEMS Linux Migrator, upgrading is a cinch, and thanks to NEMS Linux' 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 the nagiosadmin user to the forbidden list in nems-init as per dlayng
  • Add Event Handlers capability as per as per mcornhill
  • Implement IsItDown service with API for distributed testing of web site uptime (eg., so a user can monitor web site uptime from other NEMS Linux users geographic coordinates, not just their own, to rule out local issue).
  • Monitorix graphs can take a while to be generated after a reboot. To help new users understand this, add a feature that checks for the files and shows “check back soon” type message instead of broken images until they are available as per panda2297
  • Evaluate openITCockpit as a possible front-end.
  • Add feature to nems-migrator's off site backup that allows a user to request an email if their backup fails (can get the email info from NEMS SST and send email accordingly, separate of Nagios).
  • Make it so first boot automatically takes user into nems-init, with the option of instead running it through SSH.
  • Add switch to NEMS SST (which requires new notify_ commands) to next major release as per luckyworlock.
  • Document and/or fix if needed check_rpi_temperature as per mgl1976
  • Must improve logrotate. Some of the logs are getting quite large on some systems that have been up for a long time.
  • Upgrade Monitorix to latest build or move to Git.
  • Move all commands from commands.cfg to checkcommands.cfg (or whichever is more appropriate) within NEMS Migrator.
  • Add check command-specific documentation.
  • Make it so migrator also transfers OS definitions as per Rick.
  • Add button to enable/disable TLS on SMTP to NEMS SST.
  • Remove RPi-Monitor from navigation menu when disabled by NEMS SST.
  • Remove Raspberry Pi-specific graphs from Monitorix when running on other SBC. Add other graphs for those SBC's.
  • Add some generic true/false data to NEMS Anonymous Stats. In particular, discover if any users are using features like Telegram. By knowing this, I can decide if a feature should be removed from future releases.
  • Ability to use external storage for all active data. Ideal for reducing read/writes on SD cards. 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 Linux out to more powerful SBCs for larger environments, starting with the ODROID XU4 and the CL100 during the 1.3 release cycle.
  • Provide pre-built NEMS Linux hardware appliances (anyone interested?).
  • Upgrade Nagios to Nagios Core 4. (?) - Unlikely since most of the cool things about NEMS Linux rely on Nagios Core 3.5.1 … at least for now.
  • Further streamline the implementation of Check_MK. Deploy check-mk-server.
  • Create an OVA of NEMS Linux 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 Linux-Migrator's “Restore” feature.
  • Change NEMS' release cycle to feature more rolling releases throughout the course of each major version. When NEMS was first created, it did not have rolling releases. Now that it does, we probably do not need a new major release every 6 months.
  • I'm open to suggestions! Please post your comments at

NEMS Linux Roadmap

  • 1.0 - COMPLETE - Initial release. Bring easy deployment of Nagios to Raspberry Pi 3.
  • 1.1 - COMPLETE - Creation of upgrade process, nems-migrator and optimize performance.
  • 1.2 - COMPLETE - Creation of nems-init process to setup initial system. Create documentation.
  • 1.3 - COMPLETE - Focus on feature set, add off site backup. Being laying the groundwork for upcoming 1.4 (in particular, non-Pi architectures).
  • 1.4 - New build of NEMS Linux featuring support for multiple SBC options and Nagios 4.
  • 1.5 - Introduction of more SBCs and possibly a virtual appliance.
  • 1.6 - Begin focusing on UX and feature consolidation. Ie., up until now it takes using NEMS-SST to configure, NConf to setup, plus Nagios Core or Check_MK to monitor. Work on consolidating into brand new NEMS interface (all features in one user interface).
  • 1.7 - NEMS Linux should now have full control over configuration: no more need for NConf.
  • 1.8 - NEMS Linux should now have full control over monitoring: no more need for Nagios Core or Check_MK.
  • 1.9 - Polish the interface and improve features.
  • 2.0 - The final NEMS Interface, with the old features removed.
  • 2.1 - TBA

NEMS Linux Visionary List

This list covers potential features for future releases of NEMS Linux. None of these are set in stone, and should only be considered ideas.

  • Nagios 4.
  • Introduce a new user interface for Nagios, replacing nConf completely with the full suite from check_mk.
  • NEMS Linux 2.0 will also be available on other SBCs.
  • Availability of both a pre-built appliance and a step-by-step guide to building your own high-powered appliance.
  • Add intrusion detection such as Snort or Bro IDS, as per mpacey.

Things I Will Not Do

This is a list of features I will not implement.

  • Raspberry Pi Zero, 1 support. Buy a Raspberry Pi 3. The higher performance of a Pi 3 is a major asset for a project like NEMS Linux, so I will not be focusing any of my efforts on supporting legacy hardware. That said, I'm impressed overall with how well the Pi 2 is performing for NEMS users, so while the Pi 2 is not as fast as the Pi 3, it may become an officially supported board in time.
  • GUI/Desktop. NEMS Linux 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 Linux 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.
  • Massive number of SBC's supported. NEMS will be available on a very select number of SBCs/devices. Each will be scrupulously tested and customized for optimum performance as a NEMS server. I am not interested in becoming an “available for all platforms” distro - NEMS has a very specific purpose, and will be developed for a very specific hardware set. That said, if you know of a particular SBC you want NEMS to work on, let me know why in the Community Forums.
todo.txt · Last modified: 2018/05/17 17:00 by Robbie Ferguson