Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: fixed jira typos

...

  • opConfig can now use a separate MongoDB if so desired (but node and credential configuration remain in the default/common/shared database).
  • This version includes a helper for setting up MongoDB for Opmantek use, and the installer offers to run the helper on installations and upgrades.
  • opConfig now supports per-node licensing and activation: nodes can be marked disabled from within the GUI, in which case the node does not count for license limits and no commands are run on that node, nor are audit results imported or compliance rules evaluated. By default all nodes are active.
  • opConfig now includes a full-featured command line tool for node administration, bin/opnode_admin.pl . This tool implements all node management functions already present in the GUI, as well as some extras to make it suitable for scriptable node creating and editing.
  • The display of errors and exceptions in the GUI has been improved.
  • Opmantek applications can now be selectively enabled using the configurprint_command_outputation option configuration option load_applications.
  • opconfig-cli can now be told to echo command outputs (via command line option print_command_output=true) to better integrate with external tools
  • Importing audit results from Open-AudIT Enterprise was improved to analyze and use more of a node's characteristics
  • The node editing gui was extensively reworked.
  • Error handling and reporting for opconfig-cli were improved.
  • Various fixes and improvements to both GUI and back ends

...