/kudos.check_health

Ansible role for the Health Checker tool

Primary LanguageJinjaGNU General Public License v3.0GPL-3.0

kudos.check_health

Deployment and configuration of the KUDOS Health Checker framework (http://www.kudos.be/Projects/Health_checker.html)

Requirements

Ansible v2.8+

Role Variables

Core configuration

hc_core:
  time_out: <seconds>
  log_healthy: <yes|no>
  will_fix: <yes|no>
  report_last_cache: <yes|no>
  report_today_cache: <yes|no>
  count_archives: <yes|no>

Default values (non-null):

  • time_out: 60
  • log_healthy: no
  • will_fix: no
  • report_last_cache no
  • report_today_cache no
  • count_archives yes

Scheduling (cron) configuration

hc_scheduling:
  cron:
    when: <time_date_definition>
    user: <text>
    action: <text>
    no_lock: <yes|no>
    timeout: <number_seconds>
    options: <text>

Default values (non-null):

  • enabled: yes
  • scheduled: no
  • cron/when: 00 * * * *
  • cron/user: root
  • cron/action: --run
  • cron/no_lock: no

Above settings can be overridden by specific values in individual plugins.

Note: the scheduling (cron) settings are not supported for the HP-UX plugins. For scheduling on HP-UX, cron packages should be used instead.

Plugin configuration (checks)

States

Plugins can have 3 different levels of state settings:

  • installed: the plugin must be present/installed on the target host.
  • enabled: the plugin must be enabled (allowed to run) on the target host.
  • scheduled: the plugin must be scheduled to run on the target host. Currently only schedeling via cron is supported.

Note: setting the installed will determine whether the corresponding package will be installed or not. Plugins that are bundled together in a package will have their package installed when at least one plugin of that package is set to be installable. In that case there will not be a 1-1 relationship between the installed flag and the presence of the plugin on the target host.

Platform AIX

Platform Clusterware

Platform Exadata

Platform HP-UX

Platform Linux

Platform Serviceguard

Plugin configuration (display)

Plugin configuration (notify)

Static definitions

Following variables must be available in the role vars:

  • hc_display_plugins: list of display plugins
  • hc_notify_plugins: list of notify plugins
  • hc_configs: list of plugins that require a configuration file
  • hc_packages: map plugin -> package
  • hc_cron_packages: map plugin -> cron package (only for HP-UX)

Note: do not change these definitions unless you know what you are doing!

Additionally, following static vars may be defined to configure custom plugins:

  • hc_extra_configs: list of plugins that require a configuration file
  • hc_extra_packages: map plugin -> package
  • hc_extra_cron_packages: map plugin -> cron package (only for HP-UX)

Dependencies

No dependencies

Example Playbook

Including an example of how to use your role (for instance, with variables passed in as parameters) is always nice for users too:

    - hosts: all:!windows
      remote_user: root
      become: yes
      roles:
        - kudos.check_health

License

GPL v3

Author Information

Patrick Van der Veken - KUDOS BV (http://www.kudos.be)