User Tools

Site Tools



todo

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 Hope 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. This list covers potential features for future releases of NEMS Linux. None of these are set in stone, and should only be considered ideas.

  • Add check_qnap3 as per Toxic.
  • Add nagiosgraphs
  • Add check_procurve_loop as per lee3521.
  • Add MSSQL check as per [email protected]. Review this plugin and the list found here.
  • Write a language sub-system for the NEMS UI, allowing users to offer translation corrections via API. Attempt to migrate the language system to all interfaces, including NConf, Adagios, and even nems-info and nems-init.
  • Configure Adagios and NEMS to support multiple NEMS servers. See this manpage.
  • Add check raspberry pi temperature and other boards if possible and set NEMS host to use it.
  • Add CSF/LFD firewall with local IP's whitelisted.
  • 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).
  • 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). Perhaps add a service check on the NEMS server instead?
  • Make it so first boot automatically takes user into nems-init, with the option of instead running it through SSH.
  • Add button to enable/disable TLS on SMTP to NEMS SST 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.
  • 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.
  • 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?).
  • 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.
  • Add intrusion detection such as Snort or Bro IDS, as per mpacey.
  • I'm open to suggestions! Please post your comments at http://baldnerd.com/nems

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 - COMPLETE - 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
todo.txt · Last modified: 2018/09/20 14:35 by Robbie Ferguson