...
- 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 (seepriority_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 frombin/nmis-cli act=schedule
for details.
Furthermore, all log output for a particular job can be redirected to a separate file as well (usingjob.output=/some/path/nameprefix
). - NMIS 9 CLI Improvements
bin/nmis-cli
can now show the live NMIS daemon and worker process status (withact=status
).
It is now possible to delete or abort scheduled jobs in bulk, usingbin/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.
...