Skip to end of banner
Go to start of banner

opConfig Release Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

opConfig 2.0.1

Version 2.0.1 was released on 30 Sep 2014, and is an important bug-fix release. We strongly recommend that you upgrade from version 2.0.0 at your earliest convenience.

  • We detected a problem with the version of the bundled MongoDB client library, which causes database connections not to be closed correctly.
    This causes the MongoDB server to reject new connections once  the normal limit of concurrent connections is exhausted (in the high hundreds).
    This, in turn, causes both the Opmantek GUI and opconfig-cli to fail after a number of  accesses.
  • Release 2.0.1 was built with an updated, fixed version of the MongoDB client.
  • If you have opEvents and opConfig 2.0.0 installed on your system, then the MongoDB client problem will affect both products as the library module is shared.
    Upgrading opConfig to version 2.0.1 will resolve the issue for both products.
  • This version also ships with the newest version of the Opmantek Support Tool.

opConfig 2.0.0

Version 2.0.0 was released on 25 Sep 2014.

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.

opConfig 1.1.9

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.

  • No labels