...
Version 2.1.0 was released on 24 Nov 2014, and includes some new features as well as numerous bug fixes.
...
Highlights
- 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 configuration option
load_applications
. opconfig-cli
can now be told to echo command outputs (via command line optionprint_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
...
It's a new major release of opConfig with many substantial changes.
Highlights
- This version comes with the interactive Opmantek Installer which guides you through both upgrades and initial installations.
- opConfig no longer uses CGI scripts; instead it integrates with the Opmantek Web Server infrastructure, which provides consistency across applications and better scalability.
opConfig now runs out of/usr/local/omk
and interoperates with all other current Opmantek Applications (ie. opExport, opEvents, opCharts, opHA 2, Open-AudIT Enterprise). - The GUI was revised and modernized, and both interactive response time and performance have improved substantially.
- opConfig now provides a flexible and extensible facility for (software and configuration) Compliance Management.
- Credential sets are now stored in encrypted form within the database.
- opConfig now provides integration with Open-AudIT Enterprise and optionally imports complete audit information for nodes known to Open-AudIT Enterprise.
- opConfig now interoperates better with opEvents, and node configurations are shared between the applications. Importing node information from NMIS also has been simplified.
- User authorization (using groups) is now supported and nodes are completely invisible to users whose authorization doesn't match the nodes' groups.
- The default command sets were reorganized and now support easier separation into different classes, e.g. hourly/daily/weekly sets of commands.
- The functionality of the opconfig-cli.pl CLI tool and its builtin documentation were extended and improved.
- opConfig now also ships with the Opmantek Support Tool.
- Almost all configuration is now performed from within the GUI. The only remaining configuration files are the opCommon file, and the command set and compliance policy files.
Existing credential sets and connection lists are migrated automatically on first startup. - Application logging was revised and overhauled.
- opConfig now deals better with querying Unix systems for configuration.
- And of course lots of bugs were resolved, and minor imperfections repaired.
...
Version 1.1.9 was released on 21 Feb 2014.
Highlights
This is a maintenance release incorporating primarily minor bug fixes. The main noteworthy change is an update to the licensing system: to evaluate opConfig you will require a new evaluation license. Full licenses are not affected by this change.