...
opHA introduces the concept of a master Primary & pollers servers:
- The master Primary is the node that have the information of all the pollers and it is where we can read all the information from.
- The pollers, collect their own data, and send that information to the master Primary when it is requested.
The process of synchronising the information of the nodes is made by the masterPrimary. The master Primary requests the information for each poller with pull requests.
...
- Fix for configuration files that were not be read in conf.d directory (opCommon and Config).
- Removed error from logs that was not able to read conf.d.
- Now is not possible to discover a peer with same cluster_id than other poller or the masterPrimary.
- Updated cli tool get_own_config.
- Internal minor fixes in the installer:
- support tool is updated now.
- updated function for convert json files in common-cli.
...
- Bugfix: Discover peer window was closing when required fields missing.
- Bugfix: Update the last_update field to the synchronisation. This was causing some data not being updated in the master Primary and expire_at field for events not being updated in all the documents.
- New cli cleanup functions to clean data from the cli tool.
- Added new cli function get_status to get the status for each poller in json format.
- Some minor bug fixes and internal improvements.
...
- Added new features to the centralised configuration from the master Primary with support for OMK and NMIS files:
- Added new configuration file types.
- Remove files from pollers.
- Add a button with rollback instructions.
- Improved landing page, with information of the peers. Now the peers have an status API that check the daemons and the database status.
- Send the role to the pollers: If a role is set to poller, it doesn't let the use to use the GUI functions.
- Add conf.d to support zip.
- opha new cleanup functions.
- View resulting configuration files.
...
- Support for centralised configuration from the master Primary with support for OMK and NMIS files.
...
- Support for NMIS 9 to show poller nodes from the masterPrimary.
- A new button is added on the peers screen to edit manually the poller's url.
...
- Support for node deletion on the pollers. When a node was deleted on the poller, all this data wasn’t remove on the masterPrimary. Now the pull process is going to remove nodes and associated data that was removed on the poller.
- Retry policy on pull failures: If there was a failure during the poller update, the pull finished. Now it is possible to specify a retry policy:
- retry number: How many times retry a request before finish the process unsuccessfully. 3 is the default value.
- delay: How many seconds is going to wait between retries (5 seconds by default).
- It is possible to modify this params in opCommon.nmis:
...
Hot fix to solve the problem of visualise the nodes graphics of the poller from the masterPrimary.
3.0.2
| Status | ||||
|---|---|---|---|---|
|
On this version, the master Primary is going to request the information by chunks. The number of calls is based on the chunk size and the number of results. The chunk size can be modified on conf/opCommon.nmis on the poller, with the next parameter (Note that a service restart is needed to use the new parameters):
...
- The configured pollers can be seen/modified on this page: http://masterPrimary/en/omk/opHA/peers/
You can see how many calls is going to perform for each peer doing this request to that poller: http://poller/en/omk/opHA/api/v1/chunks
...