opHA 3.0.5 brings a new feature that allows to centralise the configuration files from the master and send it to the pollers. The configuration files can be applied in NMIS and OMK. This partial configuration files would override the configuration that the poller has.
Requirements
- NMIS 9.0.6 is required
- opHA version 3.0.5
- The pollers also need to be updated with at least version 3.0.5 of opHA
How does it work
opHA 3.0.5 has the main key points:
- The first step is create a file from a template (NMIS or OMK)
- Validate and save the file
- Create a group. By default, the following groups are created:
- pollers: With contains all peers
- master: With the local machine
- Assign peers to a group
- Assign group to a configuration file
- Push the configuration file: The file will be send to the peers and restart the daemons when needed (You will see a message when it is necessary).
Also, you can also map a role with a peer. By default, the following roles are available:
'Poller', 'Master', 'Portal', 'Local'
And this roles are assigned:
- Master: Server Local
- Poller: All existing peers available
New configurations
These are new configuration options:
- opha_config_file_types => ['NMIS', 'OMK']
- opha_role_list => ['Poller', 'Master', 'Portal', 'Local']
- conf_base_key
- conf_master_base_key
- opha_restart_nmis_needed_sections
- opha_restart_omk_needed_sections
Known issues
These are the know issues from this version (Will be solved in next releases):
- The configuration files pushed cannot be removed. But you can send the file again to override the necessary configuration.
- Backup files are saved, but it is not possible to rollback from the GUI. By default, configuration files have 2 backup files.
- Once you edit NMIS configuration, it is not possible to edit from the GUI. You will see a message when there are some configuration files overriding the local configuration.
- If the daemon is going to be restarted, it is not going to see the result on the log.