NMIS 9.0.1a

This beta release was published on 28 May 2019.
Please contact us at beta@opmantek.com if you're interested in trying out NMIS 9 pre-releases.

Highlights

• The main page load time was optimised by reducing the network_summary_view load time. 

NMIS 9.0.1

This beta release was published on 17 May 2019.
Please contact us at beta@opmantek.com if you're interested in trying out NMIS 9 pre-releases.

Highlights

• Lots of bug fixes, robustness and performance improvements.
• It is no longer necessary to configure the list of groups that the NMIS GUI should show;
  by default members of all groups are visible now and only groups that are explicitely configured to be hidden (using the hide_groups  configuration item) are omitted from the display. Groups can be created and assigned freely when editing or creating nodes, both with node_admin as well as using the GUI.
• Self-check faults are now logged as stateless events for node 'localhost' (if such a node exists).
• NMIS 9 now supports authentication using the system's PAM authentication infrastructure.
• NMIS 9 now properly and fully supports case-sensitivity in node names everywhere.
• "-node" and "-info" files in var are no longer required or created.
• Various information shown on the node dashboard is now updated immediately (e.g. "last ping" timestamp"), and no longer refreshed only during collect operations.
• The node_admin tool now supports more complete snapshotting of nodes (with act=dump), which optionally includes the node's RRD files, events and other historic records.
  When importing a thusly dumped node with act=import it is now possible to have all identifiers localised to the current system (with localise_ids=true ); this causes the imported node to be  'adopted' by and become active on the current NMIS system immediately.
  This mechanism allows a node to be moved completely between NMIS systems, without losing any of the node's history.
• Minor model improvements.
• More efficient node configuration structures.
  Please note that it is necessary to run bin/nmis-cli act=noderefresh  once after upgrading to activate those changes; the installer will normally perform this operation for you.

...

This beta pre-release was published on 11 Apr 2019.
Please contact us at beta@opmantek.com if you're interested in trying out NMIS 9 pre-releases.

Highlights

• The nmis9d (and the NMIS 9 installer) now interact cleanly with both systemd and sysv init systems.
• Installing on Ubuntu 18 now works.
• Orphaned worker processes left behind by a crashed nmis9d are now cleaned up more quickly and  reliably.
• various feature extensions in admin/node_admin.pl, e.g. act=dump and act=restore can now also capture and restore a node's RRD files
• Node deletion was  improved to ensure no scheduled collection jobs remain or interfere, and also includes historic/inactive events and operational status records.
• Support tool no longer captures leftover legacy configuration files
• Selftest is less likely to produce false positives
• Node editing in the GUI now presets the configuration fields with correct defaults
• The fping infrastructure now correctly handles the case of an admin modifying a node's IP address instead of caching stale data. 
• Service tests whose monitoring scripts return unexpected exit codes are now  treated as 'failed/service down' and such occurrences are logged.
• Fixed race condition in the configuration loading code, which could cause daemon crashes if the configuration is updated frequently (using the GUI or admin/patch_config.pl).
• Various bug fixes and robustness improvements

...

This is a beta pre-release and was published on 21 Aug 2018.
Please contact us at beta@opmantek.com if you're interested in trying out NMIS 9 pre-releases.

Highlights

• Feature Parity with NMIS 8.6.7G
  The improvements made in NMIS 8.6.7G have been incorporated into NMIS 9 where applicable.
• Substantially improved GUI rendering speed and reduced resource usage
  The GUI is now usable on a system with only one CPU core and 2 GB of ram.
• Now supports running on systems without systemd better: the installer now provides a classic init script for MongoDB
• admin/node_admin.pl was extended to offer more flexible import and export options.
• Various bug fixes and robustness improvements

...

This beta pre-release was published on 14 Jun 2018.
Please contact us at beta@opmantek.com if you're interested in trying out NMIS 9 pre-releases.

Highlights

• Feature Parity with NMIS 8.6.6G
  NMIS 9.0.0c supports the new  Polling Failover mechanism, and all  recent improvements made in NMIS 8 are present in NMIS 9.0.0c (where applicable).
  This also includes the recent improvements for Single-Sign-On.
• Can run in parallel with NMIS 8
  If your server specs are suitable (min. 4GB of RAM, 6-8GB recommended), then NMIS 8 and NMIS 9 can be installed on the same server without interference.
  NMIS 9 normally installs itself into /usr/local/nmis9, and its web entry point (http://localhost/nmis9/) doesn't interfere with NMIS 8.
  If the installer detects an NMIS 8 instance on your server, then it offers to import the NMIS 8 nodes' configuration: all nodes would then be polled in parallel by both NMIS 8 and NMIS 9.
• Full installer support for platforms Debian 9, Ubuntu 16.04, CentOS 7 and 6.
• Improved installer behaviour for both installations from scratch and upgrades from 9.0.0b.
  Upgrading from earlier releases of NMIS 9 (nightly or 9.0.0b) should now be supported seamlessly, ie. all required structural changes should be taken care of by the installer.
• Automatic priming for monitoring of localhost, ie. the NMIS server itself
• Node administration suite is now feature-complete
  admin/node_admin.pl can now perform all typical node operations, as well as export and import of a node's complete database information for diagnostic purposes.
• Improved and more consistent logging
• Fine-grained Operational Status information
  NMIS 9 now creates operational status overview records for every operation that is performed in the background.
  This operational status is accessible from the GUI (in the menu under System -> Host Diagnostics -> Ops Status).
• Improved robustness and flexibility of the job scheduling logic
  Long-dead nodes are now demoted to fewer connection attempts after 14 days of inaccessibility.
  Job priorities can now be freely configured (see priority_schedule in conf-default/Config.nmis).
  The intial update operation for newly added nodes is now automatically prioritised above all other operations.
• Improved self-test capability and support tool.
• More flexibility for manually scheduled jobs
  bin/nmis-cli can now schedule any job with a specific (higher or lower than default) verbosity, which will affect just that one job.
  See the help text from bin/nmis-cli act=schedule for details.
  Furthermore, all log output for a particular job can be redirected to a separate file as well (using job.output=/some/path/nameprefix).
• NMIS 9 CLI Improvements
  bin/nmis-cli can now show the live NMIS daemon and worker process status (with act=status).
  It is now possible to delete or abort scheduled jobs in bulk, using bin/nmis-cli act=delete-schedule id=ALL job.type=<something> job.uuid=<somenodeuuid>; note that "id=ALL" is required to indicate that all matching jobs are to be removed.
• Various Minor GUI Improvements
  The Node dashboard widget now displays the last time  for ping, collect and update separately, and if there is a job in progress or pending for this node, then that is shown as well.

...

Version 9.0.0b is a late alpha/early beta pre-release, which was published on 6 Apr 2018.
Please contact us at beta@opmantek.com if you're interested in trying out NMIS 9 pre-releases.

Highlights

• Full installer support for platforms Debian 9, Ubuntu 16.04, CentOS 7 and 6.
• This version can coexist with NMIS 8 on the same machine.
• New MongoDB backend which now holds almost all node and status information.
• Better long-term maintainability (no more configuration file or default model copying necessary)
• New NMIS polling engine which now uses an nmis9 daemon and a configurable number of worker processes,
  which results in more even (and somewhat reduced) server resource utilisation.
• Daemons support reconfiguration without restart for verbosity/debugging changes with signals USR1 (more verbose) and USR2 (less verbose)

...