Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor additions

...

  • 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.

Known Limitations

  • When this version is installed on CentOs and RedHat from scratch, the log format in logs/nmis.log is unsatisfactory, and too much data will be logged (at level debug).
    This is caused by incompatible changes in the Mojolicious module version 8.x. A workaround is in planning.
    Please note that when upgrading from an earlier NMIS 9 version, the Mojolicious module will not be upgraded and this problem will not affect you.

...